| /openbmc/linux/drivers/hid/ |
| H A D | hid-uclogic-rdesc.h | 112 /* Report ID for v1 pen reports */
115 /* Fixed report descriptor template for (tweaked) v1 pen reports */
119 /* Report ID for v2 pen reports */
122 /* Fixed report descriptor template for (tweaked) v2 pen reports */
126 /* Report ID for tweaked v1 frame reports */
129 /* Fixed report descriptor for (tweaked) v1 frame reports */
133 /* Report ID for tweaked v2 frame button reports */
136 /* Fixed report descriptor for (tweaked) v2 frame button reports */
140 /* Report ID for tweaked v2 frame touch ring/strip reports */
143 /* Fixed report descriptor for (tweaked) v2 frame touch ring reports */
[all …]
|
| H A D | hid-uclogic-params.h | 28 /* Normal reports: zero - out of proximity, one - in proximity */
30 /* Inverted reports: zero - in proximity, one - out of proximity */
32 /* No reports */
88 /* Report ID, if reports should be tweaked, zero if not */
95 * True, if reports include fragmented high resolution coords, with
101 * True if the pen reports tilt in bytes at offset 10 (X) and 11 (Y),
128 * Report ID, if reports should be tweaked, zero if not.
157 * The value to anchor the reversed touch ring/strip reports at.
158 * I.e. one, if the reports should be flipped without offset.
173 * Only valid if "id" is not zero. A bitmap dial sends reports with a
[all …]
|
| H A 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()
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-ccp | 6 The /sys/bus/pci/devices/<BDF>/fused_part file reports
16 The /sys/bus/pci/devices/<BDF>/debug_lock_on reports
27 The /sys/bus/pci/devices/<BDF>/tsme_status file reports
38 The /sys/bus/pci/devices/<BDF>/anti_rollback_status file reports
49 The /sys/bus/pci/devices/<BDF>/rpmc_production_enabled file reports
60 The /sys/bus/pci/devices/<BDF>/rpmc_spirom_available file reports
72 The /sys/bus/pci/devices/<BDF>/hsp_tpm_available file reports
83 The /sys/bus/pci/devices/<BDF>/rom_armor_enforced file reports
95 file reports the firmware version of the AMD AGESA
104 file reports the firmware version of the AMD Trusted
|
| H A 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 …]
|
| 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…
|
| /openbmc/linux/Documentation/hid/ |
| 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 …]
|
| 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 | 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)
|
| H A D | hidintro.rst | 37 exactly what *HID reports* may be sent between the device and the host
38 and the meaning of each individual bit in those reports. For example,
43 without any extra meta information. Note that HID reports may be sent
44 from the device ("Input Reports", i.e. input events), to the device
45 ("Output Reports" to e.g. change LEDs) or used for device configuration
46 ("Feature reports"). A device may support one or more HID reports.
109 to record and replay the raw HID reports and to debug
234 2, releases button 1, and finally releases button 2, the reports are::
249 Output, Input and Feature Reports
252 HID devices can have Input Reports, like in the mouse example, Output
[all …]
|
| /openbmc/linux/drivers/hid/usbhid/ |
| H A 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 …]
|
| /openbmc/telemetry/src/ |
| H A D | report_manager.cpp | 25 reports.reserve(maxReports); in ReportManager()
94 reports.erase( in removeReport()
95 std::remove_if(reports.begin(), reports.end(), in removeReport()
97 reports.end()); in removeReport()
108 if (reports.size() >= maxReports) in verifyAddReport()
161 reports, [](const auto& report) { return report->getId(); }); in addReport()
169 reports.emplace_back( in addReport()
173 return *reports.back(); in addReport()
|
| /openbmc/openbmc-test-automation/redfish/telemetry_service/ |
| H A D | test_telemetry_report.robot | 10 Test Setup Delete All Telemetry Reports
48 # Create maximum number of reports.
58 # Now delete the reports created.
59 Delete All Telemetry Reports
120 Delete All Telemetry Reports
195 Delete All Telemetry Reports
196 [Documentation] Delete all existing telemetry reports.
|
| /openbmc/telemetry/tests/src/ |
| H A D | test_trigger.cpp | 163 getProperty<std::vector<object_path>>(sut->getPath(), "Reports"), in TEST_F()
164 Eq(triggerParams.reports())); in TEST_F()
201 EXPECT_THAT(setProperty(sut->getPath(), "Reports", newNames), in TEST_F()
204 getProperty<std::vector<object_path>>(sut->getPath(), "Reports"), in TEST_F()
219 EXPECT_THAT(setProperty(sut->getPath(), "Reports", newPropertyVal), in TEST_F()
225 const std::vector<object_path> newPropertyVal = triggerParams.reports(); in TEST_F()
232 EXPECT_THAT(setProperty(sut->getPath(), "Reports", newPropertyVal), in TEST_F()
246 EXPECT_THAT(setProperty(sut->getPath(), "Reports", newPropertyVal), in TEST_F()
254 object_path("/xyz/openbmc_project/Telemetry/Reports/P1/P2/MyReport")}; in TEST_F()
258 EXPECT_THAT(setProperty(sut->getPath(), "Reports", newPropertyVal), in TEST_F()
[all …]
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/linux/tools/testing/selftests/hid/tests/ |
| H A D | base.py | 172 def debug_reports(cls, reports, uhdev=None, events=None): argument
173 data = [" ".join([f"{v:02x}" for v in r]) for r in reports]
178 for r in reports
190 reports = data
192 if len(reports) == 1:
195 print(f"sending {len(reports)} reports:")
196 for report in reports:
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/ |
| H A D | ReportManager.interface.yaml | 2 Implement to provide reports management. Contain information about report
10 /xyz/openbmc_project/Telemetry/Reports/{properties[Id]} where
63 /xyz/openbmc_project/Telemetry/Reports/{parameters[Id]}.
69 Contains the max number of metric reports supported by the Telemetry.
|
| /openbmc/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
173 kunit_info(test, "initialized kmalloc test (no reports)\n"); in test_init_kmalloc()
186 kunit_info(test, "initialized kzalloc test (no reports)\n"); in test_init_kzalloc()
209 kunit_info(test, "initialized stack variable (no reports)\n"); in test_init_stack_var()
284 * Test case: ensure kmsan_check_memory() reports an error when checking
312 kunit_info(test, "pages initialized via vmap (no reports)\n"); in test_init_kmsan_vmap_vunmap()
342 kunit_info(test, "vmalloc buffer can be initialized (no reports)\n"); in test_init_vmalloc()
435 "memcpy()ing aligned initialized src to aligned dst (no reports)\n"); in test_init_memcpy()
465 * aligned 4-byte values. This test case checks that KMSAN correctly reports an
[all …]
|
| /openbmc/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.
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | kasan.rst | 93 To include alloc and free stack traces of affected slab objects into reports,
105 effectively disables ``panic_on_warn`` for KASAN reports.
139 only reports tag faults during these checks.
163 Error reports
272 Generic KASAN also reports up to two auxiliary call stack traces. These stack
341 dedicated ``brk`` handler is used to print bug reports.
375 Hardware Tag-Based KASAN only reports the first found bug. After that, MTE tag
451 Normally, KASAN detects and reports such accesses, but in some cases (e.g.,
476 For software KASAN modes, to disable KASAN reports in a part of the kernel code
479 disables the reports for indirect accesses that happen through function calls.
[all …]
|