Lines Matching full:no

51 UHID_OPEN event, the internally attached HID Device Driver has no user attached.
55 followed by an UHID_OPEN event again and so on. There is no need to perform
60 though the device may have no users.
66 SET_REPORT (no other data reports on the control channel are defined so far).
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
97   may still be pending messages that you can receive with read() but no further
99   You can create a new device by sending UHID_CREATE2 again. There is no need to
110   field to 0 if no error occurred or to EIO if an I/O error occurred.
121 read() will return a queued output report. No reaction is required to any of
138           the kernel already have the report-number as prefix. Otherwise, no
158   there is actually no other process that reads your data so there is no need to
162   This is sent when there are no more processes which read the HID data. It is