linux-toradex.git/drivers/usb/class, branch v2.6.28.9

USB: usbtmc: add protocol 1 support

2009-03-23T21:55:29+00:00

commit 228dd05dbfdd0fced8ab1a28ed73b500ba6bb0a6 upstream.

The driver already supports the 1 protocol support, so just add it to
the MODULE_DEVICE_TABLE entry so it properly picks up these devices.

Thanks to Jouni Rynö for pointing this out.

Reported-by: Jouni Ryno 
Signed-off-by: Greg Kroah-Hartman

USB: usbtmc: fix stupid bug in open()

2009-03-23T21:55:29+00:00

commit 5b10916ea0a62920204517e1c4ce14560b4f96ab upstream.

open() will never succeed, as we always return -ENODEV.  Fix this
obvious bug.

Thanks to Jouni Ryno for reporting it.

Reported-by: Jouni Ryno 
Signed-off-by: Greg Kroah-Hartman

USB: cdc-acm: add usb id for motomagx phones

2009-03-17T00:32:04+00:00

commit 155df65ae11dfc322214c6f887185929c809df1b upstream.

The Motorola MOTOMAGX phones (Z6, E8, Zn5 so far) are providing
combined ACM/BLAN USB configuration. Since it has Vendor Specific
class, the corresponding drivers (cdc-acm, zaurus) can't find it just
by interface info. This patch adds usb id so the cdc-acm driver can
properly handle this combined device.

Signed-off-by: Dmitriy Taychenachev 
Signed-off-by: Greg Kroah-Hartman

USB: fix problem with usbtmc driver not loading properly

2008-12-17T18:49:10+00:00

The usbtmc driver forgot to export its device table to userspace.
Without this, it is never loaded properly when such a device is seen by
the system.

Cc: Marcel Janssen 
Cc: stable 
Signed-off-by: Greg Kroah-Hartman

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

2008-11-13T22:45:02+00:00

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 
Cc: stable 
Signed-off-by: Greg Kroah-Hartman

USB: usbtmc: Use explicit unsigned type for input buffer instead of char*

2008-10-29T21:54:40+00:00

Silences compiler warning about comparison with 0x80, and type now matches the
corresponding _bulk_out function.

drivers/usb/class/usbtmc.c: In function ‘usbtmc_ioctl_abort_bulk_in’:
drivers/usb/class/usbtmc.c:163: warning: comparison is always false due to limited range of data type

Signed-off-by: Chris Malley 
Signed-off-by: Greg Kroah-Hartman

USB: fix memory leak in cdc-acm

2008-10-22T17:05:29+00:00

This fixes a memory leak on disconnect in cdc-acm

Thanks to 施金前 for finding it.

Signed-off-by: Oliver Neukum 
Cc: stable 
Signed-off-by: Greg Kroah-Hartman

USB: cdc-wdm: make module autoload work

2008-10-22T17:05:29+00:00

this fixes an omission that led to no alias being computed for the
cdc-wdm module.

Signed-off-by: Oliver Neukum 
Cc: stable 
Signed-off-by: Greg Kroah-Hartman

USB: remove err() macro from usb class drivers

2008-10-17T21:41:10+00:00

USB should not be having it's own printk macros, so remove err() and
use the system-wide standard of dev_err() wherever possible.  In the
few places that will not work out, use a basic printk().

Signed-off-by: Greg Kroah-Hartman

USB: remove info() macro from remaining usb drivers

2008-10-17T21:41:09+00:00

USB should not be having it's own printk macros, so remove info() and
use the system-wide standard of dev_info() wherever possible.  In the
few places that will not work out, use a basic printk().

Clean up the remaining usages of this in the drivers/usb/ directory.

Signed-off-by: Greg Kroah-Hartman