summaryrefslogtreecommitdiffstats
path: root/sys/dev/usb/uhci.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Revert previous. uvideo checks the transfered length of every frame andmpi2015-06-261-1/+2
| | | | | | this break some devices. As found the hardway by Hugo Sastre via sobrado@
* Do not update frame lengths to reflect what has really been transferedmpi2015-06-221-2/+1
| | | | | | | | when an isochronous transfer is done. Frame lengths are just input values and no driver mess with them. ok ratchov@, jmatthew@
* Remove some includes include-what-you-use claims don'tjsg2015-03-141-2/+1
| | | | | | | have any direct symbols used. Tested for indirect use by compiling amd64/i386/sparc64 kernels. ok tedu@ deraadt@
* Use <sys/endian.h> instead of <machine/endian.h>guenther2014-12-191-2/+2
| | | | ok dlg@ mpi@ bcook@ millert@ miod@
* Avoid premature masking in the interrupt handler code that checks for removedkettenis2014-12-171-5/+6
| | | | | | hardware. ok mpi@, deraadt@
* More malloc() -> mallocarray() in the kernel.doug2014-12-091-2/+3
| | | | ok deraadt@ tedu@
* XFER_FREE is not used, ciao.mpi2014-10-301-6/+1
|
* Since USB xfer pools are accessed in interrupt context, initialize themmpi2014-08-101-1/+2
| | | | with the correct ipl to prevent your CPU from locking against itself.
* Set and check for XFER_BUSY in the common methods instead of doing itmpi2014-08-101-9/+2
| | | | in every HC driver.
* Only check if the abort transfer is the interrupt one if the pipe ismpi2014-08-051-2/+2
| | | | | | | | | | | opened with a callback. If a driver opens an interrupt pipe without callback function, like umct(4) does with one of its bulk in endpoints being reported as an interrupt endpoint, then we can end up aborting a transfer which is different from the interrupt one. Issue reported by Roberto E. Vargas Caballero, ok deraadt@
* Protect the freelists of transfer descriptors with the appropriate splmpi2014-07-121-10/+14
| | | | | | | | | | | so that we do not end up allocating two times new descriptors. This happens if a thread finds an empty list, start allocating, got interrupted and the interrupt also finds an empty list. Fix an issue reported by Nils Frohberg. ok yuo@, pirofti@
* add a size argument to free. will be used soon, but for now default to 0.tedu2014-07-121-5/+5
| | | | after discussions with beck deraadt kettenis.
* Do not set the bus dying flag during DVACT_DEACTIVATE otherwise thempi2014-07-101-5/+1
| | | | | | | | explore thread will not disconnect the root hub. The flag will be set before detaching the children, like it is done during a suspend- resume cycle. Fix a panic when unplugging a cardbus *hci(4).
* Adds an optional bus function to set the address of a new device andmpi2014-07-091-1/+2
| | | | | | | | | explicitly set it when required. Right now xhci(4) does not need such function because it assigns addresses when the first pipe of a device is opened. ok yuo@, pirofti@
* Clearing the data toggle bit only makes sense for endpoints that use it,mpi2014-06-041-11/+1
| | | | | | since this function is optional get rid of the no-op ones. ok ratchov@
* Use C99 initializers for pipe and bus methods.mpi2014-06-041-42/+42
| | | | | | | Apart from improving readability, this will help us reduce the number of no-op functions now that some of them are optional. ok ratchov@
* Remove unused fields from the pipes.mpi2014-05-301-9/+1
|
* The default case in uhci_deactivate() was missing. Because of that,mpi2014-05-251-1/+4
| | | | | | | DVACT_QUIESCE was not passed to usb(4) and a new uhub(4) device was reattached at every resume. Problem reported by mlarkin@
* unbreak the build when DIAGNOSTIC is not definedjsg2014-05-191-1/+3
| | | | allows ramdisk kernels to build again
* Do not pass an xfer pointer to the timeout routine checking for root hubmpi2014-05-181-43/+26
| | | | | | | | | | status changes because it might be freed when detaching the root uhub(4). Also do not reschedule a timeout if the pipe is being aborted. Finally do not add more code to retrieve the 'bInterval' value of the root hub endpoint descriptor since this value is hardcoded in the uhci(4) driver.
* Reduce the difference between HC drivers by always passing a genericmpi2014-05-161-28/+27
| | | | | usbd_xfer pointer to the routines processing finished transfers to make it crystal clear that the timeout and abort logic is the same everywhere.
* There is no need to remember which usb(4) device is the child of an USBmpi2014-05-161-8/+6
| | | | host controller because autoconf(9) already does it.
* Plug an xfer leak when detaching root hubs.mpi2014-05-091-9/+4
| | | | | | | | | This leak is similar to the public xfer leak #1 that was affecting device interrupt pipes except that root hubs are rarely detached. Note that this xfer is never associated to any TD and is just used to indicate that some of the HC ports has changed status, so there is no need to flag it as "done" before completing it.
* Plug one more xfer leak.mpi2014-05-081-1/+4
| | | | | | Now that aborting interrupt pipes does not prevent us from freeing the associated xfer, make sure to flag this xfer as "done" even if there's no need to abort it in hardware.
* Make use of usbd_xfer_isread() instead of rerolling it everywhere.mpi2014-05-041-47/+38
| | | | | | | This has the side effect of simplifying and reducing the differences between the various *hci_alloc_*_chain() functions since they are the principal place where we want to known if the transfer is a read or a write.
* Get rid of the per-softc freelist of transfer descriptors and use ampi2014-04-291-45/+27
| | | | per-driver pool(9) instead.
* Finally plug the public xfer leak #1 in our USB stack.mpi2014-04-291-7/+3
| | | | | | | | | | | | | | | | Every call to usbd_abort_pipe() on an interrupt pipe would simply reset the intrxfer pointer, which would prevent usbd_close_pipe() to free it. Since we abort pipes in a lot of situations: when a device is detached, when a USB-to-serial adapter is closed, when an error occurs, when the machine is suspended, etc, this would result in hundreds of leaked xfers in most of my machines. xhci(4) is not affected, but you can't enable it right now since the stack is not ready :) While here put a KASSERT() to make sure drivers are only calling the interrupt abort method for intrxfer, if that's not the case, please let met know.
* Start de-obfuscating the HC drivers.mpi2014-04-271-112/+105
| | | | | | | | | Since pipe methods have an xfer argument, always use it to get acces to various data structure (pipe, bus, device) instead of having a different way to get a pointer to these descriptors in every function. Also kill the {E,U}XFER() macro and use a consistent name accross all the methods for {e,u}hci_xfer.
* Instead of matching root hubs with a custom address, that only worksmpi2014-03-251-6/+5
| | | | | | | because USB_START_ADDR is defined to 0 and the softc is M_ZERO'd, assume that root hubs are the only devices with a depth of 0. Root hubs can now happily be detached and reattached.
* Unify the *hci_timeout() functions, there should be no functional change.mpi2014-03-151-14/+7
|
* Kill dead links.mpi2014-03-111-11/+1
|
* Transfer descriptors already have a back pointer to the USB devicempi2014-03-071-14/+12
| | | | | | | descriptor they are linked to, so no need to dereference their pipe pointer. Simplify a lot of affectations, no functional change. ok pirofti@
* We already have three identical copies of the *hci_str() function,mpi2014-03-071-22/+4
| | | | | so merge them into usbd_str() to not introduce other copies with the upcoming HC drivers.
* Mark a few functions with __unused.brad2013-12-091-4/+4
| | | | | | | | ohci.c:193:1: error: unused function 'OREAD1' [-Werror,-Wunused-function] ohci.c:200:1: error: unused function 'OREAD2' [-Werror,-Wunused-function] uhci.c:256:1: error: unused function 'UREAD4' [-Werror,-Wunused-function] ok deraadt@
* In our USB world, timeouts are in milliseconds, so use timeout_add_msec()mpi2013-11-091-7/+5
| | | | | | coherently through all our controller drivers and kill the mstohz() macro. ok pirofti@
* In polling mode since r1.101 we could end up dereferencing anmpi2013-11-071-9/+11
| | | | | | | | | uninitialized variable in case the transfer we were waiting for timed out; problem reported by oga@bitrig. So bring uhci_waitintr() in sync with its equivalent in ohci(4) and ehci(4), stop using an uhci_xfer, do not dereference it and set the correct status of the transfer.
* Make sure to mark the controller as dying in order to stop processingmpi2013-11-071-1/+2
| | | | | | | | any transfer when autoconf(9) asks for it. This brings uhci(4) in sync with ohci(4) and ehci(4). ok pirofti@
* Reduce the differences with ehci(4)'s transfer decriptors. This is ampi2013-11-011-169/+141
| | | | | | | first step to merge the code of our controllers that deal with usbd transfers. Tested with miod@
* Move the abort_task storage to the generic USB xfer structure insteadmpi2013-11-011-6/+6
| | | | of defining it in every controller specific structure.
* Bring ohci(4) and uhci(4) in sync with ehci(4) by ensuring that ampi2013-06-251-6/+3
| | | | | | | | | | transfer is submitted when a zero-length bulk or interrupt transfer is requested. This is the missing part of FreeBSD's svn r159024 that should have been committed with ehci's r1.57. ok uebayasi@
* Enforce ca_activate tree-walks over the entire heirarchy for all events,deraadt2013-05-301-18/+7
| | | | | | cleaning up some shutdown-hook related code on the way. (A few drivers related to sparc are still skipped at kettenis' request) ok kettenis mlarkin, tested by many others too
* Remove `abort_task' from usb task queue before recycling a `structyasuoka2013-05-201-1/+4
| | | | | | | | | usbd_xfer object' which includes the `abort_task'. Otherwise usb_abort_task_thread() may try to dequeue the recycled task then it causes panic with page fault. reported by Edd Barrett and Wade, Daniel. ok mpi
* Remove allocm() and freem() from the USB bus interface now that theympi2013-04-191-20/+1
| | | | | | are only used as wrappers around usb_{alloc,free}mem(). ok deraadt@, mglocker@
* Don't be too clever when allocating a buffer for a transfer and do notmpi2013-04-161-27/+14
| | | | | | pre-allocate TDs to put them in the free list. ok deraadt@, mglocker@
* Get rid of various 'typedef struct' definitions and use plain structuremglocker2013-04-151-285/+287
| | | | | | | | | definitions instead. We don't change usb.h for now to stay compatible with userland. Tested by mpi@ on macppc and myself on i386. ok mpi@
* proc.h is way too much header for usb to handle.tedu2013-03-281-2/+1
|
* Fix typos in DPRINTF() so error messages refer to correct *hci.krw2012-08-171-2/+2
| | | | Spotted by Artturi Alm. Thanks!
* Make all *_device_*_start() functions (e.g. ohci_device_intr_start())krw2012-08-071-1/+10
| | | | | | | | | | wait for an interrupt when the bus is in polling mode. Otherwise some devices like my YE-Data USB Floppy take a short sharp trip to ddb> at 'halt -p'. Most of the functions were already doing the wait. ok miod@. With modification that printf's become DPRINTF's.
* Remove config_activate() and DVACT_ACTIVATE. PCMCIA's the only thingmatthew2011-07-031-3/+1
| | | | | | | | that's ever used it, and it's long since been changed to use DVACT_{QUIESCE,SUSPEND,RESUME} instead. ok deraadt@, dlg@; miod@ also agreed with this idea when I brought it up a few weeks ago
* use the dying flag in struct usbd_bus instead of a private dying flagjakemsr2010-12-141-16/+16
| | | | | | in *hci_softc ok miod@, krw@