Bug 197829 - Keyboard backlight support on Hewlett-Packard NB via sysfs class kbd_backlight
Summary: Keyboard backlight support on Hewlett-Packard NB via sysfs class kbd_backlight
Status: RESOLVED WILL_NOT_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Platform_x86 (show other bugs)
Hardware: All Linux
: P2 normal
Assignee: Hans de Goede
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-10 01:05 UTC by k3dAR7
Modified: 2020-10-27 14:50 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.13
Subsystem:
Regression: No
Bisected commit-id:


Attachments
DSDT from HP 8570w (129.76 KB, application/octet-stream)
2017-11-10 01:23 UTC, k3dAR7
Details
DSDT from HP 8570w - Decompiled (836.93 KB, text/plain)
2017-11-10 01:27 UTC, k3dAR7
Details
acpidump (684.02 KB, text/plain)
2017-11-11 02:16 UTC, k3dAR7
Details
lspci (33.76 KB, text/plain)
2017-11-11 02:16 UTC, k3dAR7
Details
dmidecode (11.22 KB, text/plain)
2017-11-11 02:18 UTC, k3dAR7
Details
acpi devices status (555 bytes, text/plain)
2017-11-11 02:19 UTC, k3dAR7
Details
dmesg (160.59 KB, text/plain)
2017-11-11 02:19 UTC, k3dAR7
Details

Description k3dAR7 2017-11-10 01:05:47 UTC
Can anyone please try add support for controlling keyboard backlight
via sysfs on Hewlett-Packard notebooks?

Maybe in a similar way as this last year patch for Thinkpad?
https://lkml.org/lkml/2015/12/24/295
https://github.com/torvalds/linux/commit/bb28f3d51ff5e1be541d057708011cc1efe6fae9

Of course, if anyone have knowledge and time, but not have real Hewlett-Packard with backlighted keyboard, i can do any test with "HP EliteBook 8570w", apply any patch on kernel tree, compile and try on this notebook (or maybe also on another HP).
Also if help any log or information i post it here...

BTW: This functionality is already supported (minimaly) on Apple,
ASUS, Dell, Samsung, Sony, Thinkpad, Toshiba

Many thanks :-)
Comment 1 k3dAR7 2017-11-10 01:23:42 UTC
Created attachment 260589 [details]
DSDT from HP 8570w

Acquired by: cat /sys/firmware/acpi/tables/DSDT > HP-8570w-DSDT.dat
Comment 2 k3dAR7 2017-11-10 01:27:13 UTC
Created attachment 260591 [details]
DSDT from HP 8570w - Decompiled

Acquired by: iasl -d HP-8570w-DSDT.dat
Comment 3 Andy Shevchenko 2017-11-10 16:14:32 UTC
Usually I ask for the following set:

1. % acpidump -o tables.dat # tables.dat is point of interest
2. % lspci -vv -nk # output of the command
3. % dmidecode # output of the command
4. % grep -H 15 /sys/bus/acpi/devices/*/status # output of the command
5. % dmesg # when kernel command line has the 'ignore_loglevel initcall_debug' added

So, it would be nice to have if possible.
Comment 4 k3dAR7 2017-11-11 02:10:26 UTC
@Andy thanks for answer, all files added in next attachments...
Comment 5 k3dAR7 2017-11-11 02:16:14 UTC
Created attachment 260601 [details]
acpidump
Comment 6 k3dAR7 2017-11-11 02:16:31 UTC
Created attachment 260603 [details]
lspci
Comment 7 k3dAR7 2017-11-11 02:18:09 UTC
Created attachment 260605 [details]
dmidecode
Comment 8 k3dAR7 2017-11-11 02:19:15 UTC
Created attachment 260607 [details]
acpi devices status
Comment 9 k3dAR7 2017-11-11 02:19:35 UTC
Created attachment 260609 [details]
dmesg
Comment 10 Hans de Goede 2020-10-27 14:50:08 UTC
k3dAR7, adding support for something like this without direct, physical access to the hardware is pretty hard to do.

I appreciate that you have provided all the info Andy requested and it is perhaps possible to attempt to create/modify a driver for kbd backlight control with that info, but without access to the hardware to fiddle around how things work this is going to be a really painful process.

On top of that this will also take a lot of time to do. As the lingering of this bug since November 2017 has shown no-one really has that time.

If you still have this laptop and are still interested in getting some support for kbd-backlight control added to Linux, your best bet is to find a local kernel hobbiest who has the time and will to look into this and provide that person access to your laptop.

I'm going to close this bug (sorry) because I do not really see this bug going anywhere.

Note You need to log in before you can comment on or make changes to this bug.