Home
last modified time | relevance | path

Searched full:monitored (Results 1 – 25 of 321) sorted by relevance

12345678910>>...13

/openbmc/linux/include/dt-bindings/clock/
H A Dtegra234-clock.h150 /** @brief Monitored branch of EQOS_RX clock */
434 /** @brief Monitored branch of PEX0_C0_CORE clock */
436 /** @brief Monitored branch of PEX0_C1_CORE clock */
438 /** @brief Monitored branch of PEX0_C2_CORE clock */
440 /** @brief Monitored branch of PEX0_C3_CORE clock */
442 /** @brief Monitored branch of PEX0_C4_CORE clock */
444 /** @brief Monitored branch of PEX1_C5_CORE clock */
446 /** @brief Monitored branch of PEX1_C6_CORE clock */
462 /** @brief Monitored branch of PEX2_C7_CORE clock */
464 /** @brief Monitored branch of PEX2_C8_CORE clock */
[all …]
/openbmc/phosphor-fan-presence/monitor/example/
H A Dconfig.json18 "In addition, this fan is not monitored for the first 30 seconds after",
45 "that is only monitored with the `WaterCooled` property is false. The",
46 "sensor is monitored using a 'count' method where a counter is",
58 "In addition, this fan is not monitored for the first 30 seconds after",
107 "In addition, this fan is not monitored for the first 30 seconds after",
138 "in the group is cancelled, only to resume being monitored when any",
159 "across all the fans being monitored. The system is immediately hard",
/openbmc/linux/Documentation/devicetree/bindings/power/supply/
H A Drichtek,rt5033-charger.yaml20 monitored-battery:
23 Phandle to the monitored battery according to battery.yaml. The battery
55 - monitored-battery
63 monitored-battery = <&battery>;
H A Dstericsson,ab8500-chargalg.yaml20 monitored-battery:
30 - monitored-battery
39 monitored-battery = <&ab8500_battery>;
H A Dbq2515x.yaml56 monitored-battery:
58 description: phandle to the battery node being monitored
63 - monitored-battery
83 monitored-battery = <&bat>;
H A Dbq25980.yaml76 monitored-battery:
78 description: phandle to the battery node being monitored
83 - monitored-battery
110 monitored-battery = <&bat>;
H A Dingenic,battery.yaml31 monitored-battery:
42 - monitored-battery
60 monitored-battery = <&simple_battery>;
H A Dbq256xx.yaml61 monitored-battery:
63 description: phandle to the battery node being monitored
78 - monitored-battery
117 monitored-battery = <&bat>;
H A Dstericsson,ab8500-fg.yaml20 monitored-battery:
53 - monitored-battery
67 monitored-battery = <&battery>;
H A Dadc-battery.yaml48 monitored-battery: true
54 - monitored-battery
69 monitored-battery = <&battery>;
H A Dstericsson,ab8500-btemp.yaml20 monitored-battery:
49 - monitored-battery
63 monitored-battery = <&battery>;
H A Dqcom,pmi8998-charger.yaml41 monitored-battery:
52 - monitored-battery
80 monitored-battery = <&battery>;
H A Dstericsson,ab8500-charger.yaml20 monitored-battery:
73 - monitored-battery
88 monitored-battery = <&battery>;
H A Dcw2015_battery.yaml14 phandle in monitored-battery. If specified the driver uses the
46 monitored-battery:
77 monitored-battery = <&bat>;
H A Dsc27xx-fg.yaml50 monitored-battery: true
61 - monitored-battery
95 monitored-battery = <&bat>;
H A Dpower-supply.yaml21 monitored-battery:
24 The battery (with "simple-battery" compatible) being monitored by this
H A Dsc2731-charger.yaml26 monitored-battery:
50 monitored-battery = <&bat>;
/openbmc/linux/Documentation/admin-guide/
H A Dperf-security.rst11 monitored processes. The data leakage is possible both in scenarios of
32 execution metrics for various monitored parts of the system (e.g.,
98 performance analysis of monitored processes or a system. For example,
234 monitored *scope* is maximized and no perf_events specific limits
241 user or in kernel space can be monitored and captured for later
250 monitored and captured for later analysis. Per-user per-cpu
257 monitored and captured for later analysis. Per-user per-cpu
276 file descriptors that is not less than the number of monitored events
277 multiplied by the number of monitored CPUs.
288 specifically for capturing monitored performance events and related data.
/openbmc/bmcweb/redfish-core/include/generated/enums/
H A Dcontrol.hpp42 Monitored,
77 {ImplementationType::Monitored, "Monitored"},
41 Monitored, global() enumerator
/openbmc/qemu/hw/sensor/
H A Dmax34451.c67 * @page: Each page corresponds to a device monitored by the Max 34451
70 | 0 | Power supply monitored by RS0, controlled by PSEN0, and |
73 | 1 | Power supply monitored by RS1, controlled by PSEN1, and |
76 | 2 | Power supply monitored by RS2, controlled by PSEN2, and |
79 | 3 | Power supply monitored by RS3, controlled by PSEN3, and |
82 | 4 | Power supply monitored by RS4, controlled by PSEN4, and |
85 | 5 | Power supply monitored by RS5, controlled by PSEN5, and |
88 | 6 | Power supply monitored by RS6, controlled by PSEN6, and |
91 | 7 | Power supply monitored by RS7, controlled by PSEN7, and |
94 | 8 | Power supply monitored by RS8, controlled by PSEN8, and |
[all …]
/openbmc/phosphor-gpio-monitor/
H A DREADME.md28 which is required to be monitored. This file can be replaced with a platform
38 5. EventMon: Event of gpio to be monitored. This can be "FALLING", "RISING" OR
47 will be monitored continously. If not defined then monitoring of this gpio
94 which is required to be monitored. This file can be replaced with a platform
/openbmc/phosphor-state-manager/
H A Dsystemd_target_signal.cpp84 // Check if its result matches any of our monitored errors in processError()
90 "Monitored systemd unit has hit an error, unit:{UNIT}, result:{RESULT}", in processError()
93 // Generate a BMC dump when a monitored target fails in processError()
106 "Monitored systemd service has hit an error, unit:{UNIT}, result:{RESULT}", in processError()
135 // If this is a monitored error then log it in systemdUnitChange()
/openbmc/linux/drivers/powercap/
H A DKconfig31 and monitored on modern Intel processors (Sandy Bridge and later).
46 and monitored.
71 and monitored against the SCMI Powercap domains advertised as
/openbmc/linux/drivers/usb/mon/
H A Dmon_main.c47 m1->u_bus->monitored = 1; in mon_reader_add()
50 mbus->u_bus->monitored = 1; in mon_reader_add()
177 ubus->monitored = 0; in mon_stop()
185 ubus->monitored = 0; in mon_stop()
202 ubus->monitored = 1; in mon_bus_add()
257 if (ubus->monitored) { in mon_dissolve()
258 ubus->monitored = 0; in mon_dissolve()
/openbmc/phosphor-fan-presence/monitor/
H A Djson_parser.hpp69 * @return List of sensor definition data that make up a fan being monitored
74 * @brief Get the configured fan definitions to be monitored
78 * @return List of fan definition data on the fans to be monitored

12345678910>>...13