Searched full:reports (Results 1 – 25 of 275) sorted by relevance
1234567891011
| /Documentation/ABI/testing/ |
| 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
|
| 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-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-driver-qat_ras | 5 Description: (RO) Reports the number of correctable errors detected by the device.
13 Description: (RO) Reports the number of non fatal errors detected by the device.
21 Description: (RO) Reports the number of fatal errors detected by the device.
31 The following example reports how to reset the counters::
|
| 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…
|
| 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.
|
| 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-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
|
| 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 …]
|
| D | configfs-tsm | 82 supports the concept of attestation reports for TVMs running at
102 supports the concept of attestation reports from a service
119 supports the concept of attestation reports from a service
137 supports the concept of attestation reports from a service
|
| D | sysfs-platform-intel-ifs | 29 Description: Additional information regarding the last test. The details file reports
39 is loaded reports "none". Only present for device instances where a test image
|
| D | sysfs-platform-dell-wmi-ddv | 6 Reports the Dell ePPID (electronic Piece Part Identification)
|
| /Documentation/hid/ |
| 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-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 | 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)
|
| 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 …]
|
| /Documentation/userspace-api/media/rc/ |
| 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.
|
| /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
|
| /Documentation/admin-guide/ |
| D | ufs.rst | 64 Bug Reports
68 to dushistov@mail.ru (do not send partition tables bug reports).
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | amd,sbrmi.yaml | 16 interface that reports AMD SoC's Power (normalized Power) using,
19 reports power in microwatts.
|
| /Documentation/dev-tools/ |
| D | kasan.rst | 96 To include alloc and free stack traces of affected slab objects into reports,
108 effectively disables ``panic_on_warn`` for KASAN reports.
142 only reports tag faults during these checks.
166 Error reports
275 Generic KASAN also reports up to two auxiliary call stack traces. These stack
365 dedicated ``brk`` handler is used to print bug reports.
399 Hardware Tag-Based KASAN only reports the first found bug. After that, MTE tag
475 Normally, KASAN detects and reports such accesses, but in some cases (e.g.,
500 For software KASAN modes, to disable KASAN reports in a part of the kernel code
503 disables the reports for indirect accesses that happen through function calls.
[all …]
|
| /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.
|
| /Documentation/userspace-api/media/v4l/ |
| D | pixfmt-compressed.rst | 46 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
102 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
111 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
202 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
230 :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
|
| /Documentation/networking/devlink/ |
| D | mlxsw.rst | 43 The ``mlxsw`` driver reports the following versions
64 The ``mlxsw`` driver reports the following versions for line card auxiliary device
|
| /Documentation/networking/ |
| D | nfc.rst | 84 * NFC_EVENT_DEVICE_ADDED - reports an NFC device addition
85 * NFC_EVENT_DEVICE_REMOVED - reports an NFC device removal
86 * NFC_EVENT_TARGETS_FOUND - reports START_POLL results when 1 or more targets
|
1234567891011