| Message ID | 1392381247-28109-1-git-send-email-mika.westerberg@linux.intel.com (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
diff --git a/drivers/acpi/video_detect.c b/drivers/acpi/video_detect.c index a697b77b8865..f0447d3daf2c 100644 --- a/drivers/acpi/video_detect.c +++ b/drivers/acpi/video_detect.c @@ -170,14 +170,6 @@ static struct dmi_system_id video_detect_dmi_table[] = { }, { .callback = video_detect_force_vendor, - .ident = "HP EliteBook Revolve 810", - .matches = { - DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"), - DMI_MATCH(DMI_PRODUCT_NAME, "HP EliteBook Revolve 810 G1"), - }, - }, - { - .callback = video_detect_force_vendor, .ident = "Lenovo Yoga 13", .matches = { DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
This reverts commit e18ac62fa4b3f16234bab0d5a6627c57dbae9e7e. The referenced commit added HP EliteBook Revolve 810 to the ACPI video detected blacklist so that only the native Intel backlight interface was exported. However, this turned to be wrong solution after all. The ACPI video interface works and as long as we only use that there are no problems. So we can revert this commit and stick to use the backlight interface provided by the ACPI video driver. (Using Intel native interface will not work after resume since the ACPI video driver will restore it's state which takes control over the native one. That's a separate thing and should be addressed in the ACPI video driver, I suppose.) References: https://bugzilla.kernel.org/show_bug.cgi?id=70231 Cc: Aaron Lu <aaron.lu@intel.com> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> --- Rafael, This turned out to be misunderstanding from my side. I should have investigated this further before submitting the original patch. Sorry about that. Aaron, Thanks for the investigation and pointing me to the right direction (e.g to use acpi_video0 over the native one). drivers/acpi/video_detect.c | 8 -------- 1 file changed, 8 deletions(-)