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

dell-laptop: Terminate quirks list properly

2012-05-07T15:53:21+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 
Cc: Guenter Roeck 
Tested-by: Jens Gustedt 
Signed-off-by: Greg Kroah-Hartman

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

2012-04-27T17:16:52+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: Greg Kroah-Hartman

dell-laptop: add 3 machines that has touchpad LED

2012-04-27T17:16:52+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: Greg Kroah-Hartman

acer-wmi: No wifi rfkill on Sony machines

2012-04-13T16:13:56+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

panasonic-laptop: avoid overflow in acpi_pcc_hotkey_add()

2012-03-12T14:25:51+00:00

num_sifr could go negative since acpi_pcc_get_sqty() returns -EINVAL
on error.  Then it could bypass the sanity check (num_sifr > 255).
The subsequent call to kzalloc() would allocate a small buffer, leading
to a memory corruption.

Signed-off-by: Xi Wang 
Signed-off-by: Matthew Garrett

acer-wmi: No wifi rfkill on Lenovo machines

2012-03-12T13:58:02+00:00

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

Fujitsu tablet extras driver

2012-03-12T13:57:52+00:00

This patch adds support for some of the devices within a wide variety
of Fujitsu Tablet Computers, both convertibles and slates. Primarily
it allows for the automatic detection of the tablet/notebook mode for
convertible tablet pc's, and orientation for docked slates. It also
adds support for the application panel buttons usually found next to
the tablet screen, and docking station detection for slates.

Signed-off-by: Robert Gerlach 
Signed-off-by: Matthew Garrett

x86: Add amilo-rfkill driver for some Fujitsu-Siemens Amilo laptops

2012-03-12T13:56:47+00:00

An rfkill driver based on the fsaa1655g and fsam7440 drivers for
Fujitsu-Siemens Amilo A1655 and M7440 models found at:

http://sourceforge.net/projects/fsaa1655g/
http://sourceforge.net/projects/fsam7440/

This adds DMI matching, replaces the procfs files with rfkill devices,
and uses the proper functions to write to the i8042 safely.

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

asm-generic: architecture independent readq/writeq for 32bit environment

2012-02-22T00:47:28+00:00

This provides unified readq()/writeq() helper functions for 32-bit
drivers.

For some cases, readq/writeq without atomicity is harmful, and order of
io access has to be specified explicitly.  So in this patch, new two
header files which contain non-atomic readq/writeq are added.

 -  provides non-atomic readq/
   writeq with the order of lower address -> higher address

 -  provides non-atomic readq/
   writeq with reversed order

This allows us to remove some readq()s that were added drivers when the
default non-atomic ones were removed in commit dbee8a0affd5 ("x86:
remove 32-bit versions of readq()/writeq()")

The drivers which need readq/writeq but can do with the non-atomic ones
must add the line:

  #include  /* or hi-lo.h */

But this will be nop in 64-bit environments, and no other #ifdefs are
required.  So I believe that this patch can solve the problem of
 1. driver-specific readq/writeq
 2. atomicity and order of io access

This patch is tested with building allyesconfig and allmodconfig as
ARCH=x86 and ARCH=i386 on top of tip/master.

Cc: Kashyap Desai 
Cc: Len Brown 
Cc: Ravi Anand 
Cc: Vikas Chaudhary 
Cc: Matthew Garrett 
Cc: Jason Uhlenkott 
Cc: James Bottomley 
Cc: Thomas Gleixner 
Cc: "H. Peter Anvin" 
Cc: Roland Dreier 
Cc: James Bottomley 
Cc: Alan Cox 
Cc: Matthew Wilcox 
Cc: Andrew Morton 
Signed-off-by: Hitoshi Mitake 
Signed-off-by: Linus Torvalds

module_param: make bool parameters really bool (drivers & misc)

2012-01-12T23:02:20+00:00

module_param(bool) used to counter-intuitively take an int.  In
fddd5201 (mid-2009) we allowed bool or int/unsigned int using a messy
trick.

It's time to remove the int/unsigned int option.  For this version
it'll simply give a warning, but it'll break next kernel version.

Acked-by: Mauro Carvalho Chehab 
Signed-off-by: Rusty Russell