public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Armin Wolf <W_Armin@gmx.de>
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 2/9] platform/x86: dell-privacy: Use new buffer-based WMI API
Date: Tue, 31 Mar 2026 12:03:33 +0300 (EEST)	[thread overview]
Message-ID: <24ece1a8-dc6e-64db-0171-7e9a0ea4bacd@linux.intel.com> (raw)
In-Reply-To: <20260314175249.16040-3-W_Armin@gmx.de>

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 device state.
> 
> Signed-off-by: Armin Wolf <W_Armin@gmx.de>
> ---
>  drivers/platform/x86/dell/dell-wmi-privacy.c | 78 ++++++++++----------
>  1 file changed, 38 insertions(+), 40 deletions(-)
> 
> diff --git a/drivers/platform/x86/dell/dell-wmi-privacy.c b/drivers/platform/x86/dell/dell-wmi-privacy.c
> index ed099a431ea4..470273cc2fd2 100644
> --- a/drivers/platform/x86/dell/dell-wmi-privacy.c
> +++ b/drivers/platform/x86/dell/dell-wmi-privacy.c
> @@ -9,6 +9,7 @@
>  
>  #include <linux/acpi.h>
>  #include <linux/bitops.h>
> +#include <linux/compiler_attributes.h>
>  #include <linux/input.h>
>  #include <linux/input/sparse-keymap.h>
>  #include <linux/list.h>
> @@ -25,6 +26,26 @@
>  #define DELL_PRIVACY_CAMERA_EVENT 0x2
>  #define led_to_priv(c)       container_of(c, struct privacy_wmi_data, cdev)
>  
> +/*
> + * Describes the Device State class exposed by BIOS which can be consumed by
> + * various applications interested in knowing the Privacy feature capabilities.
> + * class DeviceState
> + * {
> + *  [key, read] string InstanceName;
> + *  [read] boolean ReadOnly;
> + *
> + *  [WmiDataId(1), read] uint32 DevicesSupported;
> + *   0 - None; 0x1 - Microphone; 0x2 - Camera; 0x4 - ePrivacy  Screen
> + *
> + *  [WmiDataId(2), read] uint32 CurrentState;
> + *   0 - Off; 1 - On; Bit0 - Microphone; Bit1 - Camera; Bit2 - ePrivacyScreen
> + * };
> + */
> +struct device_state {
> +	__le32 devices_supported;
> +	__le32 current_state;
> +} __packed;
> +
>  /*
>   * The wmi_list is used to store the privacy_priv struct with mutex protecting
>   */
> @@ -185,59 +206,36 @@ static struct attribute *privacy_attrs[] = {
>  };
>  ATTRIBUTE_GROUPS(privacy);
>  
> -/*
> - * Describes the Device State class exposed by BIOS which can be consumed by
> - * various applications interested in knowing the Privacy feature capabilities.
> - * class DeviceState
> - * {
> - *  [key, read] string InstanceName;
> - *  [read] boolean ReadOnly;
> - *
> - *  [WmiDataId(1), read] uint32 DevicesSupported;
> - *   0 - None; 0x1 - Microphone; 0x2 - Camera; 0x4 - ePrivacy  Screen
> - *
> - *  [WmiDataId(2), read] uint32 CurrentState;
> - *   0 - Off; 1 - On; Bit0 - Microphone; Bit1 - Camera; Bit2 - ePrivacyScreen
> - * };
> - */
>  static int get_current_status(struct wmi_device *wdev)
>  {
>  	struct privacy_wmi_data *priv = dev_get_drvdata(&wdev->dev);
> -	union acpi_object *obj_present;
> -	u32 *buffer;
> -	int ret = 0;
> +	struct device_state *state;
> +	struct wmi_buffer buffer;
> +	int ret;
>  
>  	if (!priv) {
>  		dev_err(&wdev->dev, "dell privacy priv is NULL\n");
>  		return -EINVAL;
>  	}
> +
>  	/* check privacy support features and device states */
> -	obj_present = wmidev_block_query(wdev, 0);
> -	if (!obj_present) {
> -		dev_err(&wdev->dev, "failed to read Binary MOF\n");
> -		return -EIO;
> -	}
> +	ret = wmidev_query_block(wdev, 0, &buffer);
> +	if (ret < 0)
> +		return ret;
>  
> -	if (obj_present->type != ACPI_TYPE_BUFFER) {
> -		dev_err(&wdev->dev, "Binary MOF is not a buffer!\n");
> -		ret = -EIO;
> -		goto obj_free;
> -	}
> -	/*  Although it's not technically a failure, this would lead to
> -	 *  unexpected behavior
> -	 */
> -	if (obj_present->buffer.length != 8) {
> -		dev_err(&wdev->dev, "Dell privacy buffer has unexpected length (%d)!\n",
> -				obj_present->buffer.length);
> +	if (buffer.length < sizeof(*state)) {
> +		dev_err(&wdev->dev, "Dell privacy buffer contains not enough data (%zu)!\n",

Same comment here as with the other patch, perhaps in other patches as 
well if it's copy pasted so please check the rest, I won't comment on 
this with the other patches.

> +			buffer.length);
>  		ret = -EINVAL;
> -		goto obj_free;
> +		goto buffer_free;
>  	}
> -	buffer = (u32 *)obj_present->buffer.pointer;
> -	priv->features_present = buffer[0];
> -	priv->last_status = buffer[1];
>  
> -obj_free:
> -	kfree(obj_present);
> +	state = buffer.data;
> +	priv->features_present = le32_to_cpu(state->devices_supported);
> +	priv->last_status = le32_to_cpu(state->current_state);
> +
> +buffer_free:
> +	kfree(buffer.data);
>  	return ret;
>  }
>  
> 

-- 
 i.


  reply	other threads:[~2026-03-31  9:03 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
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 [this message]
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=24ece1a8-dc6e-64db-0171-7e9a0ea4bacd@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=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