- 27 Apr, 2007 40 commits
-
-
Li Yang authored
Update gadget_chip.c, ether.c for newly added Freescale Highspeed USB device driver. Signed-off-by:
Li Yang <leoli@freescale.com> Signed-off-by:
David Brownell <dbrownell@users.sourceforge.net> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Li Yang authored
Freescale high-speed USB SOC can be found on some Freescale processors among different architectures. It supports both host and device functions. This driver adds its device support for Linux USB Gadget layer. It is tested on MPC8349 and MPC8313, but should work on other platforms with minor tweaks. The driver passed USBCV 1.3 compliance tests. Note that this driver doesn't yet include OTG support. Signed-off-by:
Jiang Bo <tanya.jiang@freescale.com> Signed-off-by:
Bruce Schmid <duck@freescale.com> Signed-off-by:
-
Raphael Assenat authored
Here's a patch which adds my device to the list. This patch enables the broken suspend quirk for the PCI OHCI controller present in the IT8152F/G RISC-to-PCI Companion Chip. Signed-off-by:
Raphael Assenat <raph@8d.com> Signed-off-by:
-
Eberhard Fahle authored
The driver uses usb_control_msg() for exchanging data with the device. When the driver lived freeley _outside_ the kernel tree (pre 2.6.21) the timeouts for these calls where set to 5*HZ for reading, 1HZ for writing. (These timeouts seemed to work fine for all users of the driver, at least nobody complained in the last 2 years. The current code (2.6.21-rc5) removed the 'HZ' from the timeouts and left the driver with 5 jiffies for reading and 1 jiffy for writing. My new machine is fast, but not that fast. The patch also removes a useless debug statement, which was left over from testing a broken firmware version From: Eberhard Fahle <e.fahle@wayoda.org> Signed-off-by: -
Hans Engelen authored
Signed-off-by: -
Phil Dibowitz authored
Per the Rui Santos and the hardware manufacturers, this actually inhibits useful parts of the hardware. The correct way to use this hardware is with the software at http://www.kanoistika.sk/bobovsky/archiv/umts/ and the manufacturers are also planning on including Linux drivers/material in future revisions. CC: Rui Santos <rsantos@grupopie.com> CC: <johann.wilhelm@student.tugraz.at> CC: <zihan@huawei.com> CC: <wanganyu1983@huawei.com> CC: <dingjianjian@huawei.com> Signed-off-by:
Phil Dibowitz <phil@ipom.com> Signed-off-by:
-
Craig Shelley authored
Two new device IDs for CP2101 driver. Signed-off-by:
Craig Shelley <craig@microtron.org.uk> Signed-off-by:
-
Joey Goncalves authored
Hi Greg: I have found that /drivers/usb/misc/ldusb.c works with the "PICDEM Full Speed USB" http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en021940Signed-off-by:
Joey S Goncalves <jgoncalves@peragrin.com> Cc: Michael Hund <MHund@LD-Didactic.de> Signed-off-by:
-
Oliver Neukum authored
the memory barrier is needed only with smp. Signed-off-by:
Oliver Neukum <oneukum@suse.de> Signed-off-by:
-
David Brownell authored
Remove the old crisv10 HCD ... it can't have built for some time, doesn't even have a Kconfig entry, was the last driver not to have been converted to the "hcd" framework, and considering the usbcore changes since its last patch was merged, has just got to buggy as all get-out. I'm told Axis has a new driver, and will be submitting it soon. Signed-off-by:
-
Erik Hovland authored
Another workaround for the glitch in the network layer, whereby one call ignores the (otherwise kernel-wide) convention that free() calls should not oops when passed nulls. This code already handles that API glitch in most other paths. From: Erik Hovland <erik@hovland.org> Signed-off-by:
-
Alan Stern authored
This patch (as903) adds a "busnum" sysfs attribute for USB devices. Signed-off-by:
Alan Stern <stern@rowland.harvard.edu> Signed-off-by:
-
Simon Arlott authored
The device has commands to start/stop the ADSL function, so this adds a sysfs attribute to allow it to be started/stopped/restarted. It also stops polling the device for status when the ADSL function is disabled. There are no problems with sending multiple start or stop commands, even with a fast loop of them the device still works. There is no need to protect the restart process from further user actions while it's waiting for 1.5s. Signed-off-by:
Simon Arlott <simon@fire.lp0.eu> Cc: Duncan Sands <duncan.sands@math.u-psud.fr> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
-
Simon Arlott authored
Detect usb device shutdown and ignore failed urbs. This happens when the driver is unloaded or the device is unplugged. I'm not sure what other urb statuses should be ignored, and the warning message doesn't need to be shown when the module is unloaded or the device is removed. Signed-off-by:
-
S.Caglar Onur authored
Remove duplicate define of OHCI_QUIRK_ZFMICRO from ftdi-elan.c, its already defined in drivers/ush/host/ohci.c Signed-off-by:
"S.Caglar Onur" <caglar@pardus.org.tr> Cc: <tony.olech@elandigitalsystems.com> Signed-off-by:
-
Leon Leong authored
Add the detection for the BandRich BandLuxe C100/C100S/C120 HSDPA Data Card. With the vendor and product IDs are set properly, the data card can be detected and works fine. Signed-off-by:
Leon Leong <upleong@bandrich.com> Signed-off-by:
-
Wu, Bryan authored
skb_push function may return a pointer which is not aligned as required by struct rndis_packet_msg_type. Using attribute trick to fix this bug. Signed-off-by:
Roy Huang <roy.huang@analog.com> Signed-off-by:
Jie Zhang <jie.zhang@analog.com> Signed-off-by:
Bryan Wu <bryan.wu@analog.com> Cc: David Brownell <david-b@pacbell.net> Signed-off-by:
-
Cyrill Gorcunov authored
Add checking of driver registration status and release allocated resources if it failed. Signed-off-by:
Cyrill Gorcunov <gorcunov@gmail.com> Cc: Pete Zaitcev <zaitcev@redhat.com> Cc: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br> Signed-off-by:
-
Greg Kroah-Hartman authored
This should help with any potential NULL pointer usages as reported by a few users. Signed-off-by: -
David Brownell authored
Use the new ohci-pci quirk infrastructure to address the problem it was created to address: a quirk specific to the Portege 4000, in buzilla as http://bugzilla.kernel.org/show_bug.cgi?id=6723 Also fix a misuse of "__devinit" for the quirk functions. It must not be used without first ensuring that the references from the quirk tables are gone, and that the function using those quirk tables is also gone. Signed-off-by:
-
David Brownell authored
Update "usbnet" so that ethtool reports the name of the minidriver in use (e.g. asix, cdc_ether, dm9601, rndis_host) instead of "usbnet". This is a better match to how other network drivers work, resolving a minor open issue. Signed-off-by:
-
David Brownell authored
Cleanups to the rndis_host code, and a tweak that helps talking to PXA hardware. Mostly from Ole André Vadla Ravnås <oleavr@gmail.com> - Prevent SET_INTERFACE requests, they give PXA hardware bad indigestion - For paranoia, null a pointer after freeing its data - Wrap up ActiveSync oddities for RNDIS_QUERY in one routine - Use that wrapper when getting the Ethernet address - Whitespace fixes Plus add a comment noting the open issues about some RNDIS clients still needing TBD kinds of browbeating to accept non-jumbogram packets. Signed-off-by:
-
David Brownell authored
Minor doc update to <linux/usb/ch9.h> ... say where USB_DT_CS_* came from and update the definitions to match how they're derived there. Signed-off-by:
-
Alan Stern authored
This patch (as897) changes the autosuspend timer code to use the standard types and macros in dealing with jiffies values. Signed-off-by:
-
Pete Zaitcev authored
Add the "bus zero" feature to the usbmon. If a user process specifies bus with number zero, it receives events from all buses. This is useful when we wish to see initial enumeration when a bus is created, typically after a modprobe. Until now, an application had to loop until a new bus could be open, then start capturing on it. This procedure was cumbersome and could lose initial events. Also, often it's too bothersome to find exactly to which bus a specific device is attached. Paolo Albeni provided the original concept implementation. I added the handling of "bus->monitored" flag and generally fixed it up. Signed-off-by:
Pete Zaitcev <zaitcev@redhat.com> Signed-off-by:
-
Tony Lindgren authored
Some host controller drivers may need a PIO fallback when a DMA channel is temporarily unavailable. This patch provides an address that such drivers can use for PIO in those cases, and nulls that field out when no such address is available (highmem) which should help usbmon. Signed-off-by:
Tony Lindgren <tony@atomide.com> Signed-off-by:
-
Oliver Neukum authored
this driver does - ignore errors during open - submit a running urb - use down_interruptible not handling signals - GFP_KERNEL with a spinlock held Signed-off-by:
-
Alan Stern authored
This patch (as877) adds a "last_busy" field to struct usb_device, for use by the autosuspend framework. Now if an autosuspend call comes at a time when the device isn't busy but hasn't yet been idle for long enough, the timer can be set to exactly the desired value. And we will be ready to handle things like HID drivers, which can't maintain a useful usage count and must rely on the time-of-last-use to decide when to autosuspend. The patch also makes some related minor improvements: Move the calls to the autosuspend condition-checking routine into usb_suspend_both(), which is the only place where it really matters. If the autosuspend timer is already running, don't stop and restart it. Replace immediate returns with gotos so that the optional debugging ouput won't be bypassed. If autoresume is disabled but the device is already awake, don't return an error for an autoresume call. Don't try to autoresume a device if it isn't suspended. (Yes, this undercuts the previous change -- so sue me.) Don't duplicate existing code in the autosuspend work routine. Fix the kerneldoc in usb_autopm_put_interface(): If an autoresume call fails, the usage counter is left unchanged. Signed-off-by:
-
Richard Knutsson authored
Signed-off-by:
Richard Knutsson <ricknu-0@student.ltu.se> Acked-by:
Stuart MacDonald <stuartm@connecttech.com> Signed-off-by:
-
Oliver Neukum authored
omninet kills all URBs in close. However write() returns as soon as the URB has been submitted. Killing the last URB means a race that can lose that date written in the last call to write(). As a fix this is moved to shutdown(). Signed-off-by:
-
Oliver Neukum authored
we report errors to the caller. THis patch adds error handling to the driver. Signed-off-by:
-
Oliver Neukum authored
- report errors - cleanup in error case - use of endianness macros Signed-off-by:
-
Oliver Neukum authored
this driver ignores errors while starting the transmit queue. It will never be reported stopped as the completion handler won't run and it will never be started again as it will be considered started. This patch adds error handling. Signed-off-by:
-
Oliver Neukum authored
this driver sets intfdata to NULL while it still can be read and happily followed. Signed-off-by:
-
Oliver Neukum authored
this driver has a memory leak in an error case. Signed-off-by:
-
Jelle Foks authored
This patch adds the USB ID of the ADS Tech USBX-707 USB IR blaster (that comes with the ADS Tech PTV-305 grabber card), which has a ftdi232bm inside hooked up to a pic. With this it should be fairly straightforward to make at least lirc receiving work with this device. I will submit a patch to lirc for that as soon as I have one ready, I'm getting data with minicom with this patch, but need to figure out some more details such as best/correct baudrate. Signed-off-by:
Jelle Foks <jelle@foks.8m.com> Signed-off-by:
-
Oliver Neukum authored
this has the same race as the visor driver. The counter must be incremented under the lock it is checked under. Signed-off-by:
-
Oliver Neukum authored
this fixes a small race in visor_write. Signed-off-by:
-
Oliver Neukum authored
- proper endianness macros - scheduling in interrupt in error case Signed-off-by:
Naranjo Manuel Francisco <naranjo.manuel@gmail.com>
-
Kay Sievers authored
o The "real" usb-devices export now a device node which can populate /dev/bus/usb. o The usb_device class is optional now and can be disabled in the kernel config. Major/minor of the "real" devices and class devices are the same. o The environment of the usb-device event contains DEVNUM and BUSNUM to help udev and get rid of the ugly udev rule we need for the class devices. o The usb-devices and usb-interfaces share the same bus, so I used the new "struct device_type" to let these devices identify themselves. This also removes the current logic of using a magic platform-pointer. The name of the device_type is also added to the environment which makes it easier to distinguish the different kinds of devices on the same subsystem. It looks like this: add@/devices/pci0000:00/0000:00:1d.1/usb2/2-1 ACTION=add DEVPATH=/devices/pci0000:00/0000:00:1d.1/usb2/2-1 SUBSYSTEM=usb SEQNUM=1533 MAJOR=189 MINOR=131 DEVTYPE=usb_device PRODUCT=46d/c03e/2000 TYPE=0/0/0 BUSNUM=002 DEVNUM=004 This udev rule works as a replacement for usb_device class devices: SUBSYSTEM=="usb", ACTION=="add", ENV{DEVTYPE}=="usb_device", \ NAME="bus/usb/$env{BUSNUM}/$env{DEVNUM}", MODE="0644" Updated patch, which needs the device_type patches in Greg's tree. I also got a bugzilla assigned for this. :) https://bugzilla.novell.com/show_bug.cgi?id=250659Signed-off-by:Kay Sievers <kay.sievers@vrfy.org> Signed-off-by:
-
