Lines Matching refs:reports

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