Lines Matching refs:report

16 report-parsing, report interpretation and the user-space API. Device specifics
97    channel. Any unrequested incoming or outgoing data report must be sent on
111 report can be of one of three types:
128    or retrieve a feature report. This also means, feature reports are never sent
141  - GET_REPORT: A GET_REPORT request has a report ID as payload and is sent
142    from host to device. The device must answer with a data report for the
143    requested report ID on the ctrl channel as a synchronous acknowledgement.
150    the raw data report on the intr channel on state change.
155    GET_REPORT requests can be sent for any of the 3 report types and shall
156    return the current report state of the device. However, OUTPUT reports as
159  - SET_REPORT: A SET_REPORT request has a report ID plus data as payload. It is
160    sent from host to device and a device must update it's current report state
161    according to the given data. Any of the 3 report types can be used. However,
260    drivers must read the HID report-descriptor from the device and tell HID core
267  - void (*request) (struct hid_device *hdev, struct hid_report *report,
269    Send an HID request on the ctrl channel. "report" contains the report that
273    report following the HID specs and send it via the ->raw_request() callback.
284    Same as ->request() but provides the report as raw buffer. This request shall
290    Send raw output report via intr channel. Used by some HID device drivers
293    output report on the intr channel!
295  - int (*idle) (struct hid_device *hdev, int report, int idle, int reqtype)
307 hid_input_report(). You must specify the channel-type (intr or ctrl) and report