linux-toradex.git, branch v2.6.27.7

Linux 2.6.27.7

2008-11-20T23:02:37+00:00

ACPI: EC: Don't do transaction from GPE handler in poll mode.

2008-11-20T22:54:54+00:00

commit 8517934ef6aaa28d6e055b98df65b31cedbd1372 upstream.

Referencies: http://bugzilla.kernel.org/show_bug.cgi?id=12004

Signed-off-by: Alexey Starikovskiy 
Signed-off-by: Len Brown 
Cc: Rafael J. Wysocki 
Signed-off-by: Greg Kroah-Hartman

ACPI: EC: lower interrupt storm treshold

2008-11-20T22:54:53+00:00

commit 06cf7d3c7af902939cd1754abcafb2464060cba8 upstream.

http://bugzilla.kernel.org/show_bug.cgi?id=11892

Signed-off-by: Alexey Starikovskiy 
Signed-off-by: Len Brown 
Cc: Rafael J. Wysocki 
Signed-off-by: Greg Kroah-Hartman

ACPI: EC: restart failed command

2008-11-20T22:54:53+00:00

commit a2f93aeadf97e870ff385030633a73e21146815d upstream.

Restart current transaction if we recieved unexpected GPEs instead
of needed ones.

http://bugzilla.kernel.org/show_bug.cgi?id=11896

Signed-off-by: Alexey Starikovskiy 
Signed-off-by: Len Brown 
Cc: Rafael J. Wysocki 
Signed-off-by: Greg Kroah-Hartman

ACPI: EC: wait for last write gpe

2008-11-20T22:54:53+00:00

commit dd15f8c42af09031e27da5b4d697ce925511f2e1 upstream.

There is a possibility that EC might break if next command is
issued within 1 us after write or burst-disable command.

Suggestd-by: Zhao Yakui 
Signed-off-by: Alexey Starikovskiy 
Signed-off-by: Len Brown 
Cc: Rafael J. Wysocki 
Signed-off-by: Greg Kroah-Hartman

ACPI: EC: revert msleep patch

2008-11-20T22:54:53+00:00

commit 1cfe62c8010ac56e1bd3827e30386a87cc2f3594 upstream.

With the better solution for EC interrupt storm issue,
there is no need to use msleep over udelay.

References:
	http://bugzilla.kernel.org/show_bug.cgi?id=11810
	http://bugzilla.kernel.org/show_bug.cgi?id=10724

Signed-off-by: Alexey Starikovskiy 
Signed-off-by: Len Brown 
Cc: Rafael J. Wysocki 
Signed-off-by: Greg Kroah-Hartman

USB: don't register endpoints for interfaces that are going away

2008-11-20T22:54:53+00:00

commit 352d026338378b1f13f044e33c1047da6e470056 upstream.

This patch (as1155) fixes a bug in usbcore.  When interfaces are
deleted, either because the device was disconnected or because of a
configuration change, the extra attribute files and child endpoint
devices may get left behind.  This is because the core removes them
before calling device_del().  But during device_del(), after the
driver is unbound the core will reinstall altsetting 0 and recreate
those extra attributes and children.

The patch prevents this by adding a flag to record when the interface
is in the midst of being unregistered.  When the flag is set, the
attribute files and child devices will not be created.

Signed-off-by: Alan Stern 
Signed-off-by: Greg Kroah-Hartman

USB: EHCI: fix handling of dead controllers

2008-11-20T22:54:52+00:00

commit 67b2e029743a52670d77864723b4d0d40f7733b5 upstream.

This patch (as1165) makes a few small changes in the logic used by
ehci-hcd when it encounters a controller error:

	Instead of printing out the masked status, it prints the
	original status as read directly from the hardware.

	It doesn't check for the STS_HALT status bit before taking
	action.  The mere fact that the STS_FATAL bit is set means
	that something bad has happened and the controller needs to
	be reset.  With the old code this test could never succeed
	because the STS_HALT bit was masked out from the status.

I anticipate that this will prevent the occasional "irq X: nobody cared"
problem people encounter when their EHCI controllers die.

Signed-off-by: Alan Stern 
Cc: David Brownell 
Signed-off-by: Greg Kroah-Hartman

USB: EHCI: fix divide-by-zero bug

2008-11-20T22:54:52+00:00

commit 372dd6e8ed924e876f3beb598721e813ad7fa323 upstream.

This patch (as1164) fixes a bug in the EHCI scheduler.  The interval
value it uses is already in linear format, not logarithmically coded.
The existing code can sometimes crash the system by trying to divide
by zero.

Signed-off-by: Alan Stern 
Cc: David Brownell 
Signed-off-by: Greg Kroah-Hartman

USB: cdc-acm.c: fix recursive lock in acm_start_wb error path

2008-11-20T22:54:52+00:00

commit ad0b65efd12d020b046cde8d6f474e37bb98dd73 upstream.

Fixes an obvious bug in cdc-acm by avoiding a recursive lock on
acm_start_wb()'s error path. Should apply towards 2.6.27 stable and
2.6.28.

=============================================
[ INFO: possible recursive locking detected ]
2.6.27-2-pae #109
---------------------------------------------
python/31449 is trying to acquire lock:
 (&acm->write_lock){++..}, at: [] acm_start_wb+0x5c/0x7b [cdc_acm]

but task is already holding lock:
 (&acm->write_lock){++..}, at: [] acm_tty_write+0xe1/0x167 [cdc_acm]

other info that might help us debug this:
2 locks held by python/31449:
 #0:  (&tty->atomic_write_lock){--..}, at: [] tty_write_lock+0x14/0x3b
 #1:  (&acm->write_lock){++..}, at: [] acm_tty_write+0xe1/0x167 [cdc_acm]

stack backtrace:
Pid: 31449, comm: python Not tainted 2.6.27-2-pae #109
 [] ? printk+0xf/0x18
 [] __lock_acquire+0xc7b/0x1316
 [] lock_acquire+0x70/0x97
 [] ? acm_start_wb+0x5c/0x7b [cdc_acm]
 [] _spin_lock_irqsave+0x37/0x47
 [] ? acm_start_wb+0x5c/0x7b [cdc_acm]
 [] acm_start_wb+0x5c/0x7b [cdc_acm]
 [] acm_tty_write+0x143/0x167 [cdc_acm]
 [] write_chan+0x1cd/0x297
 [] ? default_wake_function+0x0/0xd
 [] tty_write+0x149/0x1b9
 [] ? write_chan+0x0/0x297
 [] ? rw_verify_area+0x76/0x98
 [] ? tty_write+0x0/0x1b9
 [] vfs_write+0x8c/0x136
 [] sys_write+0x3b/0x60
 [] sysenter_do_call+0x12/0x3f
 =======================

Signed-off-by: Brandon Philips 
Cc: Oliver Neukum 
Signed-off-by: Greg Kroah-Hartman