Lines Matching refs:drivers

6 provided new transport drivers. The kernel includes at least support for USB,
7 Bluetooth, I2C and user-space I/O drivers.
14 drivers on top of it. The transport drivers are responsible of raw data
49 interest to HID device drivers. Transport drivers do not need to know the
55 I/O drivers normally provide hotplug detection or device enumeration APIs to the
56 transport drivers. Transport drivers use this to find any suitable HID device.
58 drivers are not required to register themselves with HID core. HID core is never
59 aware of which transport drivers are available and is not interested in it. It
62 Transport drivers attach a constant "struct hid_ll_driver" object with each
66 Transport drivers are responsible of detecting device failures and unplugging.
68 device failures. Once transport drivers detect unplug or failure events, they
87 HID core requires transport drivers to follow a given design. A Transport
145    is enforced by HID core as several transport drivers don't allow multiple
151    GET_REPORT is only used by custom HID device drivers to query device state.
165    does not require transport drivers to forward this acknowledgement to HID
168    restriction is enforced by HID core as some transport drivers do not support
185 Transport drivers normally use the following procedure to register a new device
216 transport-drivers if not supported.
230    Called from HID device drivers once they want to use the device. Transport
231    drivers can choose to setup their device in this callback. However, normally
232    devices are already set up before transport drivers register them to HID core
236    Called from HID device drivers once they are done with a device. Transport
237    drivers can free any buffers and deinitialize the device. But note that
240    Transport drivers are free to ignore it and deinitialize devices after they
244    Called from HID device drivers once they are interested in data reports.
245    Usually, while user-space didn't open any input API/etc., device drivers are
246    not interested in device data and transport drivers can put devices asleep.
247    However, once ->open() is called, transport drivers must be ready for I/O.
251    Called from HID device drivers after ->open() was called but they are no
254    Transport drivers can put devices asleep and terminate any I/O of all
260    drivers must read the HID report-descriptor from the device and tell HID core
264    Called by HID core to give PM hints to transport drivers. Usually this is
290    Send raw output report via intr channel. Used by some HID device drivers
301 Transport drivers are responsible of reading data from I/O devices. They must