Lines Matching refs:by

17 and quirks are handled by all layers depending on the quirk.
64 this struct are used by HID core to communicate with the device.
80 On the other hand, synchronous channels can be implemented by the transport
98    this channel and is never acknowledged by the remote side. Devices usually
115    data is generated by the device and sent to the host with or without
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.
157    payload may be blocked by the underlying transport driver if the
162    INPUT reports as payload might be blocked by the underlying transport driver
168    restriction is enforced by HID core as some transport drivers do not support
171 Other ctrl-channel requests are supported by USB-HID but are not available
174  - GET/SET_IDLE: Only used by USB-HID and I2C-HID.
175  - GET/SET_PROTOCOL: Not used by HID core.
176  - RESET: Used by I2C-HID, not hooked up in HID core.
177  - SET_POWER: Used by I2C-HID, not hooked up in HID core.
215 "custom_ll_driver". Note that fields like "country" can be ignored by underlying
233    so this is mostly only used by USB-HID.
255    ->open() calls have been followed by a ->close() call. However, ->start() may
264    Called by HID core to give PM hints to transport drivers. Usually this is
277    Used by HID core before calling ->request() again. A transport driver can use
290    Send raw output report via intr channel. Used by some HID device drivers
296    Perform SET/GET_IDLE request. Only used by USB-HID, do not implement!
303 protocol handshakes or other management commands which can be required by the
312 API. Responses to ->raw_request() are synchronous and must be intercepted by the