Lines Matching +full:index +full:- +full:power +full:- +full:of +full:- +full:two
2 Care and feeding of your Human Interface Devices
10 interfaces, but have similar sorts of communication needs. The two big
11 examples for this are power devices (especially uninterruptible power
15 HID events to two separate interfaces:
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.
71 The hiddev API uses a read() interface, and a set of ioctl() calls.
75 each of which can have one or more "usages". In the hid-core,
76 each one of these usages has a single signed 32-bit value.
79 -------
83 the changed value. The hid-core.c module parses the report, and
96 structures. The HID usage identifier is a composite of the HID usage
98 behavior of the read() function can be modified using the HIDIOCSFLAG
103 --------
105 This is the control interface. There are a number of controls:
108 - int (read)
110 Gets the version code out of the hiddev driver.
113 - (none)
117 index to get. This is useful when the device has more than one
118 application collection. If the index is invalid (greater or equal to
119 the number of application collections this device has) the ioctl
120 returns -1. You can find out beforehand how many application
125 - struct hiddev_collection_info (read/write)
127 This returns a superset of the information above, providing not only
130 The user passes in a hiddev_collection_info struct with the index
131 field set to the index that should be returned. The ioctl fills in
132 the other fields. If the index is larger than the last collection
133 index, the ioctl returns -1 and sets errno to -EINVAL.
136 - struct hiddev_devinfo (read)
141 - struct hiddev_string_descriptor (read/write)
144 "index" field to indicate which descriptor should be returned.
147 - (none)
152 changes. Note that the use of this ioctl is unnecessary in general,
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 --
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)
203 its report type, report id, field index, and index within the
207 - struct hiddev_usage_ref (read/write)
209 Returns the value of a usage in a hiddev_usage_ref structure. The
217 - struct hiddev_usage_ref (write)
219 Sets the value of a usage in an output report. The user fills in
224 - struct hiddev_usage_ref (write)
226 Returns the collection index associated with this usage. This
230 - int (read)
232 - int (write)
238 - read() calls will now return
239 struct hiddev_usage_ref instead of struct hiddev_event.
246 - This flag can only be used in conjunction