| /Linux-v5.15/Documentation/hid/ |
| D | hid-transport.rst | 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
[all …]
|
| D | hidraw.rst | 6 Interface Devices (HIDs). It differs from hiddev in that reports sent and
12 reports manually. This is often the case when making userspace drivers for
17 descriptors. Because hiddev parses reports which are sent and received
45 devices, the reports read using read() are the reports sent from the device
51 On a device which uses numbered reports, the first byte of the returned data
53 byte. For devices which do not use numbered reports, the report data
64 number. If the device does not use numbered reports, the first byte should
115 specification, feature reports are always sent using the control endpoint.
117 which do not use numbered reports, set the first byte to 0. The report data
127 reports, set the first byte to 0. The returned report buffer will contain the
[all …]
|
| D | hid-alps.rst | 31 14 wMaxOutputLength 0000 No Output Reports
45 ReportID-1 (Input Reports) (HIDUsage-Mouse) for TP&SP
46 ReportID-2 (Input Reports) (HIDUsage-keyboard) for TP
47 ReportID-3 (Input Reports) (Vendor Usage: Max 10 finger data) for TP
48 ReportID-4 (Input Reports) (Vendor Usage: ON bit data) for GP
49 ReportID-5 (Feature Reports) Feature Reports
50 ReportID-6 (Input Reports) (Vendor Usage: StickPointer data) for SP
51 ReportID-7 (Feature Reports) Flash update (Bootloader)
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-class-power | 7 Reports the name of the device manufacturer.
16 Reports the name of the device model.
25 Reports the serial number of the device.
47 Reports an average IBAT current reading for the battery, over
54 Reports an average IBUS current reading over a fixed period.
70 Reports the maximum IBAT current allowed into the battery.
74 Reports the maximum IBUS current the supply can support.
86 Reports an instant, single IBAT current reading for the
93 Reports the IBUS current supplied now. This value is generally
110 Reports the current TBAT battery temperature reading.
[all …]
|
| D | sysfs-pps | 21 The /sys/class/pps/ppsX/assert file reports the assert events
33 The /sys/class/pps/ppsX/clear file reports the clear events
45 The /sys/class/pps/ppsX/mode file reports the functioning
55 The /sys/class/pps/ppsX/echo file reports if the X-th does
62 The /sys/class/pps/ppsX/name file reports the name of the
69 The /sys/class/pps/ppsX/path file reports the path name of
|
| D | sysfs-class-remoteproc | 6 Reports the name of the firmware currently loaded to the
17 Reports the state of the remote processor, which will be one of:
58 Reports the name of the remote processor. This can be used by
67 Reports the coredump configuration of the remote processor,
91 Reports the recovery mechanism of the remote processor,
|
| D | sysfs-driver-input-exc3000 | 4 Description: Reports the firmware version provided by the touchscreen, for example "00_T6" on a …
13 Description: Reports the model identification provided by the touchscreen, for example "Orion_13…
22 Description: Reports the type identification provided by the touchscreen, for example "PCAP82H80 Se…
|
| /Linux-v5.15/drivers/hid/ |
| D | hid-uclogic-rdesc.h | 106 /* Report ID for v1 pen reports */
109 /* Fixed report descriptor template for (tweaked) v1 pen reports */
113 /* Report ID for v2 pen reports */
116 /* Fixed report descriptor template for (tweaked) v2 pen reports */
120 /* Fixed report descriptor for (tweaked) v1 buttonpad reports */
124 /* Report ID for tweaked v1 buttonpad reports */
127 /* Fixed report descriptor for (tweaked) v2 buttonpad reports */
131 /* Report ID for tweaked v2 buttonpad reports */
146 /* Report ID of Ugee G5 frame control reports */
|
| D | hid-uclogic-params.h | 24 /* Normal reports: zero - out of proximity, one - in proximity */
26 /* Inverted reports: zero - in proximity, one - out of proximity */
28 /* No reports */
55 /* Report ID, if reports should be tweaked, zero if not */
60 * True, if reports include fragmented high resolution coords, with
87 * Report ID, if reports should be tweaked, zero if not.
112 * reports unchanged and lets the generic HID driver handle everything.
|
| D | hid-gfrm.c | 63 * Convert GFRM100 Search key reports into Consumer.0221 (Key.Search) in gfrm_raw_event()
64 * reports. Ignore audio data. in gfrm_raw_event()
111 * key reports. Thus, we need to add it manually here, so that in gfrm_probe()
112 * those reports reach gfrm_raw_event() from hid_input_report(). in gfrm_probe()
|
| /Linux-v5.15/drivers/hid/usbhid/ |
| D | hid-pidff.c | 25 /* Report usage table used to put reports into an array */
147 struct hid_report *reports[sizeof(pidff_reports)]; member
254 hid_hw_request(pidff->hid, pidff->reports[PID_SET_ENVELOPE], in pidff_set_envelope_report()
281 hid_hw_request(pidff->hid, pidff->reports[PID_SET_CONSTANT], in pidff_set_constant_force_report()
316 hid_hw_request(pidff->hid, pidff->reports[PID_SET_EFFECT], in pidff_set_effect_report()
348 hid_hw_request(pidff->hid, pidff->reports[PID_SET_PERIODIC], in pidff_set_periodic_report()
366 * Send condition effect reports to the device
390 hid_hw_request(pidff->hid, pidff->reports[PID_SET_CONDITION], in pidff_set_condition_report()
431 hid_hw_request(pidff->hid, pidff->reports[PID_SET_RAMP], in pidff_set_ramp_force_report()
456 hid_hw_request(pidff->hid, pidff->reports[PID_CREATE_NEW_EFFECT], in pidff_request_effect_upload()
[all …]
|
| /Linux-v5.15/Documentation/userspace-api/media/rc/ |
| D | lirc-set-rec-timeout-reports.rst | 13 LIRC_SET_REC_TIMEOUT_REPORTS - enable or disable timeout reports for IR receive
30 reports.
37 Enable or disable timeout reports for IR receive. By default, timeout reports
|
| D | lirc-set-wideband-receiver.rst | 47 carrier reports. In that case it will be disabled as soon as you disable
48 carrier reports. Trying to disable wide band receiver while carrier
49 reports are active will do nothing.
|
| /Linux-v5.15/drivers/usb/serial/ |
| D | keyspan_usa90msg.h | 156 u8 msr, // reports the actual MSR register
157 cts, // reports CTS pin
158 dcd, // reports DCD pin
159 dsr, // reports DSR pin
160 ri, // reports RI pin
162 rxBreak, // reports break state
|
| D | keyspan_usa26msg.h | 209 hskia_cts, // USA26: reports HSKIA pin
210 // USA17: reports CTS pin
211 gpia_dcd, // USA26: reports GPIA pin
212 // USA17: reports DCD pin
213 dsr, // USA17: reports DSR pin
214 ri, // USA17: reports RI pin
|
| /Linux-v5.15/Documentation/dev-tools/ |
| D | kasan.rst | 56 To include alloc and free stack traces of affected slab objects into reports,
60 Error reports
169 Generic KASAN also reports up to two auxiliary call stack traces. These stack
182 effectively disables ``panic_on_warn`` for KASAN reports.
204 only reports tag faults during these checks.
273 dedicated ``brk`` handler is used to print bug reports.
313 Hardware tag-based KASAN only reports the first found bug. After that, MTE tag
387 Normally, KASAN detects and reports such accesses, but in some cases (e.g.,
412 For software KASAN modes, to disable KASAN reports in a part of the kernel code
415 disables the reports for indirect accesses that happen through function calls.
[all …]
|
| /Linux-v5.15/lib/ |
| D | Kconfig.kcsan | 53 bool "Show verbose reports with more information about system state"
56 If enabled, reports show more information about the system state that
80 various race scenarios, and verifies the reports generated to
169 Different races may still generate reports within a duration that is
171 reporting to avoid flooding the console with reports. Setting this
224 plain reads and marked writes to result in "unknown origin" reports.
|
| /Linux-v5.15/drivers/gpu/drm/i915/ |
| D | i915_perf.c | 75 * the constraints on HW configuration require reports to be filtered before it
114 * The OA unit writes reports of counters into a circular buffer, without
134 * feature and forwarded OA reports to userspace via perf's 'raw' sample
138 * them. For Mesa it's also convenient to be forwarded raw, periodic reports
139 * for combining with the side-band raw reports it captures using
169 * attach GPU timestamps to our OA samples. We were shoehorning OA reports
227 * Although this can be observed explicitly while copying reports to userspace
228 * by checking for a zeroed report-id field in tail reports, we want to account
232 * We workaround this issue in oa_buffer_check_unlocked() by reading the reports
248 * non-periodic reports (such as on context switch) or the OA unit may be
[all …]
|
| /Linux-v5.15/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 46 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
97 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
106 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
182 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
215 :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
|
| /Linux-v5.15/Documentation/trace/ |
| D | osnoise-tracer.rst | 22 interrupts and reports the max observed gap between the reads. It also
80 - The RUNTIME IN US reports the amount of time in microseconds that
82 - The NOISE IN US reports the sum of noise in microseconds observed
84 - The % OF CPU AVAILABLE reports the percentage of CPU available for
86 - The MAX SINGLE NOISE IN US reports the maximum single noise observed
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | ltc2978.rst | 323 and temp 3 reports the chip temperature.
325 temperatures, and temp5 reports the chip temperature.
328 reports the chip temperature.
332 temperatures, and temp3 reports the chip temperature.
333 - On LTC3883, temp1 reports an external temperature,
334 and temp2 reports the chip temperature.
|
| /Linux-v5.15/Documentation/admin-guide/ |
| D | reporting-issues.rst | 23 <https://lore.kernel.org/stable/>`_ archives for matching reports to join. If
33 mailing list in CC. Check the destination's archives for matching reports;
83 * Perform a rough search for existing reports with your favorite internet
85 List (LKML) <https://lore.kernel.org/lkml/>`_. If you find matching reports,
115 Find out how and where its developers expect reports. Note: most of the
120 thoroughly for reports that might match your issue. If you find anything,
145 process, consider searching again for existing reports about the issue.
193 <https://lore.kernel.org/stable/>`_ for existing reports.
294 with reports for issues that don't even happen with their current code. It's
317 developers in fact are willing to handle reports about issues occurring with
[all …]
|
| /Linux-v5.15/Documentation/ia64/ |
| D | aliasing.rst | 162 If the EFI memory map reports that the entire granule supports
188 The EFI memory map reports the following attributes:
208 If the EFI memory map reports that the entire range supports the
213 If EFI reports the range as partly WB and partly UC (as on sx[12]000
217 If EFI reports some of the range but not all (as on Intel firmware
224 The EFI memory map reports the following attributes::
|
| /Linux-v5.15/Documentation/misc-devices/ |
| D | ics932s401.rst | 24 clock, and a reference clock. The driver reports selected and actual
25 frequency. If spread spectrum mode is enabled, the driver also reports by what
|
| /Linux-v5.15/Documentation/devicetree/bindings/hwmon/ |
| D | amd,sbrmi.yaml | 16 interface that reports AMD SoC's Power (normalized Power) using,
19 reports power in microwatts.
|
