On Tue, 08 Nov 2016, Hui Wang wrote: > laptops are not released to market yet), the issue is that the > thinkpad_acpi.ko can't be automatically loaded as before. > > Through debugging, we found the HKEY_HID is LEN0268 instead of > LEN0068 on those machines, and the MHKV is 0x200 instead of > 0x100. So adding the new ID into the driver. This usually means Lenovo expects to have different windows drivers. Does thinkpad-acpi work properly on these new thinkpads? If it does, you have my Acked-by: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx> > Signed-off-by: Hui Wang <hui.wang@xxxxxxxxxxxxx> > --- > drivers/platform/x86/thinkpad_acpi.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/platform/x86/thinkpad_acpi.c b/drivers/platform/x86/thinkpad_acpi.c > index b65ce75..dbd2e27 100644 > --- a/drivers/platform/x86/thinkpad_acpi.c > +++ b/drivers/platform/x86/thinkpad_acpi.c > @@ -128,6 +128,7 @@ enum { > /* ACPI HIDs */ > #define TPACPI_ACPI_IBM_HKEY_HID "IBM0068" > #define TPACPI_ACPI_LENOVO_HKEY_HID "LEN0068" > +#define TPACPI_ACPI_LENOVO_HKEY_V2_HID "LEN0268" > #define TPACPI_ACPI_EC_HID "PNP0C09" > > /* Input IDs */ > @@ -4143,6 +4144,7 @@ static int hotkey_write(char *buf) > static const struct acpi_device_id ibm_htk_device_ids[] = { > {TPACPI_ACPI_IBM_HKEY_HID, 0}, > {TPACPI_ACPI_LENOVO_HKEY_HID, 0}, > + {TPACPI_ACPI_LENOVO_HKEY_V2_HID, 0}, > {"", 0}, > }; -- Henrique Holschuh -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html