linux-toradex.git/drivers/platform/x86/eeepc-wmi.c, branch v4.1

eeepc-wmi: Constify asus_quirks[] DMI table

2014-08-16T08:23:52+00:00

Constify the asus_quirks[] DMI table. There's no need to have it
writeable during runtime.

Signed-off-by: Mathias Krause 
Cc: Corentin Chary 
Signed-off-by: Matthew Garrett

ACPI: Clean up inclusions of ACPI header files

2013-12-07T00:03:14+00:00

Replace direct inclusions of ,  and
, which are incorrect, with 
inclusions and remove some inclusions of those files that aren't
necessary.

First of all, ,  and 
should not be included directly from any files that are built for
CONFIG_ACPI unset, because that generally leads to build warnings about
undefined symbols in !CONFIG_ACPI builds.  For CONFIG_ACPI set,
 includes those files and for CONFIG_ACPI unset it
provides stub ACPI symbols to be used in that case.

Second, there are ordering dependencies between those files that always
have to be met.  Namely, it is required that  be included
prior to  so that the acpi_pci_root declarations the
latter depends on are always there.  And  which provides
basic ACPICA type declarations should always be included prior to any other
ACPI headers in CONFIG_ACPI builds.  That also is taken care of including
 as appropriate.

Signed-off-by: Lv Zheng 
Cc: Greg Kroah-Hartman 
Cc: Matthew Garrett 
Cc: Tony Luck 
Cc: "H. Peter Anvin" 
Acked-by: Bjorn Helgaas  (drivers/pci stuff)
Acked-by: Konrad Rzeszutek Wilk  (Xen stuff)
Signed-off-by: Rafael J. Wysocki

asus-wmi: always report brightness key events

2013-02-27T13:30:37+00:00

Signed-off-by: Corentin Chary 
Signed-off-by: Matthew Garrett

Corentin has moved

2012-12-18T01:15:14+00:00

Signed-off-by: Corentin Chary 
Cc: Matthew Garrett 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

asus-wmi: control backlight power through WMI, not ACPI

2012-07-28T04:11:49+00:00

BugLink: https://bugs.launchpad.net/bugs/1000146

Some h/w that can adjust screen brightness through ACPI functions, but
can't turn on/off the backlight power correctly. So, we list those h/w in
quirks and try to turn on/off the backlight power through WMI.
Signed-off-by: AceLan Kao 
Signed-off-by: Corentin Chary 
Signed-off-by: Matthew Garrett

eeepc-wmi: split et2012 specific hacks

2012-03-26T19:05:49+00:00

Signed-off-by: Corentin Chary 
Signed-off-by: Matthew Garrett

eeepc-wmi: refine quirks handling

2012-03-26T19:05:47+00:00

Signed-off-by: Corentin Chary 
Signed-off-by: Matthew Garrett

asus-wmi: move WAPF variable into quirks_entry

2012-03-26T19:05:44+00:00

Some models work better with different values of wapf, so move the
variable into quriks_entry to make it more easy to give a specific
value to different models.

Based on original patch from AceLan Kao 

Cc: AceLan Kao 
Signed-off-by: Corentin Chary 
Signed-off-by: Matthew Garrett

asus-wmi: store backlight power status for AIO machine

2012-03-26T19:05:43+00:00

Due to some implementation reasons, ASUS ET2012 All-in-One machines
can't report the correct backlight power status, it will always return
1. To track the backlight power status correctly, we have to store the
status by ourselves.

BTW, by the BIOS design, the backlight power will be turn on/off
sequently, no matter what the value of the parameter will be.
More over, the brightness adjustment command will turn on the backlight
power. Those behaviors will make us fail to track the backlight power
status.
For example, While we are trying to turn on the backlight power,
we will send out the brightness adjustment command and then trying to
figure out if we have to turn on the backlight power, then send out
the command. But, the real case is that, the backlight power turns on
while sending the brightness adjustment command, and then we send out
the command to turn on the backlight power, it actually will turn off
the backlight power and the backlight power status we recorded becomes
wrong. So, we have to seperate these two commands by a if statement.

Signed-off-by: AceLan Kao 
Signed-off-by: Corentin Chary 
Signed-off-by: Matthew Garrett

asus-wmi: add scalar board brightness adj. support

2012-03-26T19:05:41+00:00

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 
Signed-off-by: Corentin Chary 
Signed-off-by: Matthew Garrett