Home
last modified time | relevance | path

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

12345678910>>...18

/openbmc/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 …]
/openbmc/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 …]
/openbmc/telemetry/src/
H A Dreport_manager.cpp25 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/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 …]
/openbmc/openbmc/poky/bitbake/lib/bb/tests/
H A Dcolor.py26 def reports(self): member in ProgressWatcher
72 self.assertEqual(self._progress_watcher.reports(), expected)
85 self.assertListEqual(self._progress_watcher.reports(), expected)
95 self.assertListEqual(self._progress_watcher.reports(), expected)
/openbmc/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
/openbmc/linux/tools/testing/selftests/hid/tests/
H A Dbase.py172 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:
196 for report in reports:
/openbmc/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.
/openbmc/docs/designs/
H A Dtelemetry.md44 - Metric Reports - contains actual metric reports containing telemetry data
266 metric reports. All operations on metric reports shall be done in the Telemetry
297 reports supported simultaneously.
308 periodically updated reports).
529 reports over D-Bus for the Telemetry Service. Each D-Bus sensor is mapped to
670 only. All reports was created with
672 workload. In the configuration with 50 reports and 50 sensors it is about 200
673 new readings per second, generating 200 reading reports per second. The table
681 | Idle (0 reports, 0 sensors) | 5188 B | 1% | 0% |
683 | 2 reports, 1 sensor | 5188 B | 1% | 1% |
[all …]
/openbmc/qemu/tests/tsan/
H A Dsuppressions.tsan5 # TSan reports a double lock on RECURSIVE mutexes.
9 # TSan reports a race between pthread_mutex_init() and
/openbmc/bmcweb/redfish-core/lib/
H A Dtrigger.hpp227 std::vector<sdbusplus::message::object_path> reports; member
541 ctx.reports.reserve(metricReportDefinitions.size()); in parseLinks()
552 ctx.reports.emplace_back(*reportPath); in parseLinks()
804 nlohmann::json reports = nlohmann::json::array(); in getMetricReportDefinitions() local
822 reports.emplace_back(std::move(report)); in getMetricReportDefinitions()
825 return {std::move(reports)}; in getMetricReportDefinitions()
847 const std::vector<sdbusplus::message::object_path>* reports = nullptr; in fillTrigger() local
855 discrete, "Sensors", sensors, "Reports", reports, "TriggerActions", in fillTrigger()
877 if (reports != nullptr) in fillTrigger()
880 getMetricReportDefinitions(*reports); in fillTrigger()
[all …]
/openbmc/qemu/tests/migration/guestperf/
H A Dshell.py274 if len(args.reports) == 0:
285 reports = []
286 for report in args.reports:
287 reports.append(Report.from_json_file(report))
289 plot = Plot(reports,
/openbmc/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()
/openbmc/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
/openbmc/linux/drivers/hid/intel-ish-hid/
H A Dishtp-hid-client.c76 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()
/openbmc/telemetry/tests/src/params/
H A Dtrigger_params.hpp80 const std::vector<object_path>& reports() const in reports() function in TriggerParams
85 TriggerParams& reports(std::vector<object_path> val) in reports() function in TriggerParams
/openbmc/qemu/docs/system/arm/
H A Dsbsa.rst13 specification defines how the firmware reports that to any operating system.
36 ``sbsa-ref`` is a static system that reports a very minimal devicetree to the
58 The devicetree reports:
/openbmc/linux/Documentation/hwmon/
H A Dltc2978.rst323 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.
/openbmc/linux/Documentation/arch/ia64/
H A Daliasing.rst162 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::
/openbmc/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``.
/openbmc/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.

12345678910>>...18