linux-toradex.git/drivers, branch v2.6.31.10

Input: atkbd - add force relese key quirk for Samsung R59P/R60P/R61P

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

This patch is not upstream. Since 2.6.32, there is an interface in
/sys for handling the force_release events from userspace, so such
quirk patches are no longer accepted upstream now. But this patch is
valid for version 2.6.31 downwards.

OriginalAuthor:
    Moiseev Vladimir 
    Alexander Huhlaev 

BugLink: http://bugs.launchpad.net/bugs/253874

Signed-off-by: Keng-Yu Lin 
Cc: Moiseev Vladimir 
Cc: Alexander Huhlaev 
Signed-off-by: Greg Kroah-Hartman

rt2x00: Disable powersaving for rt61pci and rt2800pci.

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

commit 93b6bd26b74efe46b4579592560f9f1cb7b61994 upstream.

We've had many reports of rt61pci failures with powersaving enabled.
Therefore, as a stop-gap measure, disable powersaving of the rt61pci
until we have found a proper solution.
Also disable powersaving on rt2800pci as it most probably will show
the same problem.

Signed-off-by: Gertjan van Wingerde 
Acked-by: Ivo van Doorn 
Signed-off-by: John W. Linville 
Signed-off-by: Greg Kroah-Hartman

V4L/DVB (13596): ov511.c typo: lock => unlock

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

commit 50e9d31183ed61c787b870cb3ee8f6c3db8c8a1e upstream.

This was found with a static checker and has not been tested, but it seems
pretty clear that the mutex_lock() was supposed to be mutex_unlock()

Signed-off-by: Dan Carpenter 
Signed-off-by: Douglas Schilling Landgraf 
Signed-off-by: Mauro Carvalho Chehab 
Cc: Brandon Philips 
Signed-off-by: Greg Kroah-Hartman

S390: dasd: support DIAG access for read-only devices

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

commit 22825ab7693fd29769518a0d25ba43c01a50092a upstream.

When a DASD device is used with the DIAG discipline, the DIAG
initialization will indicate success or error with a respective
return code. So far we have interpreted a return code of 4 as error,
but it actually means that the initialization was successful, but
the device is read-only. To allow read-only devices to be used with
DIAG we need to accept a return code of 4 as success.

Re-initialization of the DIAG access is also part of the DIAG error
recovery. If we find that the access mode of a device has been
changed from writable to read-only while the device was in use,
we print an error message.

Signed-off-by: Stefan Weinhuber 
Signed-off-by: Martin Schwidefsky 
Cc: Stephen Powell 
Signed-off-by: Greg Kroah-Hartman

i2c/tsl2550: Fix lux value in extended mode

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

commit 5f5bfb09d81c9a1d26238ae6668e584c14ae3daf upstream.

According to the TAOS Application Note 'Controlling a Backlight with
the TSL2550 Ambient Light Sensor' (page 14), the actual lux value in
extended mode should be obtained multiplying the calculated lux value
by 5.

Signed-off-by: Michele Jr De Candia 
Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman

hwmon: (sht15) Off-by-one error in array index + incorrect constants

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

commit 4235f684b66d6f00d2cd8849c884cf8f8b57ecad upstream.

Fix an off-by-one error in array index + incorrect constants.

Signed-off-by: Christoph Walser 
Signed-off-by: Jonathan Cameron 
Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman

hwmon: (fschmd) Fix check on unsigned in watchdog_write()

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

commit c7702c31340f84cfd5e5df22293578b7ae1e9370 upstream.

If unsigned the watchdog_trigger() return value will not be
checked correctly.

Signed-off-by: Roel Kluin 
Acked-by: Andrew Morton 
Cc: Hans de Goede 
Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman

hostap: Revert a toxic part of the conversion to net_device_ops

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

commit e484c16f6212f7f06407382efa4d3ad214b6c589 upstream.

As the hostap driver was converted to use net_device_ops, a mistake was
made in hostap_main.c (commit 5ae4efbcd2611562a8b93596be034e63495706a5).
Originally, the tx_queue_len was set to 0 for every other interface than
HOSTAP_INTERFACE_MASTER, but the new fragment of code sets tx_queue_len to
0 only for HOSTAP_INTERFACE_MASTER. The opposite of the previous
behavior makes the driver to drop all packets in AP mode.

Change the way 0 is assigned to tx_queue_len according to the original
logic.

Signed-off-by: Martin Decky 
Signed-off-by: John W. Linville 
Signed-off-by: Greg Kroah-Hartman

e100: Fix broken cbs accounting due to missing memset.

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

commit 70abc8cb90e679d8519721e2761d8366a18212a6 upstream.

Alan Stern noticed that e100 caused slab corruption.
commit 98468efddb101f8a29af974101c17ba513b07be1 changed
the allocation of cbs to use dma pools that don't return zeroed memory,
especially the cb->status field used to track which cb to clean, causing
(the visible) double freeing of skbs and a wrong free cbs count.

Now the cbs are explicitly zeroed at allocation time.

Reported-by: Alan Stern 
Tested-by: Alan Stern 
Signed-off-by: Roger Oksanen 
Acked-by: Jesse Brandeburg 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

e100: Use pci pool to work around GFP_ATOMIC order 5 memory allocation failure

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

commit 98468efddb101f8a29af974101c17ba513b07be1 upstream.

pci_alloc_consistent uses GFP_ATOMIC allocation that may fail on some systems
with limited memory (Bug #14265). pci_pool_alloc allows waiting with
GFP_KERNEL.

Tested-by: Karol Lewandowski 
Signed-off-by: Roger Oksanen 
Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman