Lines Matching refs:HID

2 UHID - User-space I/O driver support for HID subsystem
5 UHID allows user-space to implement HID transport drivers. Please see
6 hid-transport.rst for an introduction into HID transport drivers. This document
22 If a new device is detected by your HID I/O Driver and you want to register this
23 device with the HID subsystem, then you need to open /dev/uhid once for each
51 UHID_OPEN event, the internally attached HID Device Driver has no user attached.
54 user closes the HID device, you will receive a UHID_CLOSE event. This may be
57 UHID_OPEN events without a UHID_CLOSE event. The HID subsystem performs
62 If you want to send data on the interrupt channel to the HID subsystem, you send
91 This creates the internal HID device. No I/O is possible until you send this
96 This destroys the internal HID device. No further I/O will be accepted. There
105 on the interrupt channel. The kernel will parse the HID reports.
125 This is sent when the HID device is started. Consider this as an answer to
144 This is sent when the HID device is stopped. Consider this as an answer to
149 reloaded/changed the device driver loaded on your HID device (or some other
155 This is sent when the HID device is opened. That is, the data that the HID
162 This is sent when there are no more processes which read the HID data. It is
166 This is sent if the HID device driver wants to send raw data to the I/O
173 on the control channel as described in the HID specs. The report-type and
178 Once you read a GET_REPORT request, you shall forward it to the HID device and
179 remember the "id" field in the payload. Once your HID device responds to the
187 send a SET_REPORT request to your HID device. Once it replies, you must tell