| commit | 4564de172dcdce641c0d6c689e79e95b5f6bee2c | |
| author | Corentin Chary <corentincj@iksaif.net> | |
| Fri, 26 Jan 2007 13:04:40 +0000 (26 14:04 +0100) | ||
| committer | Len Brown <len.brown@intel.com> | |
| Tue, 30 Jan 2007 06:37:02 +0000 (30 01:37 -0500) | ||
| tree | a330a4c2ffd6f9a5c2349d99322f8599294b2711 | treesnapshot (tar.gz zip) |
| parent | be18cdabb8ed40ff4b8a240e0d6f4e6c30ff866d | commitdiff |
asus-laptop: add bluetooth and wlan support
WLED and BLED are not handled like other leds (MLED, etc ..),
because sometime they also control the wlan/bluetooth device.
If the method for wireless_status is found, it's used to get the
status, otherwise hotk->status is used. We also use the HWRS
method, which tell if the bluetooth/wlan device is present or not.
This patch show why we need a ASUS_SET_DEVICE_ATTR macro : if
there is a bluetooth device, /sys/dev.../asus-laptop/bluetooth
is usable, else it's not but it's clean.
Signed-off-by: Corentin Chary <corentincj@iksaif.net>
Signed-off-by: Len Brown <len.brown@intel.com>
WLED and BLED are not handled like other leds (MLED, etc ..),
because sometime they also control the wlan/bluetooth device.
If the method for wireless_status is found, it's used to get the
status, otherwise hotk->status is used. We also use the HWRS
method, which tell if the bluetooth/wlan device is present or not.
This patch show why we need a ASUS_SET_DEVICE_ATTR macro : if
there is a bluetooth device, /sys/dev.../asus-laptop/bluetooth
is usable, else it's not but it's clean.
Signed-off-by: Corentin Chary <corentincj@iksaif.net>
Signed-off-by: Len Brown <len.brown@intel.com>
| drivers/misc/asus-laptop.c | diffblobblamehistory |