Lines Matching refs:reports
86 channels, but they can also provide acknowledgement reports, automatic
100 reports. No management commands or data acknowledgements are sent on this
111 Outgoing reports are usually sent on the ctrl channel via synchronous
114 Communication between devices and HID core is mostly done via HID reports. A
117 - INPUT Report: Input reports provide data from device to host. This
122 - OUTPUT Report: Output reports change device states. They are sent from host
124 reports are never sent from device to host, but a host can retrieve their
126 Hosts may choose to send output reports either continuously or only on
128 - FEATURE Report: Feature reports are used for specific static device features
131 Feature reports are never sent without requests. A host must explicitly set
132 or retrieve a feature report. This also means, feature reports are never sent
135 INPUT and OUTPUT reports can be sent as pure data reports on the intr channel.
136 For INPUT reports this is the usual operational mode. But for OUTPUT reports,
137 this is rarely done as OUTPUT reports are normally quite scarce. But devices are
138 free to make excessive use of asynchronous OUTPUT reports (for instance, custom
141 Plain reports must not be sent on the ctrl channel, though. Instead, the ctrl
142 channel provides synchronous GET/SET_REPORT requests. Plain reports are only
151 Note that data reports which are sent as answer to a GET_REPORT request are
160 return the current report state of the device. However, OUTPUT reports as
166 INPUT reports as payload might be blocked by the underlying transport driver
259 Called from HID device drivers once they are interested in data reports.
270 longer interested in device reports. (Usually if user-space closed any input
275 be called again if the device driver is interested in input reports again.
349 type (input/output/feature). Under normal conditions, only input reports are