linux-toradex.git/drivers/platform, branch v2.6.33.2

classmate-laptop: use a single MODULE_DEVICE_TABLE to get correct aliases

2010-04-01T23:02:14+00:00

commit 02e77a55f7b7e36888e39c62439fedb90ae4e808 upstream.

Instead of a MODULE_DEVICE_TABLE for every acpi_driver ids table, we
create a table containing all ids to export to get a module alias for
each one.

This will fix automatic loading of the driver when one of the ACPI
devices is not present (like the accelerometer, which is not present in
some models).

Signed-off-by: Thadeu Lima de Souza Cascardo 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: lock down video output state access

2010-03-15T16:06:48+00:00

commit b525c06cdbd8a3963f0173ccd23f9147d4c384b5 upstream.

Given the right combination of ThinkPad and X.org, just reading the
video output control state is enough to hard-crash X.org.

Until the day I somehow find out a model or BIOS cut date to not
provide this feature to ThinkPads that can do video switching through
X RandR, change permissions so that only processes with CAP_SYS_ADMIN
can access any sort of video output control state.

This bug could be considered a local DoS I suppose, as it allows any
non-privledged local user to cause some versions of X.org to
hard-crash some ThinkPads.

Reported-by: Jidanni 
Signed-off-by: Henrique de Moraes Holschuh 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: fix bluetooth/wwan resume

2010-03-15T16:06:47+00:00

commit 08fedfc903c78e380b0baa7b57c52d367794d0a5 upstream.

Studying the DSDTs of various thinkpads, it looks like bit 3 of the
argument to SBDC and SWAN is not "set radio to last state on resume".
Rather, it seems to be "if this bit is set, enable radio on resume,
otherwise disable it on resume".

So, the proper way to prepare the radios for S3 suspend is: disable
radio and clear bit 3 on the SBDC/SWAN call to to resume with radio
disabled, and enable radio and set bit 3 on the SBDC/SWAN call to
resume with the radio enabled.

Also, for persistent devices, the rfkill core does not restore state,
so we really need to get the firmware to do the right thing.

We don't sync the radio state on suspend, instead we trust the BIOS to
not do anything weird if we never touched the radio state since boot.
Time will tell if that's a wise way of doing things...

Signed-off-by: Henrique de Moraes Holschuh 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: make driver events work in NVRAM poll mode

2010-03-15T16:06:47+00:00

commit 7f0cf712a74fcc3ad21f0bde95bd32c2f2cc3888 upstream.

Thadeu Lima de Souza Cascardo reports this:

Brightness notification does not work until the user writes to
hotkey_mask attribute.  That's because the polling thread will only run
if hotkey_user_mask is set and someone is reading the input device or
if hotkey_driver_mask is set.  In this second case, this condition is
not tested after the mask is changed, because the brightness and
volume drivers are started after the hotkey drivers.

Fix tpacpi_hotkey_driver_mask_set() to call hotkey_poll_setup(), so
that the poller kthread will be started when needed.

Reported-by: Thadeu Lima de Souza Cascardo 
Tested-by: Thadeu Lima de Souza Cascardo 
Signed-off-by: Henrique de Moraes Holschuh 
Cc: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: document HKEY event 3006

2010-03-15T16:06:46+00:00

commit bf8b29c8f7f8269e99eca8b19048ed5b34b51810 upstream.

Event 0x3006 is used to help power management of the ODD in the
UltraBay.  The EC generates this event when the ODD eject button is
pressed (even if the bay is powered down).

Normally, Linux doesn't need this as we keep the SATA link powered
up (which wastes power).  The EC powers up the bay by itself when the
ODD eject button is pressed, and the SATA PHY reports the hotplug.

However, we could also power that SATA link down (and for that matter,
also power down the Ultrabay) if the ODD is left idle for a while with
no disk inside, and use event 0x3006 to know when we need that SATA link
powered back up.

For now, just stop asking for more information when event 0x3006 is
seen, there is no point in pestering users about it anymore.

Signed-off-by: Henrique de Moraes Holschuh 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: R52 brightness_mode has been confirmed

2010-03-15T16:06:46+00:00

commit 7d1894d8d1c411d2dad95abfe0f65bacf68c4afa upstream.

We can stop pestering users for confirmation of the brightness_mode
default for firmware TP-76.

While at it, add a few missing comments in that quirk table.

Reported-by: Whoopie 
Signed-off-by: Henrique de Moraes Holschuh 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: fix poll thread auto-start

2010-03-15T16:06:44+00:00

commit b589ea4c44170d3f7a845684e2d1b3b9571663af upstream.

The driver was not starting the NVRAM polling thread if the input
device was bound immediately after registration.

This fixes:
http://bugzilla.kernel.org/show_bug.cgi?id=15118

Reported-by: Florian Zumbiehl 
Signed-off-by: Henrique de Moraes Holschuh 
Signed-off-by: Greg Kroah-Hartman

eeepc-laptop: disable wireless hotplug for 1005PE

2010-03-15T16:06:43+00:00

commit ced69c59811f05b2f8378467cbb82ac6ed3c6a5a upstream.

The wireless hotplug code is not needed on this model, and it disables
the wired ethernet card.  (Like on the 1005HA and 1201N).

References: 

Signed-off-by: Alan Jenkins 
Reported-by: Ansgar Burchardt 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: fix ALSA callback return status

2010-03-15T16:06:21+00:00

commit 88cc83772a3c7756b9f2b4ba835545ad90a08409 upstream.

Clemens Ladisch reports that thinkpad-acpi improperly implements the
ALSA API, and always returns 0 for success for the "put" callbacks
while the API requires it to return "1" when the control value has
been changed in the hardware/firmware.

Rework the volume subdriver to be able to properly implement the ALSA
API.  Based on a patch by Clemens Ladisch .

This fix is also needed on 2.6.33.

Reported-by: Clemens Ladisch 
Signed-off-by: Henrique de Moraes Holschuh 
Signed-off-by: Greg Kroah-Hartman

acer-wmi: Respect current backlight level when loading

2010-02-19T05:19:26+00:00

Set the backlight to use the current brightness when loaded, rather than
always resetting the backlight to maximum brightness.

Fixes kernel bugzilla #14207

Signed-off-by: Carlos Corbacho 
Reported-by: Denis Mukhin 
Signed-off-by: Len Brown