From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Kurt Borja <kuurtb@gmail.com>
Cc: Armin Wolf <W_Armin@gmx.de>, Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org,
Dell.Client.Kernel@dell.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] platform/x86: alienware-wmi-base: Transition to new WMI API
Date: Tue, 31 Mar 2026 11:22:32 +0300 (EEST) [thread overview]
Message-ID: <d80f8562-f05d-c22a-5d62-398bf05b7030@linux.intel.com> (raw)
In-Reply-To: <20260331-aw-new-api-v2-1-3b0d33bf8d22@gmail.com>
On Tue, 31 Mar 2026, Kurt Borja wrote:
> Transition to the new wmi_buffer based WMI API.
>
> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
> ---
> v2:
> - Cast wmi_buffer data to __le32 and then use le32_to_cpu() before
> returning
>
> v1: https://patch.msgid.link/20260330-aw-new-api-v1-1-95910bfa1b38@gmail.com
> ---
> drivers/platform/x86/dell/alienware-wmi-base.c | 32 +++++++++++++++-----------
> 1 file changed, 19 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/platform/x86/dell/alienware-wmi-base.c b/drivers/platform/x86/dell/alienware-wmi-base.c
> index 64562b92314f..9abdc5de8e23 100644
> --- a/drivers/platform/x86/dell/alienware-wmi-base.c
> +++ b/drivers/platform/x86/dell/alienware-wmi-base.c
> @@ -9,11 +9,13 @@
> #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
>
> #include <linux/acpi.h>
> -#include <linux/cleanup.h>
> #include <linux/module.h>
> #include <linux/platform_device.h>
> #include <linux/dmi.h>
> #include <linux/leds.h>
> +
> +#include <asm/byteorder.h>
> +
> #include "alienware-wmi.h"
>
> MODULE_AUTHOR("Mario Limonciello <mario.limonciello@outlook.com>");
> @@ -150,23 +152,27 @@ u8 alienware_interface;
> int alienware_wmi_command(struct wmi_device *wdev, u32 method_id,
> void *in_args, size_t in_size, u32 *out_data)
> {
> - struct acpi_buffer out = {ACPI_ALLOCATE_BUFFER, NULL};
> - struct acpi_buffer in = {in_size, in_args};
> - acpi_status ret;
> + struct wmi_buffer out, in = {
> + .data = in_args,
> + .length = in_size,
> + };
> + int ret;
>
> - ret = wmidev_evaluate_method(wdev, 0, method_id, &in, out_data ? &out : NULL);
> - if (ACPI_FAILURE(ret))
> - return -EIO;
> + ret = wmidev_invoke_method(wdev, 0, method_id, &in, out_data ? &out : NULL);
> + if (ret)
> + return ret;
>
> - union acpi_object *obj __free(kfree) = out.pointer;
> + if (!out_data)
> + return 0;
>
> - if (out_data) {
> - if (obj && obj->type == ACPI_TYPE_INTEGER)
> - *out_data = (u32)obj->integer.value;
> - else
> - return -ENOMSG;
> + if (out.length < sizeof(*out_data)) {
> + kfree(out.data);
> + return -ENOMSG;
> }
>
> + *out_data = le32_to_cpu(*(__le32 *)out.data);
> + kfree(out.data);
Hi,
Please don't bring back duplicated kfree() calls. Just assign out.data
into a local variable so you can use __free() for it similar to what the
old code did.
--
i.
next prev parent reply other threads:[~2026-03-31 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 5:13 [PATCH v2] platform/x86: alienware-wmi-base: Transition to new WMI API Kurt Borja
2026-03-31 8:22 ` Ilpo Järvinen [this message]
2026-03-31 16:08 ` Kurt Borja
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=d80f8562-f05d-c22a-5d62-398bf05b7030@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Dell.Client.Kernel@dell.com \
--cc=W_Armin@gmx.de \
--cc=hansg@kernel.org \
--cc=kuurtb@gmail.com \
--cc=linux-kernel@vger.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