| /linux/Documentation/hid/ |
| H A 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 …]
|
| H A 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 …]
|
| /linux/Documentation/ABI/testing/ |
| H A 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
|
| H A D | sysfs-bus-iio-bno055 | 49 Reports the binary calibration data blob for the IMU sensors.
55 Reports the autocalibration status for the accelerometer sensor.
63 Reports the autocalibration status for the gyroscope sensor.
71 Reports the autocalibration status for the magnetometer sensor.
79 Reports the status for the IMU overall autocalibration.
|
| H A 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,
|
| H A D | sysfs-class-regulator | 7 state. This reports the regulator enable control, for
33 "status". This reports the current regulator status, for
380 under_voltage. This indicates if the device reports an
389 over_current. This indicates if the device reports an
398 regulation_out. This indicates if the device reports an
407 fail. This indicates if the device reports an output failure
416 over_temp. This indicates if the device reports an
425 under_voltage_warn. This indicates if the device reports an
434 over_current_warn. This indicates if the device reports an
443 over_voltage_warn. This indicates if the device reports an
[all …]
|
| H A 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…
|
| H A D | sysfs-amd-pmc | 4 Description: Reading this file reports the version of the firmware loaded to
11 Description: Reading this file reports the program corresponding to the SMU
|
| /linux/Documentation/process/ |
| H A D | security-bugs.rst | 25 will not be processed. A significant part of reports are for bugs that
106 does not make them move faster and consumes triage capacity that other reports
177 A significant fraction of bug reports submitted to the security team are
180 maintainers, who are sometimes forced to ignore such reports due to their poor
182 number of points which tend to make these reports needlessly difficult to
185 * **Length**: AI-generated reports tend to be excessively long, containing
190 text. Configure your tools to produce concise, human-style reports.
192 * **Formatting**: Most AI-generated reports are littered with Markdown tags.
198 * **Impact Evaluation**: Many AI-generated reports lack an understanding
257 Reports are to be sent over e-mail exclusively. Please use a working e-mail
[all …]
|
| H A D | 6.Followthrough.rst | 162 where there are testers, there will be bug reports.
164 The worst sort of bug reports are regressions. If your patch causes a
176 release is as solid as possible. So, please, answer bug reports, and fix
182 reports: the next mainline stable release, when prominent distributors pick
184 respond to these reports is a matter of basic pride in your work. If that
|
| /linux/drivers/usb/serial/ |
| H A 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
|
| H A 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/tools/testing/selftests/mm/ |
| H A D | ksft_kmemleak_confirm.sh | 7 # kmemleak only reports an object once it has stayed unreferenced for
8 # min_unref_scans consecutive scans. A threshold of 1 reports on the first
19 # - at min_unref_scans=1 one scan after priming reports the orphans,
21 # enough, the second reports,
107 # 1) min_unref_scans=1: one scan after priming reports the orphans. This
118 # gated), the second reports. The gated-scan-zero check is the core
|
| /linux/arch/loongarch/ |
| H A D | Kconfig.debug | 13 traces. It scans the stack and reports every kernel text address it
14 finds. Some of the addresses it reports may be incorrect.
26 Some of the addresses it reports may be incorrect (but better than the
|
| /linux/mm/kmsan/ |
| H A D | kmsan_test.c | 4 * For each test case checks the presence (or absence) of generated reports.
5 * Relies on 'console' tracepoint to capture reports as they appear in the
184 kunit_info(test, "initialized kmalloc test (no reports)\n"); in test_init_kmalloc()
197 kunit_info(test, "initialized kzalloc test (no reports)\n"); in test_init_kzalloc()
220 kunit_info(test, "initialized stack variable (no reports)\n"); in test_init_stack_var()
295 * Test case: ensure kmsan_check_memory() reports an error when checking
323 kunit_info(test, "pages initialized via vmap (no reports)\n"); in test_init_kmsan_vmap_vunmap()
353 kunit_info(test, "vmalloc buffer can be initialized (no reports)\n"); in test_init_vmalloc()
497 "memcpy()ing aligned initialized src to aligned dst (no reports)\n"); in test_init_memcpy()
526 * aligned 4-byte values. This test case checks that KMSAN correctly reports an
[all …]
|
| /linux/tools/testing/selftests/hid/tests/ |
| H A D | base.py | 198 def debug_reports(cls, reports, uhdev=None, events=None): argument
199 data = [" ".join([f"{v:02x}" for v in r]) for r in reports]
204 for r in reports
216 reports = data
218 if len(reports) == 1:
221 print(f"sending {len(reports)} reports:")
222 for report in reports:
|
| /linux/Documentation/userspace-api/media/rc/ |
| H A 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/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3588-jaguar-pre-ict-tester.dtso | 108 * soldering issue on GPIO3_B2 reports HIGH but proper
109 * soldering reports LOW.
125 * on GPIO3_C6 or VCC_1V8_S0_1 reports LOW but proper
126 * soldering reports HIGH.
|
| /linux/drivers/block/ |
| H A D | ps3vram.c | 77 void __iomem *reports; member
101 static u32 __iomem *ps3vram_get_notifier(void __iomem *reports, int notifier) in ps3vram_get_notifier() argument
103 return reports + DMA_NOTIFIER_OFFSET_BASE + in ps3vram_get_notifier()
110 u32 __iomem *notify = ps3vram_get_notifier(priv->reports, NOTIFIER); in ps3vram_notifier_reset()
121 u32 __iomem *notify = ps3vram_get_notifier(priv->reports, NOTIFIER); in ps3vram_notifier_wait()
700 priv->reports = ioremap(reports_lpar, reports_size); in ps3vram_probe()
701 if (!priv->reports) { in ps3vram_probe()
702 dev_err(&dev->core, "ioremap REPORTS failed\n"); in ps3vram_probe()
762 iounmap(priv->reports); in ps3vram_probe()
791 iounmap(priv->reports); in ps3vram_remove()
|
| /linux/tools/testing/selftests/net/rds/ |
| H A D | run.sh | |
| /linux/Documentation/trace/ |
| H A 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/drivers/gpu/drm/i915/display/ |
| H A D | intel_tv_regs.h | 56 /* Read-only state that reports all features enabled */
58 /* Read-only state that reports that Macrovision is disabled in hardware*/
60 /* Read-only state that reports that TV-out is disabled in hardware. */
85 * Reports that DAC state change logic has reported change (RO).
91 /* Reports that DAC A voltage is above the detect threshold */
93 /* Reports that DAC B voltage is above the detect threshold */
95 /* Reports that DAC C voltage is above the detect threshold */
|
| /linux/Documentation/misc-devices/ |
| H A 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/Documentation/devicetree/bindings/hwmon/ |
| H A D | amd,sbrmi.yaml | 16 interface that reports AMD SoC's Power (normalized Power) using,
19 reports power in microwatts.
|
| /linux/Documentation/admin-guide/ |
| H A D | ufs.rst | 64 Bug Reports
68 to dushistov@mail.ru (do not send partition tables bug reports).
|