From: Mario Limonciello <mario.limonciello@amd.com>
To: "Armin Wolf" <W_Armin@gmx.de>, "Pali Rohár" <pali@kernel.org>
Cc: Dell.Client.Kernel@dell.com, mjg59@srcf.ucam.org,
hansg@kernel.org, ilpo.jarvinen@linux.intel.com,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/9] platform/x86: dell-descriptor: Use new buffer-based WMI API
Date: Mon, 9 Mar 2026 20:53:46 -0500 [thread overview]
Message-ID: <36dc7af6-11e8-4fd5-80fa-657b005a0b21@amd.com> (raw)
In-Reply-To: <c1957ff4-964c-4651-93be-056ea4d9004d@gmx.de>
On 3/9/2026 2:45 PM, Armin Wolf wrote:
> Am 09.03.26 um 18:23 schrieb Pali Rohár:
>
>> On Monday 09 March 2026 10:41:20 Mario Limonciello wrote:
>>> On 3/7/2026 6:25 PM, Armin Wolf wrote:
>>>> + /* "DELL" */
>>>> + if (le32_to_cpu(desc->vendor_signature) != 0x4C4C4544) {
>>> Do you think you could come up with a helper for matching an expected
>>> "string" like this? I /suspect/ it's going to be a common pattern that
>>> vendors use and it will increase code readability going forward if a
>>> helper
>>> is possible. I see it at least twice in this patch alone.
>>>
>>> Something like this prototype:
>>>
>>> bool wmi_valid_signature(u32 field, const char* expected_str);
>> When I read your comment, I come to another idea. What about introducing
>> a macro which will convert 4-byte string to u32 number? For example:
>>
>> #define str_to_u32(str)
>> ({ _Static_assert(__builtin_types_compatible_p(__typeof__(str),
>> char[5]), "wrong type"); (u32)(u8)(str)[0] | ((u32)((u8)(str)[1]) <<
>> 8) | ((u32)((u8)(str)[2]) << 16) | ((u32)((u8)(str)[3]) << 24); })
>>
>> The whole conversion would be done in compile time (with -O2) so should
>> not cause any possible performance issues.
>>
>> With it, the condition could be written as:
>>
>> if (le32_to_cpu(desc->vendor_signature) != str_to_u32("DELL")) {
>>
>> and no need to use magic number 0x4C4C4544 and write comment that this
>> number in ASCII is the "DELL" string.
>
> To be honest i do nothing think that having a helper function for this
> inside the WMI driver core
> is useful, especially since most vendors other than Dell do not use such
> magic numbers.
>
> From my perspective assembling the two constants ourself is fine here.
>
> Thanks,
> Armin Wolf
Oh I didn't realize no one else is doing this. Yeah if it's Dell only,
agree - meh.
>
>>
>>>> + dev_err(&wdev->dev, "Dell descriptor buffer has invalid
>>>> vendor signature (%u)\n",
>>>> + le32_to_cpu(desc->vendor_signature));
>>>> + ret = -ENOMSG;
>>>> descriptor_valid = ret;
>>>> goto out;
>>>> }
>>>> - buffer = (u32 *)obj->buffer.pointer;
>>>> -
>>>> - if (strncmp(obj->string.pointer, "DELL WMI", 8) != 0) {
>>>> - dev_err(&wdev->dev, "Dell descriptor buffer has invalid
>>>> signature (%8ph)\n",
>>>> - buffer);
>>>> - ret = -EINVAL;
>>>> + /* " WMI" */
>>>> + if (le32_to_cpu(desc->object_signature) != 0x494D5720) {
>>>> + dev_err(&wdev->dev, "Dell descriptor buffer has invalid
>>>> object signature (%u)\n",
>>>> + le32_to_cpu(desc->object_signature));
>>>> + ret = -ENOMSG;
>>>> descriptor_valid = ret;
>>>> goto out;
>>>> }
>
next prev parent reply other threads:[~2026-03-10 1:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-08 0:25 [PATCH 0/9] Convert most Dell WMI drivers to use the new buffer-based API Armin Wolf
2026-03-08 0:25 ` [PATCH 1/9] platform/x86: dell-descriptor: Use new buffer-based WMI API Armin Wolf
2026-03-09 15:41 ` Mario Limonciello
2026-03-09 17:23 ` Pali Rohár
2026-03-09 19:45 ` Armin Wolf
2026-03-10 1:53 ` Mario Limonciello [this message]
2026-03-10 10:46 ` Gergo Koteles
2026-03-14 17:55 ` Armin Wolf
2026-03-08 0:25 ` [PATCH 2/9] platform/x86: dell-privacy: " Armin Wolf
2026-03-08 0:25 ` [PATCH 3/9] platform/x86: dell-smbios-wmi: " Armin Wolf
2026-03-08 0:25 ` [PATCH 4/9] platform/x86: dell-wmi-base: " Armin Wolf
2026-03-08 0:25 ` [PATCH 5/9] platform/x86: dell-ddv: " Armin Wolf
2026-03-08 0:25 ` [PATCH 6/9] hwmon: (dell-smm) " Armin Wolf
2026-03-08 14:52 ` Guenter Roeck
2026-03-08 20:03 ` Armin Wolf
2026-03-08 0:25 ` [PATCH 7/9] platform/wmi: Make wmi_bus_class const Armin Wolf
2026-03-08 0:25 ` [PATCH 8/9] platform/wmi: Make sysfs attributes const Armin Wolf
2026-03-08 0:25 ` [PATCH 9/9] modpost: Handle malformed WMI GUID strings Armin Wolf
2026-03-09 16:07 ` Mario Limonciello
2026-03-14 17:56 ` 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=36dc7af6-11e8-4fd5-80fa-657b005a0b21@amd.com \
--to=mario.limonciello@amd.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=W_Armin@gmx.de \
--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=mjg59@srcf.ucam.org \
--cc=pali@kernel.org \
--cc=platform-driver-x86@vger.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