diff options
| author | Denis Benato <denis.benato@linux.dev> | 2026-09-16 14:38:28 +0000 |
|---|---|---|
| committer | Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> | 2026-09-18 21:07:14 +0300 |
| commit | 854be60ed0e9f2b7729be3972da14e63d1058e95 (patch) | |
| tree | f1cbd4afe07802f37753b0b508da950bf777cbce /tools/perf/scripts/python/stackcollapse.py | |
| parent | 99215e618ff209ccfc01ec62ee58c4b3179a7435 (diff) | |
| download | linux-next-854be60ed0e9f2b7729be3972da14e63d1058e95.tar.gz linux-next-854be60ed0e9f2b7729be3972da14e63d1058e95.zip | |
platform/x86: asus-wmi: remove unused screenpad_brightness
Nothing reads asus->driver->screenpad_brightness anymore: the last
reader went away when the screenpad update path stopped relying on a
driver-side copy of the brightness, leaving only the write in
asus_screenpad_init(). ASUS_SCREENPAD_BRIGHT_DEFAULT became unused in
the same rework.
Drop the field from struct asus_wmi_driver, the write and the unused
define. Nothing in the current code depends on remembering the last
brightness while the panel is off; should a model turn up that needs
it (the original screenpad implementation did, and older DUO models
may behave differently from the hardware tested so far), the field can
be reintroduced then.
Assisted-by: zcode:glm-5.3-flash
Signed-off-by: Denis Benato <denis.benato@linux.dev>
Link: https://patch.msgid.link/20260916143838.170950-5-denis.benato@linux.dev
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions