/linux-6.3-rc2/Documentation/ABI/testing/ |
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
|
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
|
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
|
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 …]
|
A D | sysfs-platform-intel-ifs | 23 Description: Additional information regarding the last test. The details file reports 32 is loaded reports "none".
|
A D | sysfs-class-rapidio | 19 (RO) reports RapidIO common transport system size: 32 (RO) reports RapidIO destination ID assigned to the given
|
/linux-6.3-rc2/drivers/hid/usbhid/ |
A D | hid-pidff.c | 147 struct hid_report *reports[sizeof(pidff_reports)]; member 316 hid_hw_request(pidff->hid, pidff->reports[PID_SET_EFFECT], in pidff_set_effect_report() 431 hid_hw_request(pidff->hid, pidff->reports[PID_SET_RAMP], in pidff_set_ramp_force_report() 826 pidff->reports[ret] = report; in pidff_find_reports() 842 if (ret != -1 && !pidff->reports[ret]) { in pidff_find_reports() 846 pidff->reports[ret] = report; in pidff_find_reports() 859 if (!pidff->reports[i]) { in pidff_reports_ok() 928 pidff_find_special_field(pidff->reports[PID_SET_EFFECT], in pidff_find_special_fields() 1057 pidff->reports[report], \ 1178 hid_hw_request(hid, pidff->reports[PID_POOL], in pidff_reset() [all …]
|
/linux-6.3-rc2/Documentation/hid/ |
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 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 135 INPUT and OUTPUT reports can be sent as pure data reports on the intr channel. 136 For INPUT reports this is the usual operational mode. But for OUTPUT reports, 142 channel provides synchronous GET/SET_REPORT requests. Plain reports are only [all …]
|
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 129 device. For devices which do not use numbered reports, the report data will [all …]
|
/linux-6.3-rc2/arch/loongarch/ |
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-6.3-rc2/Documentation/userspace-api/media/rc/ |
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-6.3-rc2/drivers/block/ |
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() 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-6.3-rc2/Documentation/misc-devices/ |
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-6.3-rc2/Documentation/devicetree/bindings/hwmon/ |
A D | amd,sbrmi.yaml | 16 interface that reports AMD SoC's Power (normalized Power) using, 19 reports power in microwatts.
|
/linux-6.3-rc2/drivers/hid/intel-ish-hid/ |
A D | ishtp-hid-client.c | 76 char *reports; in process_recv() local 283 reports = (char *)reports_list->reports; in process_recv() 286 recv_msg = (struct hostif_msg *)(reports + in process_recv() 288 report_len = *(uint16_t *)reports; in process_recv() 289 payload = reports + sizeof(uint16_t) + in process_recv() 307 reports += sizeof(uint16_t) + report_len; in process_recv()
|
/linux-6.3-rc2/Documentation/hwmon/ |
A 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-6.3-rc2/Documentation/networking/devlink/ |
A D | mlxsw.rst | 43 The ``mlxsw`` driver reports the following versions 64 The ``mlxsw`` driver reports the following versions for line card auxiliary device
|
A D | devlink-health.rst | 21 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``.
|
A D | hns3.rst | 15 The ``hns3`` driver reports the following versions
|
/linux-6.3-rc2/Documentation/scsi/ |
A D | NinjaSCSI.rst | 29 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-6.3-rc2/Documentation/userspace-api/media/v4l/ |
A 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`` 197 If :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM`` 225 :ref:`VIDIOC_ENUM_FMT` reports ``V4L2_FMT_FLAG_CONTINUOUS_BYTESTREAM``
|
/linux-6.3-rc2/Documentation/ia64/ |
A 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-6.3-rc2/Documentation/dev-tools/ |
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. 136 only reports tag faults during these checks. 160 Error reports 269 Generic KASAN also reports up to two auxiliary call stack traces. These stack 338 dedicated ``brk`` handler is used to print bug reports. 372 Hardware Tag-Based KASAN only reports the first found bug. After that, MTE tag 448 Normally, KASAN detects and reports such accesses, but in some cases (e.g., 476 disables the reports for indirect accesses that happen through function calls. 496 kernel log for KASAN reports. [all …]
|
/linux-6.3-rc2/Documentation/networking/ |
A 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
|
/linux-6.3-rc2/lib/ |
A D | Kconfig.kcsan | 43 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.
|