linux-toradex.git/drivers/platform, branch v3.2.19

sony-laptop: Enable keyboard backlight by default

2012-05-30T23:43:50+00:00

commit 6fe6ae56a7cebaebc2e6daa11c423e4692f9b592 upstream.

When the keyboard backlight support was originally added, the commit said
to default it to on with a 10 second timeout.  That actually wasn't the
case, as the default value is commented out for the kbd_backlight parameter.
Because it is a static variable, it gets set to 0 by default without some
other form of initialization.

However, it seems the function to set the value wasn't actually called
immediately, so whatever state the keyboard was in initially would remain.
Then commit df410d522410e67660 was introduced during the 2.6.39 timeframe to
immediately set whatever value was present (as well as attempt to
restore/reset the state on module removal or resume).  That seems to have
now forced the light off immediately when the module is loaded unless
the option kbd_backlight=1 is specified.

Let's enable it by default again (for the first time).  This should solve
https://bugzilla.redhat.com/show_bug.cgi?id=728478

Signed-off-by: Josh Boyer 
Acked-by: Mattia Dongili 
Signed-off-by: Matthew Garrett 
Signed-off-by: Ben Hutchings

dell-laptop: Terminate quirks list properly

2012-05-11T12:14:37+00:00

commit d62d421b071b08249361044d8e56c8b5c3ed6aa7 upstream.

Add missing DMI_NONE entry to end of the quirks list so
dmi_check_system() won't read past the end of the list.

Signed-off-by: Martin Nyhus 
Signed-off-by: Matthew Garrett 
Signed-off-by: Ben Hutchings

dell-laptop: touchpad LED should persist its status after S3

2012-05-11T12:14:08+00:00

commit 2d5de9e84928e35b4d9b46b4d8d5dcaac1cff1fa upstream.

Touchpad LED will not turn on after S3, it will make the touchpad status
doesn't consist with the LED.
By adding one flag to let the LED device restore it's status.

Signed-off-by: AceLan Kao 
Signed-off-by: Matthew Garrett 
Signed-off-by: Ben Hutchings

dell-laptop: add 3 machines that has touchpad LED

2012-05-11T12:14:08+00:00

commit 2a748853ca395c48ea75baa250f7cea6f0f23dbf upstream.

Add "Vostro 3555", "Inspiron N311z", and "Inspiron M5110" into quirks,
so that they could have touchpad LED function work.

Signed-off-by: AceLan Kao 
Signed-off-by: Matthew Garrett 
Signed-off-by: Ben Hutchings

acer-wmi: No wifi rfkill on Sony machines

2012-04-13T15:33:49+00:00

commit 5719b81988f3c24ff694dc3a37e35b35630a3966 upstream.

The wireless rfkill should charged by sony-laptop but not acer-wmi.
So, add Sony's SNY5001 acpi device to blacklist in acer-wmi.

Tested on Sony Vaio

Cc: Carlos Corbacho 
Cc: Matthew Garrett 
Cc: Mattia Dongili 
Cc: Dimitris N 
Tested-by: Dimitris N 
Signed-off-by: Lee, Chun-Yi 
Signed-off-by: Matthew Garrett 
Signed-off-by: Greg Kroah-Hartman

acer-wmi: No wifi rfkill on Lenovo machines

2012-03-19T16:02:21+00:00

commit 461e74377cfcfc2c0d6bbdfa8fc5fbc21b052c2a upstream.

We have several reports which says acer-wmi is loaded on ideapads
and register rfkill for wifi which can not be unblocked.

Since ideapad-laptop also register rfkill for wifi and it works
reliably, it will be fine acer-wmi is not going to register rfkill
for wifi once VPC2004 is found.

Also put IBM0068/LEN0068 in the list. Though thinkpad_acpi has no
wifi rfkill capability, there are reports which says acer-wmi also
block wireless on Thinkpad E520/E420.

Signed-off-by: Ike Panhc 
Signed-off-by: Matthew Garrett 
Cc: Jonathan Nieder 
Signed-off-by: Greg Kroah-Hartman

toshiba_acpi: Fix machines that don't support HCI_SYSTEM_EVENT

2011-12-05T18:07:28+00:00

The Satellite C670-10V generates notifications for hotkeys but does
not support HCI_SYSTEM_EVENT. As a result when a hotkey is pressed
it gets stuck in an infinite loop in toshiba_acpi_notify. To fix
this, detect whether or not HCI_SYSTEM_EVENT is supported up-front
and don't try to read system events if it isn't supported. In
addition, limit the number of retries when reading HCI_SYSTEM_EVENT
fails so that this loop cannot run unbounded.

Signed-off-by: Seth Forshee 
Signed-off-by: Matthew Garrett

platform/x86: fix dell-laptop function prototypes

2011-11-17T12:29:02+00:00

Fix build warnings:
  drivers/platform/x86/dell-laptop.c:592:13: warning: function declaration isn't a prototype
  drivers/platform/x86/dell-laptop.c:599:13: warning: function declaration isn't a prototype

Signed-off-by: Randy Dunlap 
Cc: Matthew Garrett 
Signed-off-by: Linus Torvalds

x86 platform drivers: add POWER_SUPPLY to selected drivers for Dell

2011-11-08T20:49:29+00:00

The Kconfig loop detection goes crazy without this.

Signed-off-by: Linus Torvalds

x86 platform drivers: make Dell laptop driver select needed LED support

2011-11-08T20:17:25+00:00

Otherwise we get compile errors like this:

  ERROR: "led_classdev_unregister" [drivers/platform/x86/dell-laptop.ko] undefined!
  ERROR: "led_classdev_register" [drivers/platform/x86/dell-laptop.ko] undefined!
  make[1]: *** [__modpost] Error 1
  make: *** [modules] Error 2

when the dell-laptop support is enabled without the necessary LED
support being enabled.

Reported-by: Alessandro Suardi 
Acked-by: Matthew Garrett 
Signed-off-by: Linus Torvalds