From: Mark Pearson <mpearson-len...@squebb.ca> New Lenovo platforms are adding the Fn + N key to generate system debug details that support can use for collecting important details on any customer cases for Windows. Add the infrastructure so we can do the same on Linux by sending a KEY_VENDOR keycode to userspace.
Signed-off-by: Mark Pearson <mpearson-len...@squebb.ca> Signed-off-by: Nitin Joshi <njos...@lenovo.com> Link: https://lore.kernel.org/r/20240417173124.9953-3-mpearson-len...@squebb.ca [hdego...@redhat.com: Adjust for switch to sparse-keymap keymaps] Signed-off-by: Hans de Goede <hdego...@redhat.com> --- drivers/platform/x86/thinkpad_acpi.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c index c7e2e85944ac..dd8873d61126 100644 --- a/drivers/platform/x86/thinkpad_acpi.c +++ b/drivers/platform/x86/thinkpad_acpi.c @@ -3267,6 +3267,7 @@ static const struct key_entry keymap_lenovo[] __initconst = { * after switching to sparse keymap support. The mappings above use translated * scancodes to preserve uAPI compatibility, see tpacpi_input_send_key(). */ + { KE_KEY, 0x131d, { KEY_VENDOR } }, /* System debug info, similar to old ThinkPad key */ { KE_KEY, TP_HKEY_EV_TRACK_DOUBLETAP /* 0x8036 */, { KEY_PROG4 } }, { KE_END } }; -- 2.44.0 _______________________________________________ ibm-acpi-devel mailing list ibm-acpi-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel
