[Bug 221752] New: asus-wmi: no camera LED classdev registered on Zenbook S 14 UX5406SA (micmute LED works)

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=221752

            Bug ID: 221752
           Summary: asus-wmi: no camera LED classdev registered on Zenbook
                    S 14 UX5406SA (micmute LED works)
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: plattform@roninmail.cc
        Regression: No

Created attachment 310450
  --> https://bugzilla.kernel.org/attachment.cgi?id=310450&action=edit
CLI with information I guessed you might need.

Hardware
ASUS Zenbook S 14, UX5406SA_UX5406SA
BIOS UX5406SA.303, 11/08/2024
Fedora 44, kernel 7.1.3-200.fc44.x86_64, KDE Plasma (Wayland)
Secure Boot enabled (kernel lockdown active)
Description
The Fn camera key correctly toggles the internal camera at the firmware level:
when disabled, /dev/video0 cannot be opened; when enabled, it streams normally.
The keypress is delivered to userspace.
However, the camera indicator LED is never driven under Linux. It remains dark
regardless of camera state. The user therefore has a functional privacy toggle
with no working indicator.
Key observation
asus-wmi registers and correctly drives a LED classdev for micmute on this
machine, but registers nothing for the camera:
$ ls /sys/class/leds/
asus::kbd_backlight  platform::micmute  phy0-led
input2::capslock  input2::numlock  input2::scrolllock
input25::*  input28::*  input29::*
Same driver, same EC, same machine — one indicator is wired up, the other is
not.
Additional data

/sys/class/firmware-attributes/asus-armoury/attributes/ contains only
charge_mode and pending_reboot.
asus-wmi debugfs is unavailable under Secure Boot (lockdown), so
ASUS_WMI_DEVID_CAMERA (0x00060013) could not be probed via DSTS/DEVS.
v4l2-ctl -d /dev/video0 -L reports privacy with flags=read-only, value=0 — the
UVC privacy control is not the mechanism in use.

dmesg (asus)
asus_wmi: Initialization: 0x1
asus_wmi: BIOS WMI version: 9.4
asus_wmi: SFUN value: 0x21
asus-nb-wmi asus-nb-wmi: Detected ATK, not ASUSWMI, use DSTS
input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input15
asus_armoury: No matching power limits found for this system
asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -19
Note: the LED was previously stuck permanently lit; a cold boot cleared it and
it has not lit since. This is consistent with a latched EC state and no
kernel-driven LED path in either direction.
Possibly related: the S5406SA (same generation) has a reported asus-wmi issue
traced to missing LED plumbing (Launchpad #2092283).
Request: register a camera LED classdev for this model, as is done for micmute,
so the camera privacy indicator reflects actual camera state.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.