Documentation/hid/hid-transport.rst

73 must unregister the device from HID core and HID core will stop using the
80 transmission behavior regarding acknowledgements. An asynchronous channel must
82 verifications. Generally, HID calls operating on asynchronous channels must be
88 required on asynchronous channels, a transport-driver must implement that via
92 driver must provide two bi-directional I/O channels to each HID device. These
93 channels must not necessarily be bi-directional in the hardware itself. A
101    channel. Any unrequested incoming or outgoing data report must be sent on
106    device management. Unrequested data input events must not be sent on this
131    Feature reports are never sent without requests. A host must explicitly set
141 Plain reports must not be sent on the ctrl channel, though. Instead, the ctrl
146    from host to device. The device must answer with a data report for the
164    sent from host to device and a device must update its current report state
168    A device must answer with a synchronous acknowledgement. However, HID core
262    However, once ->open() is called, transport drivers must be ready for I/O.
282    drivers must read the HID report-descriptor from the device and tell HID core
320    be synchronous. A transport driver must not use ->wait() to complete such
330    must not cause SET_REPORT calls! This must be implemented as asynchronous
342 Transport drivers are responsible of reading data from I/O devices. They must
347 Every raw data packet read from a device must be fed into HID core via
348 hid_input_report(). You must specify the channel-type (intr or ctrl) and report
352 Responses to GET_REPORT requests via ->request() must also be provided via this
353 API. Responses to ->raw_request() are synchronous and must be intercepted by the