Searched full:usbcore (Results 1 – 25 of 30) sorted by relevance
12
9 usbcore-y := usb.o hub.o hcd.o urb.o message.o driver.o10 usbcore-y += config.o file.o buffer.o sysfs.o endpoint.o11 usbcore-y += devio.o notify.o generic.o quirks.o devices.o12 usbcore-y += phy.o port.o trace.o14 usbcore-$(CONFIG_OF) += of.o15 usbcore-$(CONFIG_USB_XHCI_SIDEBAND) += offload.o16 usbcore-$(CONFIG_USB_PCI) += hcd-pci.o17 usbcore-$(CONFIG_ACPI) += usb-acpi.o20 usbcore-y += ../misc/onboard_usb_dev_pdevs.o23 obj-$(CONFIG_USB) += usbcore.o
114 with the usbcore.autosuspend command line or module parameter.127 with usbcore.authorized_default command line or module parameter.
6 #define TRACE_SYSTEM usbcore
51 const char *usbcore_name = "usbcore";629 * usb_alloc_dev - usb device constructor (usbcore-internal)873 * time. Only hub-aware drivers that are part of usbcore ever have to
22 #include <linux/usb/hcd.h> /* for usbcore internals */1449 * pending urbs) and usbcore state for the interfaces, so that usbcore1675 * should hcd+usbcore postprocess control requests? in usb_set_interface()1735 * endpoints). Other usbcore state is unchanged, including bindings of2157 * hc/hcd/usbcore interface/endpoint state. in usb_set_configuration()
258 * provided by usbcore or the HCD until its complete() is called.
4 What callbacks will usbcore do?7 Usbcore will call into a driver through callbacks defined in the driver85 You are strongly encouraged to use usbcore's facility,107 killed by usbcore. Note that in this case disconnect will be called some
205 a module parameter in usbcore. You can specify the value when usbcore209 modprobe usbcore autosuspend=5214 options usbcore autosuspend=5216 Some distributions load the usbcore module very early during the boot221 If usbcore is compiled into the kernel rather than built as a loadable224 usbcore.autosuspend=5231 echo 5 >/sys/module/usbcore/parameters/autosuspend633 ``/sys/module/usbcore`` then unbinding it will interfere with port power
9 their interpretation) that can be returned from usbcore.12 device drivers only see through usbcore. As a rule, all the HCDs should193 Error codes returned by usbcore-functions
25 - "usbcore" will map this DMA address, if a DMA-aware driver didn't do
58 "usbcore.autosuspend=-1"
23 (kernel command line) usbcore.blinkenlights=124 (modprobe command line) modprobe usbcore blinkenlights=1
21 - supports the updated and simplified usbcore APIs
61 usbcore.ko
40 but those changes haven't needed to really change the basic "usbcore"
80 module will be called usbcore.
17 struct usb_host_endpoint *hep; /* usbcore info */
20 * host side, usbcore sets up the DMA mappings and flushes caches; on the
295 /* this hub status bit is reserved by USB 2.0 and not seen by usbcore */
28 the value of the usbcore.autosuspend module parameter.
17 * Derived from the USBcore related parts of Broadcom-SB
698 /* usbcore nukes other pending transactions on disconnect */ in sl811h_irq()1166 /* usbcore nukes all pending transactions on disconnect */ in sl811h_timer()
56 * @urb_list: urbs queued to this endpoint; maintained by usbcore658 * Usbcore drivers should not set usbdev->state directly. Instead use1179 * struct usb_driver - identifies USB interface driver to usbcore1279 * struct usb_device_driver - identifies USB device driver to usbcore1403 /* The following flags are used internally by usbcore and HCDs */1917 /* wrappers that also update important state inside usbcore */1961 * members below are private to usbcore,
430 * result of the submit is given back to the usbcore as the in stub_tx_loop()
514 * This is controlled through usbcore by usb autosuspend,