Lines Matching refs:kernel

8 With UHID, a user-space transport driver can create kernel hid-devices for each
10 events provided from the kernel to user-space and vice versa.
62 an HID_INPUT2 event with your raw data payload. If the kernel wants to send data
66 Those requests are always synchronous. That means, the kernel sends
69 the response via UHID_GET_REPORT_REPLY and UHID_SET_REPORT_REPLY to the kernel.
70 The kernel blocks internal driver-execution during such round-trips (times out
82 the kernel. The kernel will parse the event immediately and if the event ID is
91   event to the kernel. The payload is of type struct uhid_create2_req and
97   UHID_INPUT events can be sent to the kernel.
102   You must send UHID_CREATE2 before sending input to the kernel! This event
104   on the interrupt channel. The kernel will parse the HID reports.
135           the kernel already have the report-number as prefix. Otherwise, no
136           prefix is added by the kernel.
137           For messages sent by user-space to the kernel, you must adjust the
143   If you didn't destroy your device via UHID_DESTROY, but the kernel sends an
144   UHID_STOP event, this should usually be ignored. It means that the kernel
154   send UHID_INPUT2 events to the kernel.
167   This event is sent if the kernel driver wants to perform a GET_REPORT request
170   The kernel serializes GET_REPORT requests so there will never be two in
176   kernel with the exact same "id" as in the request. If the request already
177   timed out, the kernel will ignore the response silently. The "id" field is
183   the kernel about it via UHID_SET_REPORT_REPLY.