From: Hans de Goede <hdegoede@redhat.com>
To: Armin Wolf <W_Armin@gmx.de>, ilpo.jarvinen@linux.intel.com
Cc: rafael@kernel.org, lenb@kernel.org, mario.limonciello@amd.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
linux-acpi@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] platform/x86: wmi: Support reading/writing 16 bit EC values
Date: Mon, 25 Mar 2024 15:54:19 +0100 [thread overview]
Message-ID: <5f07bed0-045b-4576-81ee-c87392846334@redhat.com> (raw)
In-Reply-To: <20240314184538.2933-1-W_Armin@gmx.de>
Hi,
On 3/14/24 7:45 PM, Armin Wolf wrote:
> The ACPI EC address space handler currently only supports
> reading/writing 8 bit values. Some firmware implementations however
> want to access for example 16 bit values, which is perfectly legal
> according to the ACPI spec.
>
> Add support for reading/writing such values.
>
> Tested on a Dell Inspiron 3505 and a Asus Prime B650-Plus.
>
> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
Thank you for your patch-series, I've applied the series to my
review-hans branch:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/log/?h=review-hans
Note it will show up in my review-hans branch once I've pushed my
local branch there, which might take a while.
Once I've run some tests on this branch the patches there will be
added to the platform-drivers-x86/for-next branch and eventually
will be included in the pdx86 pull-request to Linus for the next
merge-window.
Regards,
Hans
> ---
> Chnages since v4:
> - spelling fix
> - fix checkpatch warning
>
> Changes since v3:
> - change type of variable i to size_t
>
> Changes since v2:
> - fix address overflow check
>
> Changes since v1:
> - use BITS_PER_BYTE
> - validate that number of bytes to read/write does not overflow the
> address
> ---
> drivers/platform/x86/wmi.c | 54 +++++++++++++++++++++++++++++---------
> 1 file changed, 41 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/platform/x86/wmi.c b/drivers/platform/x86/wmi.c
> index 1920e115da89..9602658711cf 100644
> --- a/drivers/platform/x86/wmi.c
> +++ b/drivers/platform/x86/wmi.c
> @@ -1153,6 +1153,34 @@ static int parse_wdg(struct device *wmi_bus_dev, struct platform_device *pdev)
> return 0;
> }
>
> +static int ec_read_multiple(u8 address, u8 *buffer, size_t bytes)
> +{
> + size_t i;
> + int ret;
> +
> + for (i = 0; i < bytes; i++) {
> + ret = ec_read(address + i, &buffer[i]);
> + if (ret < 0)
> + return ret;
> + }
> +
> + return 0;
> +}
> +
> +static int ec_write_multiple(u8 address, u8 *buffer, size_t bytes)
> +{
> + size_t i;
> + int ret;
> +
> + for (i = 0; i < bytes; i++) {
> + ret = ec_write(address + i, buffer[i]);
> + if (ret < 0)
> + return ret;
> + }
> +
> + return 0;
> +}
> +
> /*
> * WMI can have EmbeddedControl access regions. In which case, we just want to
> * hand these off to the EC driver.
> @@ -1162,27 +1190,27 @@ acpi_wmi_ec_space_handler(u32 function, acpi_physical_address address,
> u32 bits, u64 *value,
> void *handler_context, void *region_context)
> {
> - int result = 0;
> - u8 temp = 0;
> + int bytes = bits / BITS_PER_BYTE;
> + int ret;
>
> - if ((address > 0xFF) || !value)
> + if (!value)
> + return AE_NULL_ENTRY;
> +
> + if (!bytes || bytes > sizeof(*value))
> return AE_BAD_PARAMETER;
>
> - if (function != ACPI_READ && function != ACPI_WRITE)
> + if (address > U8_MAX || address + bytes - 1 > U8_MAX)
> return AE_BAD_PARAMETER;
>
> - if (bits != 8)
> + if (function != ACPI_READ && function != ACPI_WRITE)
> return AE_BAD_PARAMETER;
>
> - if (function == ACPI_READ) {
> - result = ec_read(address, &temp);
> - *value = temp;
> - } else {
> - temp = 0xff & *value;
> - result = ec_write(address, temp);
> - }
> + if (function == ACPI_READ)
> + ret = ec_read_multiple(address, (u8 *)value, bytes);
> + else
> + ret = ec_write_multiple(address, (u8 *)value, bytes);
>
> - switch (result) {
> + switch (ret) {
> case -EINVAL:
> return AE_BAD_PARAMETER;
> case -ENODEV:
> --
> 2.39.2
>
prev parent reply other threads:[~2024-03-25 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 18:45 [PATCH v5 1/2] platform/x86: wmi: Support reading/writing 16 bit EC values Armin Wolf
2024-03-14 18:45 ` [PATCH v5 2/2] platform/x86: wmi: Avoid returning AE_OK upon unknown error Armin Wolf
2024-03-14 18:56 ` [PATCH v5 1/2] platform/x86: wmi: Support reading/writing 16 bit EC values Kuppuswamy Sathyanarayanan
2024-03-25 14:54 ` Hans de Goede [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f07bed0-045b-4576-81ee-c87392846334@redhat.com \
--to=hdegoede@redhat.com \
--cc=W_Armin@gmx.de \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).