diff options
author | Kai-Heng Feng <kai.heng.feng@canonical.com> | 2024-03-08 13:32:55 +0800 |
---|---|---|
committer | Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> | 2024-03-12 12:55:57 +0200 |
commit | f7b7066508d69934e4545db0c709c98ce506df0c (patch) | |
tree | df0f1048c74b714b315745428ae0571a520e5eee /drivers/platform/x86/intel/pmc | |
parent | e9df5436fd61c8cf375ac086d936f90385cd6888 (diff) |
platform/x86: asus-wmi: Consider device is absent when the read is ~0
AAEON PICO-TGU4 board doesn't have any LED but there are bogus LED
controls under /sys/class/leds:
$ ls /sys/class/leds
asus::kbd_backlight asus::lightbar platform::micmute
The reason is that the ~0 read from asus_wmi_get_devstate() is treated
as a valid state, in truth it means the device is absent.
So filter out ~0 read to prevent bogus LED controls being created.
Signed-off-by: Kai-Heng Feng <kai.heng.feng@canonical.com>
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Link: https://lore.kernel.org/r/20240308053255.224496-1-kai.heng.feng@canonical.com
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Diffstat (limited to 'drivers/platform/x86/intel/pmc')
0 files changed, 0 insertions, 0 deletions