diff options
author | Corentin Chary <corentin.chary@gmail.com> | 2011-12-15 08:27:34 +0100 |
---|---|---|
committer | Matthew Garrett <mjg@redhat.com> | 2012-03-20 12:02:16 -0400 |
commit | 774b06780be20d07c5459becd6495c04523a93a2 (patch) | |
tree | fc91522465fd85a9e48f6736545214e2fd60eca8 /lib | |
parent | 40969c7dd6298718820e0818b5b5acef7b24923d (diff) | |
download | linux-next-774b06780be20d07c5459becd6495c04523a93a2.tar.gz |
asus-laptop: control how BLED and WLED should be exposed
Let the user tells if BLED and WLED should be exposed as led or
rfkill (the old sysfs are still here, but this adds a standard
interface to control the device).
For example on my A6JC, with WAPF=1, I would do:
$ modprobe asus-laptop wled_type=led bluetooth_type=rfkill
There is still no known way to automatically guess what BLED
and WLED methods will control, it's why user information is needed.
A userspace database could do that automatically, and maybe some DMI
matching in the driver.
Signed-off-by: Corentin Chary <corentin.chary@gmail.com>
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions