public inbox for linux-hwmon@vger.kernel.org
 help / color / mirror / Atom feed
From: Armin Wolf <W_Armin@gmx.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Dell.Client.Kernel@dell.com, pali@kernel.org,
	mjg59@srcf.ucam.org, soyer@irl.hu,
	Hans de Goede <hansg@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	linux@roeck-us.net, linux-hwmon@vger.kernel.org,
	mario.limonciello@amd.com
Subject: Re: [PATCH v3 1/9] platform/x86: dell-descriptor: Use new buffer-based WMI API
Date: Tue, 31 Mar 2026 22:00:33 +0200	[thread overview]
Message-ID: <44633ad0-2b80-40db-9655-e0eddb3fa02a@gmx.de> (raw)
In-Reply-To: <658006e6-bbfe-03b4-f788-8f041adda03d@linux.intel.com>

Am 31.03.26 um 11:44 schrieb Ilpo Järvinen:

> On Sat, 14 Mar 2026, Armin Wolf wrote:
>
>> Use the new buffer-based WMI API to also support ACPI firmware
>> implementations that do not use ACPI buffers for the descriptor.
>>
>> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
>> ---
>>   .../platform/x86/dell/dell-wmi-descriptor.c   | 94 +++++++++----------
>>   1 file changed, 47 insertions(+), 47 deletions(-)
>>
>> diff --git a/drivers/platform/x86/dell/dell-wmi-descriptor.c b/drivers/platform/x86/dell/dell-wmi-descriptor.c
>> index c2a180202719..fe42eb8bbd79 100644
>> --- a/drivers/platform/x86/dell/dell-wmi-descriptor.c
>> +++ b/drivers/platform/x86/dell/dell-wmi-descriptor.c
>> @@ -7,7 +7,7 @@
>>   
>>   #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>>   
>> -#include <linux/acpi.h>
>> +#include <linux/compiler_attributes.h>
>>   #include <linux/list.h>
>>   #include <linux/module.h>
>>   #include <linux/wmi.h>
>> @@ -15,6 +15,24 @@
>>   
>>   #define DELL_WMI_DESCRIPTOR_GUID "8D9DDCBC-A997-11DA-B012-B622A1EF5492"
>>   
>> +/*
>> + * Descriptor buffer is 128 byte long and contains:
>> + *
>> + *       Name             Offset  Length  Value
>> + * Vendor Signature          0       4    "DELL"
>> + * Object Signature          4       4    " WMI"
>> + * WMI Interface Version     8       4    <version>
>> + * WMI buffer length        12       4    <length>
>> + * WMI hotfix number        16       4    <hotfix>
>> + */
>> +struct descriptor {
>> +	char vendor_signature[4];
>> +	char object_signature[4];
>> +	__le32 interface_version;
>> +	__le32 buffer_length;
>> +	__le32 hotfix_number;
>> +} __packed;
>> +
>>   struct descriptor_priv {
>>   	struct list_head list;
>>   	u32 interface_version;
>> @@ -88,76 +106,58 @@ bool dell_wmi_get_hotfix(u32 *hotfix)
>>   }
>>   EXPORT_SYMBOL_GPL(dell_wmi_get_hotfix);
>>   
>> -/*
>> - * Descriptor buffer is 128 byte long and contains:
>> - *
>> - *       Name             Offset  Length  Value
>> - * Vendor Signature          0       4    "DELL"
>> - * Object Signature          4       4    " WMI"
>> - * WMI Interface Version     8       4    <version>
>> - * WMI buffer length        12       4    <length>
>> - * WMI hotfix number        16       4    <hotfix>
>> - */
>> -static int dell_wmi_descriptor_probe(struct wmi_device *wdev,
>> -				     const void *context)
>> +static int dell_wmi_descriptor_probe(struct wmi_device *wdev, const void *context)
>>   {
>> -	union acpi_object *obj = NULL;
>>   	struct descriptor_priv *priv;
>> -	u32 *buffer;
>> +	struct wmi_buffer buffer;
>> +	struct descriptor *desc;
>>   	int ret;
>>   
>> -	obj = wmidev_block_query(wdev, 0);
>> -	if (!obj) {
>> -		dev_err(&wdev->dev, "failed to read Dell WMI descriptor\n");
>> -		ret = -EIO;
>> -		goto out;
>> -	}
>> +	ret = wmidev_query_block(wdev, 0, &buffer);
>> +	if (ret < 0)
>> +		return ret;
>>   
>> -	if (obj->type != ACPI_TYPE_BUFFER) {
>> -		dev_err(&wdev->dev, "Dell descriptor has wrong type\n");
>> +	if (buffer.length < sizeof(*desc)) {
> Hi again,
>
> Thinking some more of this...
>
> Since many of these drivers will need to do this size check and assign
> into some variable that is different from the one passed to
> wmidev_query_block(), would it make sense to move those into generic code?
> It probably requires a macro so you'd have access to type information.

You mean something like wmidev_block_query_sized(wdev, instance, size)?

Personally i see little benefit in having the assignment handled by a macro.

Thanks,
Armin Wolf


  reply	other threads:[~2026-03-31 20:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-14 17:52 [PATCH v3 0/9] Convert most Dell WMI drivers to use the new buffer-based API Armin Wolf
2026-03-14 17:52 ` [PATCH v3 1/9] platform/x86: dell-descriptor: Use new buffer-based WMI API Armin Wolf
2026-03-31  9:00   ` Ilpo Järvinen
2026-03-31 19:53     ` Armin Wolf
2026-03-31  9:44   ` Ilpo Järvinen
2026-03-31 20:00     ` Armin Wolf [this message]
2026-04-01 10:06       ` Ilpo Järvinen
2026-04-01 17:31         ` Armin Wolf
2026-03-14 17:52 ` [PATCH v3 2/9] platform/x86: dell-privacy: " Armin Wolf
2026-03-31  9:03   ` Ilpo Järvinen
2026-03-14 17:52 ` [PATCH v3 3/9] platform/x86: dell-smbios-wmi: " Armin Wolf
2026-03-14 17:52 ` [PATCH v3 4/9] platform/x86: dell-wmi-base: " Armin Wolf
2026-03-31  9:20   ` Ilpo Järvinen
2026-03-14 17:52 ` [PATCH v3 5/9] platform/x86: dell-ddv: " Armin Wolf
2026-03-14 17:52 ` [PATCH v3 6/9] hwmon: (dell-smm) " Armin Wolf
2026-03-14 17:52 ` [PATCH v3 7/9] platform/wmi: Make wmi_bus_class const Armin Wolf
2026-03-14 17:52 ` [PATCH v3 8/9] platform/wmi: Make sysfs attributes const Armin Wolf
2026-03-14 17:52 ` [PATCH v3 9/9] modpost: Handle malformed WMI GUID strings Armin Wolf
2026-03-16 17:03 ` [PATCH v3 0/9] Convert most Dell WMI drivers to use the new buffer-based API Mario Limonciello
2026-03-17 15:52 ` Guenter Roeck
2026-03-17 20:11   ` Armin Wolf
2026-03-17 20:22     ` Guenter Roeck
2026-03-27 20:42       ` 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=44633ad0-2b80-40db-9655-e0eddb3fa02a@gmx.de \
    --to=w_armin@gmx.de \
    --cc=Dell.Client.Kernel@dell.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mario.limonciello@amd.com \
    --cc=mjg59@srcf.ucam.org \
    --cc=pali@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=soyer@irl.hu \
    /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