Lines Matching refs:must

69 must unregister the device from HID core and HID core will stop using the
76 transmission behavior regarding acknowledgements. An asynchronous channel must
78 verifications. Generally, HID calls operating on asynchronous channels must be
84 required on asynchronous channels, a transport-driver must implement that via
88 driver must provide two bi-directional I/O channels to each HID device. These
89 channels must not necessarily be bi-directional in the hardware itself. A
97    channel. Any unrequested incoming or outgoing data report must be sent on
102    device management. Unrequested data input events must not be sent on this
127    Feature reports are never sent without requests. A host must explicitly set
137 Plain reports must not be sent on the ctrl channel, though. Instead, the ctrl
142    from host to device. The device must answer with a data report for the
160    sent from host to device and a device must update it's current report state
164    A device must answer with a synchronous acknowledgement. However, HID core
247    However, once ->open() is called, transport drivers must be ready for I/O.
260    drivers must read the HID report-descriptor from the device and tell HID core
285    be synchronous. A transport driver must not use ->wait() to complete such
292    must not cause SET_REPORT calls! This must be implemented as asynchronous
301 Transport drivers are responsible of reading data from I/O devices. They must
306 Every raw data packet read from a device must be fed into HID core via
307 hid_input_report(). You must specify the channel-type (intr or ctrl) and report
311 Responses to GET_REPORT requests via ->request() must also be provided via this
312 API. Responses to ->raw_request() are synchronous and must be intercepted by the