Home
last modified time | relevance | path

Searched refs:reports (Results 1 – 25 of 277) sorted by relevance

12345678910>>...12

/linux/Documentation/ABI/testing/
H A Dsysfs-driver-ccp6 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 Dsysfs-pps21 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 Dsysfs-amd-pmc4 Description: Reading this file reports the version of the firmware loaded to
11 Description: Reading this file reports the program corresponding to the SMU
H A Dsysfs-class-regulator7 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 Dconfigfs-tsm82 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
H A Dsysfs-platform-intel-ifs29 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
H A Dsysfs-class-rapidio19 (RO) reports RapidIO common transport system size:
32 (RO) reports RapidIO destination ID assigned to the given
H A Dsysfs-driver-wacom8 from this file returns 1 if tablet reports in high speed mode
101 Reading from this file reports the mode status of the
103 reports have been received from the paired device, reading
/linux/drivers/hid/usbhid/
H A Dhid-pidff.c147 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()
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()
466 hid_hw_request(pidff->hid, pidff->reports[PID_BLOCK_LOAD], in pidff_request_effect_upload()
504 hid_hw_request(pidff->hid, pidff->reports[PID_EFFECT_OPERATION], in pidff_playback_pid()
[all …]
/linux/Documentation/hid/
H A Dhid-transport.rst86 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 Dhidraw.rst6 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 Dhidintro.rst37 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
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::
271 Different reports are identified by means of different *Report ID*
300 Collections (with reports identified by Reports IDs 1 and 2,
/linux/tools/testing/selftests/hid/tests/
H A Dbase.py185 def debug_reports(cls, reports, uhdev=None, events=None): argument
186 data = [" ".join([f"{v:02x}" for v in r]) for r in reports]
191 for r in reports
203 reports = data
205 if len(reports) == 1:
209 for report in reports:
/linux/Documentation/userspace-api/media/rc/
H A Dlirc-set-wideband-receiver.rst47 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/loongarch/
H A DKconfig.debug13 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/drivers/block/
H A Dps3vram.c77 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()
702 priv->reports = ioremap(reports_lpar, reports_size); in ps3vram_probe()
703 if (!priv->reports) { in ps3vram_probe()
764 iounmap(priv->reports); in ps3vram_probe()
793 iounmap(priv->reports); in ps3vram_remove()
/linux/Documentation/misc-devices/
H A Dics932s401.rst24 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/networking/devlink/
H A Ddevlink-health.rst21 The main idea is to unify and centralize driver health reports in the
29 For each registered health reporter a driver can issue error/health reports
30 asynchronously. All health reports handling is done by ``devlink``.
H A Dmlxsw.rst43 The ``mlxsw`` driver reports the following versions
64 The ``mlxsw`` driver reports the following versions for line card auxiliary device
/linux/Documentation/scsi/
H A DNinjaSCSI.rst29 If you installed pcmcia-cs already, pcmcia reports your card as UNKNOWN
151 Please send me some reports(bug reports etc..) of this software.
/linux/lib/
H A DKconfig.kcsan43 bool "Show verbose reports with more information about system state"
46 If enabled, reports show more information about the system state that
70 various race scenarios, and verifies the reports generated to
159 Different races may still generate reports within a duration that is
161 reporting to avoid flooding the console with reports. Setting this
236 plain reads and marked writes to result in "unknown origin" reports.
/linux/Documentation/trace/
H A Dosnoise-tracer.rst22 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/Documentation/networking/
H A Dnfc.rst84 * 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
/linux/Documentation/userspace-api/media/v4l/
H A Dpixfmt-compressed.rst46 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``
/linux/net/bluetooth/hidp/
H A DKconfig8 for HID reports. HIDP is required for the Bluetooth Human

12345678910>>...12