- 19 Mar, 2010 40 commits
-
-
Yoshihiro Shimoda authored
fix the problem that when a USB hub is attached to the r8a66597-hcd and a device is removed from that hub, it's likely that a kernel panic follows. Reported-by:
Markus Pietrek <Markus.Pietrek@emtrion.de> Signed-off-by:
Yoshihiro Shimoda <shimoda.yoshihiro@renesas.com> Cc: stable <stable@kernel.org> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Sarah Sharp authored
The xHCI hardware can only handle polling intervals that are a power of two. When we add a new endpoint during a bandwidth allocation, and the polling interval is rounded down to a power of two, print the original polling interval in the endpoint descriptor. Signed-off-by:
Sarah Sharp <sarah.a.sharp@linux.intel.com> Signed-off-by:
-
Matthew Wilcox authored
USB 3 and Wireless USB specify a logarithmic encoding of the endpoint interval that matches the USB 2 specification. usb_fill_int_urb() didn't know that and was filling in the interval as if it was USB 1.1. Fix usb_fill_int_urb() for SuperSpeed devices, but leave the wireless case alone, because David Vrabel wants to keep the old encoding. Update the struct urb kernel doc to note that SuperSpeed URBs must have urb->interval specified in microframes. Add a missing break statement in the usb_submit_urb() interrupt URB checking, since wireless USB and SuperSpeed USB encode urb->interval differently. This allows xHCI roothubs to actually register with khubd. Signed-off-by:
Matthew Wilcox <willy@linux.intel.com> Signed-off-by:
-
Michael Brunner authored
This patch removes a double usb_control_msg that sets the cp210x configuration registers a second time when calling cp210x_set_config. For data sizes >2 the second write gets corrupted. The patch has been created against 2.6.34-rc1, but all cp210x driver revisions are affected. Signed-off-by:
Michael Brunner <mibru@gmx.de> Signed-off-by:
-
Christoph Egger authored
One last bit was missed while removing the USB_BERRY_CHARGE config option in a8d4211f which gets dropped by this patch. Signed-off-by:
Christoph Egger <siccegge@stud.informatik.uni-erlangen.de> Signed-off-by:
-
Maurus Cuelenaere authored
This prevents some drivers from complaining that no bcdDevice id was set. Signed-off-by:
Maurus Cuelenaere <mcuelenaere@gmail.com> Signed-off-by:
-
Alessio Igor Bogani authored
The change_speed() function should be serialized against multiple calls. Use the cfg_lock mutex to do this. Signed-off-by:
Alessio Igor Bogani <abogani@texware.it> Signed-off-by:
-
Michal Nazarewicz authored
The Kconfig help message for Mass Storage Gadget claimed the module will be named "g_file_storage" whereas it should be "g_mass_storage". Signed-off-by:
Michal Nazarewicz <m.nazarewicz@samsung.com> Cc: Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
-
Peter Korsgaard authored
Contrary to the comment in fsg_add, fsg_bind calls fsg_unbind on errors, which decreases refcount and frees the fsg_dev structure, causing trouble when fsg_add does the same. Fix it by simply leaving up cleanup to fsg_add(). Signed-off-by:
Peter Korsgaard <jacmet@sunsite.dk> Acked-by:
-
Mike Frysinger authored
The recent commit (0e530b45) that moved usb_ep_autoconfig from the __devinit section to the __init section missed the mass storage device. Its fsg_bind() function uses the usb_ep_autoconfig() function from non __init context leading to: WARNING: drivers/usb/gadget/g_mass_storage.o(.text): Section mismatch in reference from the function _fsg_bind() to the function .init.text:_usb_ep_autoconfig() So move fsg_bind() into __init as well. Signed-off-by:
Mike Frysinger <vapier@gentoo.org> Signed-off-by:
-
Mike Frysinger authored
The recent change to clean out dead gadget drivers (90f79768) missed the call to gadget_is_musbhsfc() behind CONFIG_BLACKFIN. This causes Blackfin gadget builds to fail since the function no longer exists anywhere. Signed-off-by:
-
Dan Carpenter authored
"dev" is always null here. In the end it's only used to get the pci_name() of "pdev" which is redundant information and so I removed it. Signed-off-by:
Dan Carpenter <error27@gmail.com> Signed-off-by:
-
spark authored
Signed-off-by:
spark <spark@bandrich.com> Signed-off-by:
-
Stefan Schmidt authored
The module is called qcaux and not moto_modem. Also use help instead of ---help-- to be in sync with the other Kconfig entries. Signed-off-by:
Stefan Schmidt <stefan@datenfreihafen.org> Signed-off-by:
-
Oliver Neukum authored
The new runtime PM scheme allows resume() to have no locks. This fixes the deadlock. Signed-off-by:
Oliver Neukum <neukum@b1-systems.de> Signed-off-by:
-
Oliver Neukum authored
- as the callback can schedule work, URBs must be killed first - if the driver causes an autoresume, the caller must handle locking Signed-off-by:
-
Oliver Neukum authored
The guarding flag must be set and tested under spinlock and cleared before the URBs are resubmitted in resume. Signed-off-by:
-
Oliver Neukum authored
There's a window under which cdc-wdm may submit an URB to a device about to be suspended. This introduces a flag to prevent it. Signed-off-by:
-
Oliver Neukum authored
dev_dbg() and dev_err() cannot be used to report failures that may have been caused by a device's removal Signed-off-by:
-
Oliver Neukum authored
While an available response is read the device must not be autosuspended. This requires a flag dedicated to that purpose. Signed-off-by:
-
Oliver Neukum authored
Unify mutexes to fix a race between write and disconnect and shift the test for disconnection to always report it. Signed-off-by:
-
Felipe Balbi authored
... and avoid a compilation if we disable host side of musb. Signed-off-by:
Felipe Balbi <felipe.balbi@nokia.com> Signed-off-by:
-
Mike Frysinger authored
The recent commit "usb: musb: Add context save and restore support" added some stubs for the Blackfin code so things would compile, but it also added a bunch of warnings due to missing return statements. Signed-off-by:
-
Mike Frysinger authored
The USB PHY on current Blackfin processors is a UTMI+ level 2 PHY. However, it has no ULPI support - so there are no registers at all. That means accesses to ULPI_BUSCONTROL have to be abstracted away like other MUSB registers. This fixes building for Blackfin parts again. Signed-off-by:
Anand Gadiyar <gadiyar@ti.com> Signed-off-by:
-
Tony Lindgren authored
CONFIG_ARCH_OMAP34XX is now CONFIG_ARCH_OMAP3. But since drivers/usb/musb/omap2430.c use CONFIG_PM for these registers and functions, do the same for the header. Otherwise we get the following for most omap3 defconfigs: drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before 'do' drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before 'while' drivers/usb/musb/omap2430.c:268: error: expected identifier or '(' before 'do' drivers/usb/musb/omap2430.c:268: error: expected identifier or '(' before 'while' Signed-off-by:Tony Lindgren <tony@atomide.com> Signed-off-by:
-
Grant Likely authored
C file uses IS_ERR and PTR_ERR, but doesn't include <linux/err.h> Signed-off-by:
Grant Likely <grant.likely@secretlab.ca> Signed-off-by:
-
Oliver Neukum authored
The name used in the documentation doesn't match reality. Signed-off-by:
-
Nathaniel McCallum authored
Signed-off-by:
Nathaniel McCallum <nathaniel@natemccallum.com> Cc: stable <stable@kernel.org> Signed-off-by:
-
Nathaniel McCallum authored
Signed-off-by:
-
Nathaniel McCallum authored
Signed-off-by:
-
Daniel Sangorrin authored
This is a patch to ftdi_sio_ids.h and ftdi_sio.c that adds identifiers for CONTEC USB serial converter. I tested it with the device COM-1(USB)H [akpm@linux-foundation.org: keep the VIDs sorted a bit] Signed-off-by:
Daniel Sangorrin <daniel.sangorrin@gmail.com> Cc: Andreas Mohr <andi@lisas.de> Cc: Radek Liboska <liboska@uochb.cas.cz> Cc: stable <stable@kernel.org> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
-
Andiry Xu authored
When a signal interrupts a Configure Endpoint command, the cmd_completion used in xhci_configure_endpoint() is not re-initialized and the wait_for_completion_interruptible_timeout() will return failure. Initialize cmd_completion in xhci_configure_endpoint(). Signed-off-by:
Andiry Xu <andiry.xu@amd.com> Signed-off-by:
-
Alex Chiang authored
Naming consistency with other USB HCDs. Signed-off-by:
Alex Chiang <achiang@hp.com> Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com> Signed-off-by:
-
Sonic Zhang authored
The recent commit "usb: musb: Fix for isochronous IN transfer" (f82a689f) seems to have been against an older kernel version. It uses the old style naming of variables. Unfortunately, this breaks building for most MUSB users out there since "bDesiredMode" has been renamed to "desired_mode". Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com> Signed-off-by:
-
Bernhard Rosenkraenzer authored
This patch adds various USB device IDs for Gobi 2000 devices, as found in the drivers available at https://www.codeaurora.org/wiki/GOBI_ReleasesSigned-off-by:
Bernhard Rosenkraenzer <bero@arklinux.org> Cc: stable <stable@kernel.org> Signed-off-by:
-
Oliver Neukum authored
Stupid logic bug passing a just nulled pointer Signed-off-by:
-
Clemens Ladisch authored
The EHCI driver stores in usb_host_endpoint.hcpriv a pointer to either an ehci_qh or an ehci_iso_stream structure, and uses the contents of the hw_info1 field to distinguish the two cases. After ehci_qh was split into hw and sw parts, ehci_iso_stream must also be adjusted so that it again looks like an ehci_qh structure. This fixes a NULL pointer access in ehci_endpoint_disable() when it tries to access qh->hw->hw_info1. Signed-off-by:
Clemens Ladisch <clemens@ladisch.de> Reported-by:
Colin Fletcher <colin.m.fletcher@googlemail.com> Cc: stable <stable@kernel.org> Acked-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
-
Clemens Ladisch authored
When isochronous URBs are shorter than one frame and when more than one ITD in a frame has been completed before the interrupt can be handled, scan_periodic() completes the URBs in the order in which they are found in the descriptor list. Therefore, the descriptor list must contain the ITDs in the correct order, i.e., a new ITD must be linked in after any previous ITDs of the same endpoint. This should fix garbled capture data in the USB audio drivers. Signed-off-by:
-
Huang Ying authored
I found a DLink DWM 652 U5 USB 3G modem has product ID 0xce1e instead of orignal 0xce16. The new ID is added. And I found there are two entries for 0xce16, one has raw number, the other has symbol DLINK_PRODUCT_DWM_652_U5. This is fixed too. Signed-off-by:
Huang Ying <ying.huang@intel.com> Signed-off-by:
-
Ondrej Zary authored
SL11R-IDE 2.6c (at least) reports wrong capacity (one sector more). Reading that last sector causes the device not to work anymore (and looks like HAL or something does that automatically after plugging in): sd 5:0:0:0: [sdc] Device not ready sd 5:0:0:0: [sdc] Result: hostbyte=0x00 driverbyte=0x08 sd 5:0:0:0: [sdc] Sense Key : 0x2 [current] sd 5:0:0:0: [sdc] ASC=0x0 ASCQ=0x0 sd 5:0:0:0: [sdc] CDB: cdb[0]=0x28: 28 00 04 a8 b5 70 00 00 01 00 Add unusual_devs entry to fix the capacity. Signed-off-by:
Ondrej Zary <linux@rainbow-software.org> Signed-off-by:
Phil Dibowitz <phil@ipom.com> Signed-off-by:
-
