diff options
| author | AceLan Kao <acelan.kao@canonical.com> | 2012-03-20 09:53:08 +0100 |
|---|---|---|
| committer | Matthew Garrett <mjg@redhat.com> | 2012-03-26 15:05:41 -0400 |
| commit | c87992d1fa51a6a3d8f0e980ca4d2bdec7e78a17 (patch) | |
| tree | c702643e69183fcc5cb5f5b8b4f1e429ff1366fb /drivers/platform/x86/asus-nb-wmi.c | |
| parent | bde9e5098c121cfca6d9c7e3a26e6ae44a3c9632 (diff) | |
| download | op-kernel-dev-c87992d1fa51a6a3d8f0e980ca4d2bdec7e78a17.zip op-kernel-dev-c87992d1fa51a6a3d8f0e980ca4d2bdec7e78a17.tar.gz | |
asus-wmi: add scalar board brightness adj. support
Some ASUS ET2012E/I All-in-One machines that use a scalar board
to control the brightness, and they only accept brightness up and down
command. So, I introduced a get_scalar_command() function to pass the
command to the scalar board through WMI.
Besides, we have to store the brightness value locally, for we need the
old value to know the brightness value is increasing or decreasing.
BTW, since there is no way to retrieve the actual brightness(it would be
a fixed value), and the max brightness value would be fixed to 1, so we
have to keep passing the brightness up/down command when we reached the
max brightness value or 0.
Signed-off-by: AceLan Kao <acelan.kao@canonical.com>
Signed-off-by: Corentin Chary <corentin.chary@gmail.com>
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Diffstat (limited to 'drivers/platform/x86/asus-nb-wmi.c')
| -rw-r--r-- | drivers/platform/x86/asus-nb-wmi.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/platform/x86/asus-nb-wmi.c b/drivers/platform/x86/asus-nb-wmi.c index 3501127..1aea6b8 100644 --- a/drivers/platform/x86/asus-nb-wmi.c +++ b/drivers/platform/x86/asus-nb-wmi.c @@ -101,7 +101,7 @@ static struct asus_wmi_driver asus_nb_wmi_driver = { .keymap = asus_nb_wmi_keymap, .input_name = "Asus WMI hotkeys", .input_phys = ASUS_NB_WMI_FILE "/input0", - .quirks = asus_nb_wmi_quirks, + .detect_quirks = asus_nb_wmi_quirks, }; |
