Documentation/hid/hidraw.rst

2 HIDRAW - Raw Access to USB and Bluetooth Human Interface Devices
15 Hidraw is also useful for communicating with non-conformant HID devices
19 communication with these non-conformant devices is impossible using hiddev.
21 these non-conformant devices.
31 directly under /dev (eg: /dev/hidraw0).  As this location is distribution-
32 and udev rule-dependent, applications should use libudev to locate hidraw
40 ---------------
43 -------
47 a report available to be read.  read() can be made non-blocking, by passing
51 On a device which uses numbered reports, the first byte of the returned data
53 byte.  For devices which do not use numbered reports, the report data
54 will begin at the first byte.
57 -------
63 The first byte of the buffer passed to write() should be set to the report
64 number.  If the device does not use numbered reports, the first byte should
65 be set to 0. The report data itself should begin at the second byte.
68 -------
90 	- BUS_USB
91 	- BUS_HIL
92 	- BUS_BLUETOOTH
93 	- BUS_VIRTUAL
97 HIDIOCGRAWNAME(len):
101 the device.  The returned string is Unicode, UTF-8 encoded.
103 HIDIOCGRAWPHYS(len):
111 HIDIOCSFEATURE(len):
116 Set the first byte of the supplied buffer to the report number.  For devices
117 which do not use numbered reports, set the first byte to 0. The report data
118 begins in the second byte. Make sure to set len accordingly, to one more
121 HIDIOCGFEATURE(len):
125 endpoint.  The first byte of the supplied buffer should be set to the report
127 reports, set the first byte to 0.  The returned report buffer will contain the
128 report number in the first byte, followed by the report data read from the
130 begin at the first byte of the returned buffer.
132 HIDIOCSINPUT(len):
141 HIDIOCGINPUT(len):
152 HIDIOCSOUTPUT(len):
162 HIDIOCGOUTPUT(len):
172 -------
173 In samples/, find hid-example.c, which shows examples of read(), write(),