ACPI / x86: Revert: Make PWM2 device always present at Lenovo Yoga Book
PATCH 1/1 ACPI / x86: Revert: Make PWM2 device always present at Lenovo Yoga Book
It turns out that there is a WMI object which controls the PWM2 device used for the keyboard backlight and that WMI object also provides some other useful functionality.
The upcoming lenovo-yogabook-wmi driver will offer both backlight control and the other functionality, so there no longer is a need to have the lpss-pwm driver binding to PWM2 for backlight control; and this is now actually undesirable because this will cause both the WMI code and the lpss-pwm driver to poke at the same PWM controller.
Revert commit ff6cdfd71495 ("ACPI / x86: Make PWM2 device always present at Lenovo Yoga Book"), removing the always-present quirk for the PWM2 ACPI-device, so that the lpss-pwm controller will no longer bind to it.
--- drivers/acpi/x86/utils.c | 4 ---- 1 file changed, 4 deletions(-)
drivers/acpi/x86/utils.c +0 -4
@@ -54,10 +54,6 @@ static const struct always_present_id always_present_ids[] = { ENTRY("80860F09", "1", X86_MATCH(ATOM_SILVERMONT), {}), ENTRY("80862288", "1", X86_MATCH(ATOM_AIRMONT), {}), -/* Lenovo Yoga Book uses PWM2 for keyboard backlight control */ - ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { - DMI_MATCH(DMI_PRODUCT_NAME, "Lenovo YB1-X9"), - }),/* The Xiaomi Mi Pad 2 uses PWM2 for touchkeys backlight control */ ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { DMI_MATCH(DMI_SYS_VENDOR, "Xiaomi Inc"),
Signature · 1 line
2.31.1
Quoted 10 lines · Hans de Goede
It turns out that there is a WMI object which controls the PWM2 device used for the keyboard backlight and that WMI object also provides some other useful functionality.
The upcoming lenovo-yogabook-wmi driver will offer both backlight control and the other functionality, so there no longer is a need to have the lpss-pwm driver binding to PWM2 for backlight control; and this is now actually undesirable because this will cause both the WMI code and the lpss-pwm driver to poke at the same PWM controller.
Quoted 29 lines
Revert commit
ff6cdfd71495("ACPI / x86: Make PWM2 device always present at Lenovo Yoga Book"), removing the always-present quirk for the PWM2 ACPI-device, so that the lpss-pwm controller will no longer bind to it.Cc Yauhen Kharuzhy <[email protected]>Signed-off-by Hans de Goede <[email protected]>--- drivers/acpi/x86/utils.c | 4 ---- 1 file changed, 4 deletions(-)drivers/acpi/x86/utils.c +0
-4@@ -54,10 +54,6 @@ static const struct always_present_id always_present_ids[] = { ENTRY("80860F09", "1", X86_MATCH(ATOM_SILVERMONT), {}), ENTRY("80862288", "1", X86_MATCH(ATOM_AIRMONT), {}), -/* Lenovo Yoga Book uses PWM2 for keyboard backlight control */ - ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { - DMI_MATCH(DMI_PRODUCT_NAME, "Lenovo YB1-X9"), - }),/* The Xiaomi Mi Pad 2 uses PWM2 for touchkeys backlight control */ ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { DMI_MATCH(DMI_SYS_VENDOR, "Xiaomi Inc"),Signature · 1 line
2.31.1
Signature · 1 line
Yauhen Kharuzhy
Quoted 34 lines · Yauhen Kharuzhy
Quoted 10 lines · Hans de Goede
It turns out that there is a WMI object which controls the PWM2 device used for the keyboard backlight and that WMI object also provides some other useful functionality.
The upcoming lenovo-yogabook-wmi driver will offer both backlight control and the other functionality, so there no longer is a need to have the lpss-pwm driver binding to PWM2 for backlight control; and this is now actually undesirable because this will cause both the WMI code and the lpss-pwm driver to poke at the same PWM controller.
Acked-by Yauhen Kharuzhy <[email protected]>Quoted 19 lines
Revert commit
ff6cdfd71495("ACPI / x86: Make PWM2 device always present at Lenovo Yoga Book"), removing the always-present quirk for the PWM2 ACPI-device, so that the lpss-pwm controller will no longer bind to it.Cc Yauhen Kharuzhy <[email protected]>Signed-off-by Hans de Goede <[email protected]>--- drivers/acpi/x86/utils.c | 4 ---- 1 file changed, 4 deletions(-)drivers/acpi/x86/utils.c +0
-0@@ -54,10 +54,6 @@ static const struct always_present_id always_present_ids[] = {ENTRY ("80860F09" ,"1" ,X86_MATCH (ATOM_SILVERMONT ), {}), ENTRY("80862288", "1", X86_MATCH(ATOM_AIRMONT), {}),
Quoted 8 lines
drivers/acpi/x86/utils.c static const struct always_present_id always_present_ids[] = {
Quoted 8 lines
drivers/acpi/x86/utils.c +0
-5-/* Lenovo Yoga Book uses PWM2 for keyboard backlight control */ - ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { - DMI_MATCH(DMI_PRODUCT_NAME, "Lenovo YB1-X9"), - }),/* The Xiaomi Mi Pad 2 uses PWM2 for touchkeys backlight control */ ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { DMI_MATCH(DMI_SYS_VENDOR, "Xiaomi Inc"), --
Applied as 5.16-rc2 material, thanks!
Rafael J. Wysocki
maintainerQuoted 36 lines · Rafael J. Wysocki
Quoted 34 lines · Yauhen Kharuzhy
Quoted 10 lines · Hans de Goede
It turns out that there is a WMI object which controls the PWM2 device used for the keyboard backlight and that WMI object also provides some other useful functionality.
The upcoming lenovo-yogabook-wmi driver will offer both backlight control and the other functionality, so there no longer is a need to have the lpss-pwm driver binding to PWM2 for backlight control; and this is now actually undesirable because this will cause both the WMI code and the lpss-pwm driver to poke at the same PWM controller.
Acked-by Yauhen Kharuzhy <[email protected]>Quoted 19 lines
Revert commit
ff6cdfd71495("ACPI / x86: Make PWM2 device always present at Lenovo Yoga Book"), removing the always-present quirk for the PWM2 ACPI-device, so that the lpss-pwm controller will no longer bind to it.Cc Yauhen Kharuzhy <[email protected]>Signed-off-by Hans de Goede <[email protected]>--- drivers/acpi/x86/utils.c | 4 ---- 1 file changed, 4 deletions(-)drivers/acpi/x86/utils.c +0
-0@@ -54,10 +54,6 @@ static const struct always_present_id always_present_ids[] = {ENTRY ("80860F09" ,"1" ,X86_MATCH (ATOM_SILVERMONT ), {}), ENTRY("80862288", "1", X86_MATCH(ATOM_AIRMONT), {}),
Quoted 10 lines
Quoted 8 lines
drivers/acpi/x86/utils.c static const struct always_present_id always_present_ids[] = {
Quoted 8 lines
drivers/acpi/x86/utils.c +0
-5-/* Lenovo Yoga Book uses PWM2 for keyboard backlight control */ - ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { - DMI_MATCH(DMI_PRODUCT_NAME, "Lenovo YB1-X9"), - }),/* The Xiaomi Mi Pad 2 uses PWM2 for touchkeys backlight control */ ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { DMI_MATCH(DMI_SYS_VENDOR, "Xiaomi Inc"), --Applied as 5.16-rc2 material, thanks!
I've decided to make this change in 5.17.
It would be good to put the patch under a different subject too, because the way it is may confuse someone to regard it as a fix.
Hi,
Quoted 48 lines · Rafael J. Wysocki
Quoted 36 lines · Rafael J. Wysocki
Quoted 34 lines · Yauhen Kharuzhy
Quoted 10 lines · Hans de Goede
It turns out that there is a WMI object which controls the PWM2 device used for the keyboard backlight and that WMI object also provides some other useful functionality.
The upcoming lenovo-yogabook-wmi driver will offer both backlight control and the other functionality, so there no longer is a need to have the lpss-pwm driver binding to PWM2 for backlight control; and this is now actually undesirable because this will cause both the WMI code and the lpss-pwm driver to poke at the same PWM controller.
Acked-by Yauhen Kharuzhy <[email protected]>Quoted 19 lines
Revert commit
ff6cdfd71495("ACPI / x86: Make PWM2 device always present at Lenovo Yoga Book"), removing the always-present quirk for the PWM2 ACPI-device, so that the lpss-pwm controller will no longer bind to it.Cc Yauhen Kharuzhy <[email protected]>Signed-off-by Hans de Goede <[email protected]>--- drivers/acpi/x86/utils.c | 4 ---- 1 file changed, 4 deletions(-)drivers/acpi/x86/utils.c +0
-0@@ -54,10 +54,6 @@ static const struct always_present_id always_present_ids[] = {ENTRY ("80860F09" ,"1" ,X86_MATCH (ATOM_SILVERMONT ), {}), ENTRY("80862288", "1", X86_MATCH(ATOM_AIRMONT), {}),Quoted 10 lines
Quoted 8 lines
drivers/acpi/x86/utils.c static const struct always_present_id always_present_ids[] = {
Quoted 8 lines
drivers/acpi/x86/utils.c +0
-5-/* Lenovo Yoga Book uses PWM2 for keyboard backlight control */ - ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { - DMI_MATCH(DMI_PRODUCT_NAME, "Lenovo YB1-X9"), - }),/* The Xiaomi Mi Pad 2 uses PWM2 for touchkeys backlight control */ ENTRY("80862289", "2", X86_MATCH(ATOM_AIRMONT), { DMI_MATCH(DMI_SYS_VENDOR, "Xiaomi Inc"), --Applied as 5.16-rc2 material, thanks!
Quoted 1 line
I've decided to make this change in 5.17.
That is fine, the WMI driver won't land before then anyways.
Quoted 2 lines
It would be good to put the patch under a different subject too, because the way it is may confuse someone to regard it as a fix.
Ack, I will send a v2 with a commit msg which makes it less likely this gets picked into a stable series.
Note if it does end up in a stable series that is fine too, there were plans to use the LPSS PWM driver to driver the kbd backlight but those were never fulfilled so the ACPI PWM device getting its default _STA return of 0 back on older kernels will not matter.
Regards,
Hans