Home
last modified time | relevance | path

Searched full:hcds (Results 1 – 23 of 23) sorted by relevance

/linux/Documentation/driver-api/usb/
H A Derror-codes.rst11 Some of them are returned by the Host Controller Drivers (HCDs), which
12 device drivers only see through usbcore. As a rule, all the HCDs should
84 This is because otherwise there would be a race between HCDs updating
H A Ddma.rst26 it first and set ``URB_NO_TRANSFER_DMA_MAP``. HCDs
/linux/drivers/usb/host/
H A Dohci-sa1111.c171 * ohci_hcd_sa1111_probe - initialize SA-1111-based HCDs
255 * ohci_hcd_sa1111_remove - shutdown processing for SA-1111-based HCDs
H A Dehci-fsl.c40 * fsl_ehci_drv_probe - initialize FSL-based HCDs
670 * fsl_ehci_drv_remove - shutdown processing for FSL-based HCDs
H A Dohci-at91.c170 * usb_hcd_at91_probe - initialize AT91-based HCDs
265 * usb_hcd_at91_remove - shutdown processing for AT91-based HCDs
H A Dohci.h98 /* these two bits are available for definition/use by HCDs in both
H A Dxhci.c714 /* Only halt host and free memory after both hcds are removed */ in xhci_stop()
1448 * HCDs. Find the index for an endpoint given its descriptor. Use the return
/linux/include/linux/usb/
H A Dotg.h82 /* for HCDs */
H A Dhcd.h154 /* The next flag is a stopgap, to be removed when all the HCDs
/linux/drivers/mfd/
H A Domap-usb-tll.c194 * usbtll_omap_probe - initialize TI-based HCDs
267 * usbtll_omap_remove - shutdown processing for UHH & TLL HCDs
/linux/drivers/usb/core/
H A Durb.c399 /* Lots of sanity checks, so HCDs can rely on clean data in usb_submit_urb()
503 * cause problems in HCDs if they get it wrong. in usb_submit_urb()
537 * a power of two (so HCDs don't need to). in usb_submit_urb()
633 * Host Controller Drivers (HCDs) place all the URBs for a particular
H A Dhcd-pci.c158 * usb_hcd_pci_probe - initialize PCI-based HCDs
300 * usb_hcd_pci_remove - shutdown processing for PCI-based HCDs
H A Dhcd.c50 * Plugs into usbcore (usb_bus) and lets HCDs share code, minimizing
87 /* used when updating list of hcds */
1013 * HCDs should call this function when they know that a resume signal is
1035 * HCDs should call this function when they know that a resume signal has
2867 * bottom up so that hcds can customize the root hubs before hub_wq in usb_add_hcd()
3020 * usb_remove_hcd - shutdown processing for generic HCDs
H A Ddevices.c458 * the schedules are actually bursty, HCDs need to deal with in usb_device_dump()
H A Dconfig.c498 * maxpacket sizes other than 512. High speed HCDs may not in usb_parse_endpoint()
H A Dhub.c833 * long blocking there is the exception, not the rule. accordingly, HCDs
910 * High speed HCDs use this to tell the hub driver that some split control or
2174 * usb_set_device_state - change a device's current state (usbcore, hcds)
H A Dmessage.c471 /* In 2.5 we require hcds' endpoint queues not to progress after fault in sg_complete()
/linux/include/uapi/linux/usb/
H A Dch11.h6 * It is used/shared between the USB core, the HCDs and couple of other USB
/linux/include/linux/
H A Dusb.h316 * That way we will have a 'stable' behavior among all HCDs supported by Linux.
1395 /* The following flags are used internally by usbcore and HCDs */
/linux/drivers/usb/fotg210/
H A Dfotg210-hcd.c2690 * That'd mean updating how usbcore talks to HCDs. (2.7?)
4900 * keep io watchdog by default, those good HCDs could turn off it later in hcd_fotg210_init()
5544 * fotg210_hcd_probe - initialize faraday FOTG210 HCDs
5609 * fotg210_hcd_remove - shutdown processing for EHCI HCDs
/linux/drivers/usb/misc/
H A Dusbtest.c816 * halt or toggle). toggle testing is impractical without support from hcds.
1816 * is pretty weak. Some HCDs place limits here; most devices will
/linux/drivers/usb/gadget/udc/
H A Ddummy_hcd.c2506 * just like more familiar pci-based HCDs. in dummy_start()
/linux/drivers/net/usb/
H A Dusbnet.c441 /* some LK 2.4 HCDs oopsed if we freed or resubmitted urbs from