From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Armin Wolf <W_Armin@gmx.de>
Cc: Hans de Goede <hdegoede@redhat.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] platform/x86: wmi: Support reading/writing 16 bit EC values
Date: Fri, 8 Mar 2024 10:01:05 +0200 (EET) [thread overview]
Message-ID: <21fd57a2-d8c3-779c-7090-b7cdfc8198be@linux.intel.com> (raw)
In-Reply-To: <20240307195753.2961-1-W_Armin@gmx.de>
On Thu, 7 Mar 2024, 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 prefectly 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.
>
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
> @@ -1162,27 +1188,28 @@ 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 (!value)
> + return AE_NULL_ENTRY;
>
> - if ((address > 0xFF) || !value)
> + if (bytes > sizeof(*value))
> return AE_BAD_PARAMETER;
>
> - if (function != ACPI_READ && function != ACPI_WRITE)
> + if (address > U8_MAX || address + bytes > U8_MAX)
This doesn't look correct. With address = 0xff and bits = 8 this will
return AE_BAD_PARAMETER, is that intensional?
--
i.
next prev parent reply other threads:[~2024-03-08 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 19:57 [PATCH v2 1/2] platform/x86: wmi: Support reading/writing 16 bit EC values Armin Wolf
2024-03-07 19:57 ` [PATCH v2 2/2] platform/x86: wmi: Avoid returning AE_OK upon unknown error Armin Wolf
2024-03-08 8:01 ` Ilpo Järvinen [this message]
2024-03-08 16:04 ` [PATCH v2 1/2] platform/x86: wmi: Support reading/writing 16 bit EC values Armin Wolf
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=21fd57a2-d8c3-779c-7090-b7cdfc8198be@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=W_Armin@gmx.de \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
/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