summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorDavid Stephenson <git@davidstephenson.net>2026-08-25 19:36:21 +0000
committerIlpo Järvinen <ilpo.jarvinen@linux.intel.com>2026-09-18 19:42:22 +0300
commit2782e0c22e155cc0852114dcf9bb98c209b06853 (patch)
treea117e81f357641b9b00f442fcda1cb3151d0e588 /tools/perf/scripts/python
parent9af7fddef448d649fa1332d86a14465a1d1fafe3 (diff)
downloadlinux-next-2782e0c22e155cc0852114dcf9bb98c209b06853.tar.gz
linux-next-2782e0c22e155cc0852114dcf9bb98c209b06853.zip
platform: arm64: thinkpad-t14s-ec: don't send KEY_KBDILLUMTOGGLE on Fn+Space
On the T14s, the EC already steps the keyboard backlight when you press Fn+Space: off, then low, then high. We report that change with t14s_kbd_bl_update() (brightness_hw_changed). We then also send KEY_KBDILLUMTOGGLE. The extra key is the problem. Desktops treat it as "please toggle the light." GNOME calls Keyboard.Toggle() and changes the LED itself. That fights the EC's three steps. The on-screen bar also stays empty, because Toggle() always returns 0%. thinkpad_acpi on x86 already skips the key when the firmware changed the light. It only uses brightness_hw_changed. Do the same here: keep the LED update, do not send KEY_KBDILLUMTOGGLE. Tested on a Lenovo ThinkPad T14s Gen 6 (21N1, Snapdragon X Elite) with GNOME. After this change the OSD bar tracks off / 50% / 100%. Signed-off-by: David Stephenson <git@davidstephenson.net> Reviewed-by: Sebastian Reichel <sre@kernel.org> Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com> Link: https://patch.msgid.link/20260825193556.133277-1-git@davidstephenson.net 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')
0 files changed, 0 insertions, 0 deletions