summaryrefslogtreecommitdiffstats
path: root/drivers/platform/x86/thinkpad_acpi.c
diff options
context:
space:
mode:
authorMaximilian Luz <luzmaximilian@gmail.com>2022-05-27 04:34:47 +0200
committerHans de Goede <hdegoede@redhat.com>2022-06-13 17:25:09 +0200
commit7518eefeb7ad55ca2126ebdd6369490b9dc5e7a8 (patch)
treee31b3abd5c9f5d581b1c433718cd8521a53a1811 /drivers/platform/x86/thinkpad_acpi.c
parentd420185489e52f414b18cef10487279a9a005b27 (diff)
downloadlinux-stable-7518eefeb7ad55ca2126ebdd6369490b9dc5e7a8.tar.gz
linux-stable-7518eefeb7ad55ca2126ebdd6369490b9dc5e7a8.tar.bz2
linux-stable-7518eefeb7ad55ca2126ebdd6369490b9dc5e7a8.zip
platform/surface: aggregator_registry: Add support for keyboard cover on Surface Pro 8
Add support for the detachable keyboard cover on the Surface Pro 8. The keyboard cover on the Surface Pro 8 is, unlike the keyboard covers of earlier Surface Pro generations, handled via the Surface System Aggregator Module (SSAM). The keyboard and touchpad (as well as other HID input devices) of this cover are standard SSAM HID client devices (just like keyboard and touchpad on e.g. the Surface Laptop 3 and 4), however, some care needs to be taken as they can be physically detached (similarly to the Surface Book 3). Specifically, the respective SSAM client devices need to be removed when the keyboard cover has been detached and (re-)initialized when the keyboard cover has been (re-)attached. On the Surface Pro 8, detachment of the keyboard cover (and by extension its devices) is managed via the KIP subsystem. Therefore, said devices need to be registered under the KIP device hub, which in turn will remove and re-create/re-initialize those devices as needed. Signed-off-by: Maximilian Luz <luzmaximilian@gmail.com> Link: https://lore.kernel.org/r/20220527023447.2460025-13-luzmaximilian@gmail.com Reviewed-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Diffstat (limited to 'drivers/platform/x86/thinkpad_acpi.c')
0 files changed, 0 insertions, 0 deletions