/openbmc/linux/drivers/clk/hisilicon/ |
D | clk-hisi-phase.c |
|
/openbmc/phosphor-power/phosphor-regulators/src/ |
H A D | phase_fault_detection.hpp | 40 * Detects and logs redundant phase faults in a voltage regulator. 42 * A voltage regulator is sometimes called a "phase controller" because it 45 * A regulator may have redundant phases. If a redundant phase fails, the 47 * phase fault error should be logged warning the user that the regulator has 50 * The technique used to detect a phase fault varies depending on the regulator 54 * Phase fault detection is executed repeatedly based on a timer. A phase fault 58 * Phase faults are detected by executing actions. 74 * @param actions Actions that detect phase faults in the regulator. 75 * @param deviceID Unique ID of the device to use when detecting phase 100 * Executes the actions that detect phase faults in the regulator. [all …]
|
H A D | phase_fault.hpp | 26 * Redundant phase fault type. 28 * A voltage regulator is sometimes called a "phase controller" because it 31 * A regulator may have redundant phases. If a redundant phase fails, the 33 * phase fault error should be logged warning the user that the regulator has 39 * N phase fault type. 47 * N+1 phase fault type. 49 * An "N+2" regulator has lost one redundant phase. The regulator is now at 60 * @param type phase fault type 81 * @param type phase fault type 82 * @return phase fault type name
|
H A D | phase_fault_detection.cpp | 40 * Number of consecutive phase faults required to log an error. This provides 59 // Execute the actions to detect phase faults in execute() 62 // Check for any N or N+1 phase faults that were detected in execute() 75 "Unable to detect phase faults in regulator " + in execute() 100 // Check if the phase fault was detected in checkForPhaseFault() 103 // Phase fault not detected; reset consecutive fault count in checkForPhaseFault() 108 // Phase fault detected; increment consecutive fault count in checkForPhaseFault() 113 toString(faultType) + " phase fault detected in regulator " + in checkForPhaseFault() 119 // Log phase fault error and update ErrorHistory in checkForPhaseFault()
|
/openbmc/phosphor-power/phosphor-regulators/docs/ |
H A D | phase_fault_monitoring.md | 1 # Phase Fault Monitoring 5 Some voltage regulators contain redundant phases. If a redundant phase fails, 7 lost, and the regulator may fail if another phase fails. 9 Voltage regulators can be monitored for redundant phase faults. If a fault is 13 application checks for redundant phase faults every 15 seconds. 15 A phase fault must be detected two consecutive times (15 seconds apart) before 19 A phase fault error will only be logged for a regulator once per system boot. 21 ## How phase fault detection is defined 23 Phase fault detection is defined for a voltage regulator using the 32 If a different type of error occurs while detecting phase faults in a regulator: [all …]
|
/openbmc/linux/drivers/clk/sunxi-ng/ |
D | ccu_phase.c |
|
/openbmc/u-boot/drivers/ddr/marvell/axp/ |
H A D | ddr3_read_leveling.c | 55 * Desc: Execute the Read leveling phase by HW 91 u32 delay, phase, pup, cs; in ddr3_read_leveling_hw() local 108 phase = (reg >> REG_PHY_PHASE_OFFS) & in ddr3_read_leveling_hw() 111 dram_info->rl_val[cs][pup][P] = phase; in ddr3_read_leveling_hw() 112 if (phase > dram_info->rl_max_phase) in ddr3_read_leveling_hw() 113 dram_info->rl_max_phase = phase; in ddr3_read_leveling_hw() 114 if (phase < dram_info->rl_min_phase) in ddr3_read_leveling_hw() 115 dram_info->rl_min_phase = phase; in ddr3_read_leveling_hw() 138 DEBUG_RL_S(", Phase: "); in ddr3_read_leveling_hw() 173 * Desc: Execute the Read leveling phase by SW [all …]
|
/openbmc/qemu/tests/tcg/multiarch/gdbstub/ |
H A D | late-attach.py | 11 phase = gdb.parse_and_eval("phase").string() 14 phase = "start" 16 if phase == "start": 19 phase = gdb.parse_and_eval("phase").string() 20 report(phase == "sigwait", "{} == \"sigwait\"".format(phase))
|
/openbmc/linux/drivers/clk/sunxi/ |
D | clk-mod0.c |
|
/openbmc/phosphor-power/phosphor-regulators/test/ |
H A D | phase_fault_detection_tests.cpp | 201 // performing phase fault detection 10 times. The lambda allows us to in TEST_F() 206 // - 3 error messages for inability to detect phase faults in TEST_F() 207 // - 2 error messages for the N phase fault in TEST_F() 208 // - 2 error messages for the N+1 phase fault in TEST_F() 213 logError("Unable to detect phase faults in regulator vdd1")) in TEST_F() 217 logError("n phase fault detected in regulator vdd1: count=1")) in TEST_F() 221 logError("n phase fault detected in regulator vdd1: count=2")) in TEST_F() 225 logError("n+1 phase fault detected in regulator vdd1: count=1")) in TEST_F() 229 logError("n+1 phase fault detected in regulator vdd1: count=2")) in TEST_F() 234 // - N phase fault error should be logged once in TEST_F() [all …]
|
/openbmc/linux/include/linux/regulator/ |
D | da9121.h |
|
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
H A D | phase_fault_detection.md | 5 Specifies how to detect and log redundant phase faults in a voltage regulator. 7 A voltage regulator is sometimes called a "phase controller" because it controls 10 A regulator may have redundant phases. If a redundant phase fails, the regulator 11 will continue to provide the desired output voltage. However, a phase fault 14 The technique used to detect a phase fault varies depending on the regulator 18 Phase fault detection is performed every 15 seconds. A phase fault must be 22 Phase faults are detected and logged by executing actions: 32 - Use the [log_phase_fault](log_phase_fault.md) action to log a phase fault 50 … array of strings | One or more comment lines describing the phase fault detection. … 63 "comments": ["Detect phase fault using I/O expander"], [all …]
|
H A D | log_phase_fault.md | 5 Logs a redundant phase fault error for a voltage regulator. This action should 12 - An "N+1" regulator has one redundant phase 14 A phase fault occurs when a phase stops functioning properly. The redundancy 17 The phase fault type indicates the level of redundancy remaining **after** the 22 | n+1 | An "N+2" regulator has lost one redundant phase. The regulator is now at redundancy level … 33 | type | yes | string | Phase fault type. Specify one of the following: "n+1", "n". |
|
/openbmc/linux/drivers/gpu/drm/tidss/ |
D | tidss_dispc_regs.h |
|
/openbmc/linux/drivers/net/wwan/iosm/ |
D | iosm_ipc_imem_ops.c |
|
D | iosm_ipc_imem.c |
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
D | uncore-power.json |
|
/openbmc/linux/Documentation/devicetree/bindings/watchdog/ |
D | realtek,otto-wdt.yaml |
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/icelakex/ |
D | uncore-power.json |
|
/openbmc/linux/tools/perf/pmu-events/arch/x86/snowridgex/ |
D | uncore-power.json |
|
/openbmc/linux/Documentation/ABI/testing/ |
D | sysfs-driver-zynqmp-fpga |
|
/openbmc/linux/drivers/staging/iio/Documentation/ |
D | sysfs-bus-iio-dds |
|
/openbmc/linux/drivers/media/i2c/ |
D | saa711x_regs.h |
|
/openbmc/qemu/docs/devel/ |
H A D | reset.rst | 109 Multi-phase mechanism 114 The resettable interface uses a multi-phase system to relieve objects and 124 1. The **enter** phase is executed when the object enters reset. It resets only 129 2. The **hold** phase is executed for entry into reset, once every object in the 130 group which is being reset has had its *enter* phase executed. At this point 133 3. The **exit** phase is executed when the object leaves the reset state. 142 The *exit* phase is executed only when the last reset operation ends. Therefore 148 the 'exit' phase and this sequencing makes sure no outstanding DMA request 164 phase of the reset; they are name ``phases.enter()``, ``phases.hold()`` and 181 /* call parent class enter phase */ [all …]
|
/openbmc/linux/drivers/hwmon/pmbus/ |
D | tps25990.c |
|