linux-stable.git/drivers/platform, branch linux-2.6.31.y

acerhdf: limit modalias matching to supported

2010-01-06T22:26:13+00:00

commit bdc731bc5fcd1794e9ac8ac80c389d302381c123 upstream.

BugLink: https://bugs.launchpad.net/ubuntu/+bug/435958

The module alias currently matches any Acer computer but when loaded the
BIOS checks will only succeed on Aspire One models.  This causes a invalid
BIOS warning for all other models (seen on Aspire 4810T).  This is not
fatal but worries users that see this message.  Limiting the moule alias
to models starting with AOA or DOA for Packard Bell.

Signed-off-by: Stefan Bader 
Acked-by: Borislav Petkov 
Acked-by: Peter Feuerer 
Signed-off-by: Andrew Morton 
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: preserve rfkill state across suspend/resume

2009-12-18T21:44:22+00:00

commit 208b996b6c460285650d39b2330f8ef82c007d10 upstream.

Since the rfkill rework in 2.6.31, the driver is always resuming with
the radios disabled.

Change thinkpad-acpi to ask the firmware to resume with the radios in
the last state.  This fixes the Bluetooth and WWAN rfkill switches.

Note that it means we respect the firmware's oddities.  Should the
user toggle the hardware rfkill switch on and off, it might cause the
radios to resume enabled.

UWB is an unknown quantity since it has nowhere the same level of
firmware support (no control over state storage in NVRAM, for
example), and might need further fixing.  Testers welcome.

This change fixes a regression from 2.6.30.

Reported-by: Jerone Young 
Reported-by: Ian Molton 
Signed-off-by: Henrique de Moraes Holschuh 
Tested-by: Ian Molton 
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: fix default brightness_mode for R50e/R51

2009-12-18T21:44:22+00:00

commit a9f8eacca4e9e8693de9b896c1fa7aadaa9402e8 upstream.

According to a report, the R50e wants EC-based brightness control,
even if it uses an Intel GPU.  The current driver default was reported
to not work at all.

This bug can be worked around by the "brightness_mode=3" module
parameter.

Change the default of the R50e and R51 2xxx models (which use the same
EC firmware, 1V) to TPACPI_BRGHT_Q_EC, but keep TPACPI_BRGHT_Q_ASK set
for now, as I'd like to get more reports.

This fixes a regression caused by commit
59fe4fe34d7afdf63208124f313be9056feaa2f4,
"thinkpad-acpi: fix incorrect use of TPACPI_BRGHT_MODE_ECNVRAM"

Kernel 2.6.31 also needs this fix.

Reported-by: Ferenc Wagner 
Tested-by: Ferenc Wagner 
Signed-off-by: Henrique de Moraes Holschuh 
Cc: stable@kernel.org
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

asus-laptop: change light sens default values.

2009-12-18T21:44:14+00:00

commit d951d4cc84e8b5ddb8e0ab81cf6a72cc73fdd668 upstream.

The light sensor disable brightness key and
/sys/class/backlight/ control. There was a lot of report
from users who didn't understand why they couldn't change their
brightness, including:

https://bugs.launchpad.net/bugs/222171
https://bugzilla.novell.com/show_bug.cgi?id=514747
http://bugzilla.kernel.org/show_bug.cgi?id=13671
http://bugzilla.kernel.org/show_bug.cgi?id=14432

Now the light sensor is disabled, and if the user want to enable
it, the level should be ok.

The funny thing is that comments where ok, not code.

Cc: stable@kernel.org
Cc: Thomas Renninger 
Cc: Peter Küppers 
Cc: Michael Franzl 
Cc: Ian Turner 
Signed-off-by: Corentin Chary 
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

acerhdf: return temperature in milidegree instead of degree

2009-12-08T18:22:50+00:00

commit 7005291706341a11c094f39a756a01c9e649e5f9 upstream.

Return temperature in milidegree instead of degree, as sysfs-api requires
the temperature in milidegree.

Signed-off-by: Peter Feuerer 
Tested-by: Borislav Petkov 
Cc: Andreas Mohr 
Signed-off-by: Andrew Morton 
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

acerhdf: additional BIOS versions

2009-12-08T18:22:48+00:00

commit f944915187f53810130eb1c56985e27e3cbe4a6d upstream.

Added BIOS versions:
Acer: AOA110-v0.3307, AOA150-v0.3301, AOA150-v0.3307
Packard Bell: AOA150-v0.3105

Signed-off-by: Peter Feuerer 
Cc: Andreas Mohr 
Cc: Borislav Petkov 
Signed-off-by: Andrew Morton 
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

acerhdf: fix fan control for AOA150 model

2009-12-08T18:22:41+00:00

commit ded0cdfc6a7673916b0878c32fa8ba566b4f8cdb upstream.

- Apply Borislav Petkov's patch (convert the fancmd[] array to a real
  struct thus disambiguating command handling and making code more
  readable.)

- Add BIOS product to BIOS table as AOA110 and AOA150 have different
  register values

- Add force_product parameter to allow forcing different product

- fix linker warning caused by "acerhdf_drv" not being named
  "acerhdf_driver"

Signed-off-by: Peter Feuerer 
Cc: Andreas Mohr 
Acked-by: Borislav Petkov 
Signed-off-by: Andrew Morton 
Signed-off-by: Len Brown 
Cc: Adrian von Bidder 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: fix sign of ERESTARTSYS return

2009-12-08T18:21:47+00:00

commit 80a8d1228e90349b4514e8c925c061fa5cbcea75 upstream.

The returned error should be negative

Signed-off-by: Roel Kluin 
Acked-by: Henrique de Moraes Holschuh 
Signed-off-by: Andrew Morton 
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

sony-laptop: check for rfkill hard block at load time

2009-10-05T16:31:49+00:00

commit 50fab0760a6c07cded229357a1351c325a575770 upstream.

"I recently (on a flight) I found out that when I boot with the hard-switch
activated, so turning off all wireless activity on my laptop, the state
is not correctly announced in /dev/rfkill (reading it with rfkill command,
or my own gnome applet)...

After turning off and on again the hard-switch the events were right."

We can fix this by querying the firmware at load time and calling
rfkill_set_hw_state().

Signed-off-by: Alan Jenkins 
Tested-by: Norbert Preining 
Acked-by: Johannes Berg 
Acked-by: Mattia Dongili 
Signed-off-by: John W. Linville 
Signed-off-by: Greg Kroah-Hartman

thinkpad-acpi: don't ask about brightness_mode for fw. 1V and 1R

2009-10-05T16:31:35+00:00

commit 6da25bf51689a5cc60370d30275dbb9e6852e0cb upstream.

X40 (firmware 1V) and T41 (firmware 1R) have been confirmed to work
well with the new defaults, so we can stop pestering people to confirm
that fact.

For now, whitelist just these two firmware types.  It is best to have
at least one more firmware type confirmed for Radeon 9xxx and Intel
GMA-2 ThinkPads before removing the confirmation requests entirely.

Reported-by: Robert de Rooy 
Signed-off-by: Henrique de Moraes Holschuh 
Signed-off-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman