Lines Matching +full:non +full:- +full:compliant

18 normalised event interface - see Documentation/input/input.rst
24  usb.c ---> hid-core.c  ----> hid-input.c ----> [keyboard/mouse/joystick/event]
27                           --> hiddev.c ----> POWER / MONITOR CONTROL
57 So you point your hiddev compliant user-space program at the correct
60 Assuming that you have a hiddev compliant user-space program, of
69 conveniently linked of http://www.linux-usb.org.
75 each of which can have one or more "usages".  In the hid-core,
79 -------
83 the changed value.  The hid-core.c module parses the report, and
103 --------
108   - int (read)
113   - (none)
120 returns -1. You can find out beforehand how many application
125   - struct hiddev_collection_info (read/write)
133 index, the ioctl returns -1 and sets errno to -EINVAL.
136   - struct hiddev_devinfo (read)
141   - struct hiddev_string_descriptor (read/write)
147   - (none)
157   - string (variable length)
162   - struct hiddev_report_info (write)
169   - struct hiddev_report_info (write)
177   - struct hiddev_report_info (read/write)
181 must be filled in by the user. The ID can be absolute -- the actual
182 report id as reported by the device -- or relative --
184 report_id) for the next report after report_id. Without a-priori
187 returns non-zero when there is no more next ID. The real report ID is
191   - struct hiddev_field_info (read/write)
196 be filled in, which should be a number from 0 and maxfield-1, as
200   - struct hiddev_usage_ref (read/write)
207   - struct hiddev_usage_ref (read/write)
217   - struct hiddev_usage_ref (write)
224   - struct hiddev_usage_ref (write)
230   - int (read)
232   - int (write)
238       - read() calls will now return
246       - This flag can only be used in conjunction