From: Rong Zhang <i@rong.moe>
To: git@turtledev.nz, "Corentin Chary" <corentin.chary@gmail.com>,
"Luke D. Jones" <luke@ljones.dev>,
"Denis Benato" <denis.benato@linux.dev>,
"Hans de Goede" <hansg@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org
Cc: "José Guilherme de Castro Rodrigues"
<jose.guilherme.cr.bh@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] platform/x86: asus-wmi: Add support for ASUS_WMI_DEVID_CAMERA_LED_NEG
Date: Tue, 17 Nov 2026 02:51:44 +0800 [thread overview]
Message-ID: <173bed0f4e42a85087766a8e8cce8557115f2ccf.camel@rong.moe> (raw)
In-Reply-To: <20261117-asus-wmi-camera-led-v5-1-41c47653758b@turtledev.nz>
Hi Zane,
On Tue, 2026-11-17 at 07:37 +1300, Zane Hunt via B4 Relay wrote:
> From: Zane Hunt <git@turtledev.nz>
>
> On some newer Zenbooks (Zenbook S 14 UX5406SA, Zenbook S 16 UM5606WA) the
> camera key turns the camera off in firmware, but the LED on the key never
> lights up under Linux. These machines don't have
> ASUS_WMI_DEVID_CAMERA_LED, so asus-wmi never registers asus::camera. The
> firmware exposes the state through ASUS_WMI_DEVID_CAMERA_LED_NEG instead.
>
> Reading CAMERA_LED_NEG is what drives the LED: the DSTS handler reads the
> camera state from the EC and writes it to the LED GPIO before returning
> it. The set side can't be used, the firmware only accepts DEVS on this
> device once per boot.
>
> When CAMERA_LED is missing but CAMERA_LED_NEG is there, register
> asus::camera as a read-only LED backed by CAMERA_LED_NEG, and read it
> after every camera key event, sending a brightness_hw_changed event.
> Registering the LED reads it as well, which fixes the LED being dark after
> a cold boot with the camera disabled. There is no brightness_set
> callback, so writes to the brightness attribute are ignored, as with
> other get-only LEDs.
>
> While at it, include <linux/container_of.h>, which this file already
> relied on.
>
> Link: https://lore.kernel.org/r/adg6GzkykThAB_4u@djouze-zen
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221752
> Assisted-by: Claude:claude-opus-5-5 iasl
> Co-developed-by: José Guilherme de Castro Rodrigues <jose.guilherme.cr.bh@gmail.com>
> Signed-off-by: José Guilherme de Castro Rodrigues <jose.guilherme.cr.bh@gmail.com>
> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Signed-off-by: Zane Hunt <git@turtledev.nz>
Reviewed-by: Rong Zhang <i@rong.moe>
Thanks,
Rong
> ---
> Changes in v5:
> - Rebased on pdx86 for-next, asus-wmi.c has moved to
> drivers/platform/asus/
> - Change the subject, this adds support for CAMERA_LED_NEG rather than
> fixing a bug in the driver (Rong)
> - Drop camera_neg_led_set(), so asus::camera has no brightness_set now.
> The key event already resyncs the LED, and skyedryv's s2idle test
> showed nothing gets missed while suspended (José, Rong)
> - "Returns" -> "Returns:" in the camera_neg_led_sync() comment (Ilpo)
> - Kept Ilpo's Reviewed-by since the only code change is dropping the
> set callback
> - Rong's idea of also sending brightness_hw_changed on machines that
> have both CAMERA_LED and CAMERA_LED_NEG is left for a follow-up, I
> only have the UX5406SA to test with
> - Link to v4: https://patch.msgid.link/20261019-asus-wmi-camera-led-v4-1-7744c125bcc9@turtledev.nz
>
> Changes in v4:
> - Keep José's Signed-off-by from v2 and add his Co-developed-by
> - Use my full name in the tags
> - Include <linux/container_of.h>
> - Reuse the existing asus::camera registration block, only the
> handlers and flags differ
> - camera_neg_led_available is now only set when CAMERA_LED is missing,
> so asus::camera is always the CAMERA_LED_NEG one when it's set. That
> makes the LED_BRIGHT_HW_CHANGED check in the event handler unneeded,
> so it's gone
> - Drop the explicit read at probe, led_classdev_register() already
> reads the state through brightness_get
> - Link to v3: https://patch.msgid.link/20261017-asus-wmi-camera-led-v3-1-845a82373997@turtledev.nz
>
> Changes in v3 (picking up José's v2, which had stalled):
> - Rebased on pdx86 for-next
> - Also read CAMERA_LED_NEG at probe, so the LED is right after a cold boot
> - Register a read-only asus::camera LED when only CAMERA_LED_NEG exists,
> with brightness_hw_changed on key presses (Ilpo's suggestion on v2)
> - Comment on why the read is what updates the LED (also from v2 review)
> - v2: https://lore.kernel.org/r/adg6GzkykThAB_4u@djouze-zen
>
> Tested v5 on the Zenbook S 14 UX5406SA (BIOS 309), on Fedora's 7.2.15
> kernel with the same change applied: camera key presses keep the LED,
> asus::camera, brightness_hw_changed and the camera output in sync, also
> with nothing reading the brightness attribute, so the key event alone is
> what updates the LED. Writing 0 or 1 to brightness changes nothing.
>
> I used Claude while working on this. It helped
> me read through the DSDT, drafted the changes on top of v2 and wrote the
> test scripts. I went through the patch myself and ran the tests on my
> laptop.
> ---
> drivers/platform/asus/asus-wmi.c | 63 ++++++++++++++++++++++++++++--
> include/linux/platform_data/x86/asus-wmi.h | 2 +-
> 2 files changed, 61 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/platform/asus/asus-wmi.c b/drivers/platform/asus/asus-wmi.c
> index b33ebdb21aa..991e5b36664 100644
> --- a/drivers/platform/asus/asus-wmi.c
> +++ b/drivers/platform/asus/asus-wmi.c
> @@ -17,6 +17,7 @@
> #include <linux/backlight.h>
> #include <linux/bits.h>
> #include <linux/cleanup.h>
> +#include <linux/container_of.h>
> #include <linux/debugfs.h>
> #include <linux/delay.h>
> #include <linux/dmi.h>
> @@ -72,6 +73,8 @@ module_param(fnlock_default, bool, 0444);
> #define NOTIFY_KBD_TTP 0xae
> #define NOTIFY_LID_FLIP 0xfa
> #define NOTIFY_LID_FLIP_ROG 0xbd
> +#define NOTIFY_CAMERA_TOGGLE_1 0x82
> +#define NOTIFY_CAMERA_TOGGLE_2 0x85
> #define NOTIFY_KEYSTONE 0xb4
>
> #define ASUS_WMI_FNLOCK_BIOS_DISABLED BIT(0)
> @@ -312,6 +315,7 @@ struct asus_wmi {
> u32 kbd_rgb_dev;
> bool kbd_rgb_state_available;
> bool oobe_state_available;
> + bool camera_neg_led_available;
>
> u8 throttle_thermal_policy_mode;
> u32 throttle_thermal_policy_dev;
> @@ -2105,6 +2109,43 @@ static int camera_led_set(struct led_classdev *led_cdev,
> return err < 0 ? err : 0;
> }
>
> +static bool is_camera_toggle(int code)
> +{
> + return code == NOTIFY_CAMERA_TOGGLE_1 || code == NOTIFY_CAMERA_TOGGLE_2;
> +}
> +
> +/*
> + * Some models (e.g. Zenbook S 14 UX5406SA, Zenbook S 16 UM5606WA) have no
> + * ASUS_WMI_DEVID_CAMERA_LED. The firmware handles the camera key itself and
> + * only exposes the state through ASUS_WMI_DEVID_CAMERA_LED_NEG, and reading
> + * that has a side effect: the firmware copies the state to the LED GPIO.
> + * Nothing else updates the LED, so read it after every camera key event.
> + * Registering asus::camera reads it too (via brightness_get), which sets the
> + * LED at probe. Setting it is no use, the firmware accepts DEVS on this
> + * device only once per boot.
> + *
> + * Returns: 1 if the camera is disabled (LED lit), 0 if enabled, or -errno.
> + */
> +static int camera_neg_led_sync(struct asus_wmi *asus)
> +{
> + u32 result;
> + int err;
> +
> + err = asus_wmi_get_devstate(asus, ASUS_WMI_DEVID_CAMERA_LED_NEG, &result);
> + if (err)
> + return err;
> +
> + return !(result & ASUS_WMI_DSTS_STATUS_BIT);
> +}
> +
> +static enum led_brightness camera_neg_led_get(struct led_classdev *led_cdev)
> +{
> + struct asus_wmi *asus = container_of(led_cdev, struct asus_wmi, camera_led);
> + int state = camera_neg_led_sync(asus);
> +
> + return state < 0 ? LED_OFF : state;
> +}
> +
> static void asus_wmi_led_exit(struct asus_wmi *asus)
> {
> scoped_guard(spinlock_irqsave, &asus_ref.lock)
> @@ -2236,11 +2277,17 @@ static int asus_wmi_led_init(struct asus_wmi *asus)
> goto error;
> }
>
> - if (asus_wmi_dev_is_present(asus, ASUS_WMI_DEVID_CAMERA_LED)) {
> + if (asus->camera_neg_led_available ||
> + asus_wmi_dev_is_present(asus, ASUS_WMI_DEVID_CAMERA_LED)) {
> asus->camera_led.name = "asus::camera";
> asus->camera_led.max_brightness = 1;
> - asus->camera_led.brightness_get = camera_led_get;
> - asus->camera_led.brightness_set_blocking = camera_led_set;
> + if (asus->camera_neg_led_available) {
> + asus->camera_led.flags = LED_BRIGHT_HW_CHANGED;
> + asus->camera_led.brightness_get = camera_neg_led_get;
> + } else {
> + asus->camera_led.brightness_get = camera_led_get;
> + asus->camera_led.brightness_set_blocking = camera_led_set;
> + }
>
> rv = led_classdev_register(&asus->platform_device->dev,
> &asus->camera_led);
> @@ -4742,6 +4789,13 @@ static void asus_wmi_handle_event_code(int code, struct asus_wmi *asus)
> if (is_display_toggle(code) && asus->driver->quirks->no_display_toggle)
> return;
>
> + if (is_camera_toggle(code) && asus->camera_neg_led_available) {
> + int state = camera_neg_led_sync(asus);
> +
> + if (state >= 0)
> + led_classdev_notify_brightness_hw_changed(&asus->camera_led, state);
> + }
> +
> if (!sparse_keymap_report_event(asus->inputdev, code,
> key_value, autorelease))
> pr_info("Unknown key code 0x%x\n", code);
> @@ -5219,6 +5273,9 @@ static int asus_wmi_add(struct platform_device *pdev)
> #endif /* IS_ENABLED(CONFIG_ASUS_WMI_DEPRECATED_ATTRS) */
>
> asus->oobe_state_available = asus_wmi_dev_is_present(asus, ASUS_WMI_DEVID_OOBE);
> + asus->camera_neg_led_available =
> + !asus_wmi_dev_is_present(asus, ASUS_WMI_DEVID_CAMERA_LED) &&
> + asus_wmi_dev_is_present(asus, ASUS_WMI_DEVID_CAMERA_LED_NEG);
>
> if (asus_wmi_dev_is_present(asus, ASUS_WMI_DEVID_THROTTLE_THERMAL_POLICY))
> asus->throttle_thermal_policy_dev = ASUS_WMI_DEVID_THROTTLE_THERMAL_POLICY;
> diff --git a/include/linux/platform_data/x86/asus-wmi.h b/include/linux/platform_data/x86/asus-wmi.h
> index 66c7ab35d6c..1f7efaf0984 100644
> --- a/include/linux/platform_data/x86/asus-wmi.h
> +++ b/include/linux/platform_data/x86/asus-wmi.h
> @@ -57,7 +57,7 @@
> #define ASUS_WMI_DEVID_MUTE_LED 0x0004001C
>
> /* Disable Camera LED */
> -#define ASUS_WMI_DEVID_CAMERA_LED_NEG 0x00060078 /* 0 = on (unused) */
> +#define ASUS_WMI_DEVID_CAMERA_LED_NEG 0x00060078 /* 0 = on */
> #define ASUS_WMI_DEVID_CAMERA_LED 0x00060079 /* 1 = on */
>
> /* Backlight and Brightness */
>
> ---
> base-commit: a362539b42193dcdb17f8fba40031a515c53885c
> change-id: 20261017-asus-wmi-camera-led-06a6e05f01e2
>
> Best regards,
> --
> Zane Hunt <git@turtledev.nz>
>
next prev parent reply other threads:[~2026-11-16 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 18:37 Zane Hunt via B4 Relay
2026-11-16 18:51 ` Rong Zhang [this message]
2026-11-16 22:14 ` José Guilherme de Castro Rodrigues
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=173bed0f4e42a85087766a8e8cce8557115f2ccf.camel@rong.moe \
--to=i@rong.moe \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=git@turtledev.nz \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jose.guilherme.cr.bh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--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
all inboxes | Powered by JetHome®