| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | monitoring.md | 1 # Regulator Monitoring
6 monitoring:
8 - [Sensor monitoring](sensor_monitoring.md)
10 - [Phase fault monitoring](phase_fault_monitoring.md)
13 Monitoring is optional and is defined in the
16 ## How monitoring is enabled
18 Regulator monitoring is enabled during the system boot after regulators are
27 `phosphor-regulators` will start performing the monitoring defined in the JSON
28 config file. Monitoring is done periodically based on a timer.
30 ## How monitoring is disabled
[all …]
|
| H A D | sensor_monitoring.md | 1 # Sensor Monitoring
9 When [regulator monitoring](monitoring.md) is enabled, the `phosphor-regulators`
15 ## How sensor monitoring is defined
17 Sensor monitoring is defined for a voltage regulator using the
38 values are read during monitoring. This can occur in the following cases:
46 When regulator monitoring is disabled, the following changes will be made to all
62 - Sensor monitoring will continue with the next rail or voltage regulator.
63 - The sensors for this rail will be read again during the next monitoring cycle.
|
| H A D | README.md | 28 C++ objects. These objects implement the regulator configuration and monitoring
40 ## Monitoring voltage regulators
42 `phosphor-regulators` supports two types of regulator monitoring:
44 - Sensor monitoring
46 - Phase fault monitoring
49 See [Regulator Monitoring](monitoring.md) for more information.
57 monitoring.
|
| H A D | multiple_chassis.md | 52 ### Monitoring subsection
54 In a single chassis system, regulator monitoring is always performed on the
57 In a multiple chassis system, regulator monitoring will only be performed on
61 See [Regulator Monitoring](monitoring.md) for more information.
|
| H A D | phase_fault_monitoring.md | 1 # Phase Fault Monitoring
12 When [regulator monitoring](monitoring.md) is enabled, the `phosphor-regulators`
39 next monitoring cycle.
|
| /openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-supplies-monitoring/ |
| H A D | power-supplies-monitoring.bb | 2 SUMMARY = "Power Supplies monitoring for HPE RL300 Gen11"
4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se…
5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage…
11 IMAGE_INSTALL += "power-supplies-monitoring "
21 …install -m 0644 ${UNPACKDIR}/psu2-monitoring.service ${D}${sysconfdir}/system/psu2-monitoring.serv…
22 …install -m 0644 ${UNPACKDIR}/psu1-monitoring.service ${D}${sysconfdir}/system/psu1-monitoring.serv…
|
| /openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-supplies-monitoring/ |
| H A D | power-supplies-monitoring.bb | 2 SUMMARY = "Power Supplies monitoring for HPE RL300 Gen11"
4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se…
5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage…
11 IMAGE_INSTALL += "power-supplies-monitoring "
21 …install -m 0644 ${UNPACKDIR}/psu2-monitoring.service ${D}${sysconfdir}/system/psu2-monitoring.serv…
22 …install -m 0644 ${UNPACKDIR}/psu1-monitoring.service ${D}${sysconfdir}/system/psu1-monitoring.serv…
|
| /openbmc/openbmc/meta-hpe/meta-dl385-g11/recipes-hpe/power-supplies-monitoring/ |
| H A D | power-supplies-monitoring.bb | 2 SUMMARY = "Power Supplies monitoring for HPE RL300 Gen11"
4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se…
5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage…
11 IMAGE_INSTALL += "power-supplies-monitoring "
21 …install -m 0644 ${UNPACKDIR}/psu2-monitoring.service ${D}${sysconfdir}/system/psu2-monitoring.serv…
22 …install -m 0644 ${UNPACKDIR}/psu1-monitoring.service ${D}${sysconfdir}/system/psu1-monitoring.serv…
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/libpfm/ |
| H A D | libpfm4_4.13.0.bb | 1 SUMMARY = "Monitoring tools exploiting the performance monitoring events"
3 monitoring tools exploiting the performance monitoring events such as those \
4 provided by the Performance Monitoring Unit (PMU) of modern processors."
|
| /openbmc/phosphor-fan-presence/ |
| H A D | README.md | 40 - [Fan Monitoring](#fan-monitoring)
45 - [Sensor Monitoring](#sensor-monitoring)
93 - [Fan Monitoring](#fan-monitoring)
96 - [Sensor Monitoring](#sensor-monitoring) - Only supports JSON
160 ### Fan Monitoring
169 Another feature that can be configured is the ability to cancel the monitoring
203 ### Sensor Monitoring
210 monitoring data
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | manager.hpp | 74 * Sets whether regulator monitoring is enabled.
76 * When monitoring is enabled:
80 * Regulator monitoring should be enabled when the system is being powered
84 * Regulator monitoring should be disabled when the system is being powered
88 * Regulator monitoring can also be temporarily disabled and then re-enabled
91 * Monitoring should be disabled for only short periods of time; other
94 * @param enable true if monitoring should be enabled, false if it should be
113 * Sensor monitoring timer expired callback function.
217 * Event timer used to initiate sensor monitoring.
222 * Indicates whether regulator monitoring is enabled.
|
| H A D | rail.hpp | 58 * @param sensorMonitoring sensor monitoring for this rail, if any
118 * Sensor monitoring is optional. If sensor monitoring is defined for this
132 * Returns the sensor monitoring for this rail, if any.
135 * sensor monitoring is defined for this rail.
155 * Sensor monitoring for this rail, if any. Set to nullptr if no sensor
156 * monitoring is defined for this rail.
|
| H A D | sensors.hpp | 144 * Reading all the sensors once is called a monitoring cycle. The application
146 * each rail. During a monitoring cycle, the following sensor service methods
148 * - startCycle() // At the start of a sensor monitoring cycle
152 * - endCycle() // At the end of a sensor monitoring cycle
182 * Notify the sensors service that the current sensor monitoring cycle has
188 * Notify the sensors service that sensor monitoring has ended for the
215 * Notify the sensors service that a sensor monitoring cycle is starting.
220 * Notify the sensors service that sensor monitoring is starting for the
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | sensor_monitoring_tests.cpp | 68 * @param monitoring SensorMonitoring object to move into object hierarchy
75 createParentObjects(std::unique_ptr<SensorMonitoring> monitoring) in createParentObjects() argument
80 "vdd", std::move(configuration), std::move(monitoring)); in createParentObjects()
143 SensorMonitoring* monitoring = new SensorMonitoring(std::move(actions)); in TEST() local
147 createParentObjects(std::unique_ptr<SensorMonitoring>{monitoring}); in TEST()
183 monitoring->execute(services, *system, *chassis, *device, *rail); in TEST()
188 monitoring->clearErrorHistory(); in TEST()
198 monitoring->execute(services, *system, *chassis, *device, *rail); in TEST()
219 SensorMonitoring* monitoring = new SensorMonitoring(std::move(actions)); in TEST() local
223 createParentObjects(std::unique_ptr<SensorMonitoring>{monitoring}); in TEST()
[all …]
|
| /openbmc/openpower-hw-diags/attn/ |
| H A D | attn_monitor.cpp | 58 scheduleGPIOEvent(); // continue monitoring gpio in handleGPIOEvent()
61 /** @brief Request a GPIO line for monitoring attention events */
79 // Register file descriptor for monitoring in requestGPIOEvent()
82 // Start monitoring in requestGPIOEvent()
|
| /openbmc/phosphor-gpio-monitor/ |
| H A D | README.md | 1 # GPIO Monitoring
7 This daemon accepts a command line parameter for monitoring single gpio line and
9 monitoring single GPIO line, for multiple lines, user has to run this daemon
21 monitoring in single instance of phosphor-multi-gpio-monitor running. It is very
49 will be monitored continuously. If not defined then monitoring of this gpio
89 monitoring in single instance of phosphor-multi-gpio-presence running. It is
|
| /openbmc/openbmc-test-automation/redfish/extended/ |
| H A D | test_escale_base.robot | 36 Escale Base Test Inactive Monitoring
37 [Documentation] Run base power tests with DCMI power monitoring off.
44 Escale Base Test Active Monitoring
45 [Documentation] Run base power tests with DCMI power monitoring on.
85 [Documentation] Activate power monitoring via REST then check via IPMI.
94 [Documentation] Deactivate power monitoring via REST and check via IPMI.
|
| /openbmc/qemu/include/qemu/ |
| H A D | filemonitor.h | 63 * Create a handle for a file monitoring object.
68 * If the platform does not support file monitoring, an
69 * error will be reported. Likewise if file monitoring
75 * Returns: the new monitoring object, or NULL on error
118 * Removes the file monitoring watch @id, associated
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Chassis/ |
| H A D | Intrusion.interface.yaml | 46 - name: monitoring
48 One chassis intrusion sensor needs to implement the 'monitoring'
50 monitoring the security state against intrusion events.
|
| /openbmc/openpower-occ-control/ |
| H A D | occ_device.hpp | 131 /** @brief stops monitoring for errors */
184 /** Abstraction of error monitoring */
187 /** Abstraction of SBE timeout monitoring */
190 /** SBE FFDC monitoring */
193 /** Abstraction of OCC presence monitoring */
226 /** @brief callback for OCC error monitoring
232 /** @brief callback for OCC presence monitoring
239 /** @brief callback for SBE timeout monitoring
|
| /openbmc/phosphor-power/ |
| H A D | README.md | 5 This repository contains applications for configuring and monitoring devices
16 power supply monitoring application.
23 - power-sequencer: Original power sequencer monitoring application.
24 - power-supply: Original power supply monitoring application.
|
| /openbmc/openbmc/poky/meta/recipes-extended/mdadm/files/ |
| H A D | mdadm.init | 11 # Short-Description: MD monitoring daemon
39 log_daemon_msg "Starting MD monitoring service" "mdadm --monitor"
50 log_daemon_msg "Stopping MD monitoring service" "mdadm --monitor"
|
| /openbmc/docs/designs/ |
| H A D | hw-fault-monitor.md | 16 available externally via Redfish for data center monitoring and management
28 external data center monitoring software.
85 center monitoring software.
103 the crash dump so that it could be post-processed by data center monitoring
119 center monitoring tools would use the logs to determine whether memory should
142 external data center monitoring software) will be a new Redfish LogService
165 external data center monitoring software of new fault information being
182 data center monitoring tools) are running software that is newer or older than
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/hddtemp/hddtemp/ |
| H A D | init | 19 # Short-Description: disk temperature monitoring daemon
20 # Description: hddtemp is a disk temperature monitoring daemon
26 DESC="disk temperature monitoring daemon"
71 log_progress_msg "no disks with monitoring capability were found."
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/wavemon/ |
| H A D | wavemon_0.9.6.bb | 1 SUMMARY = "wavemon is a wireless device monitoring application"
3 DESCRIPTION = "wavemon is a wireless device monitoring application that \
|