| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | design.md | 3 This document describes the high-level design of the `phosphor-regulators`
6 The low-level design is documented using doxygen comments in the source files.
13 The `phosphor-regulators` application is a single-threaded C++ executable. It is
17 The application is driven by a system-specific JSON configuration file. The JSON
19 C++ objects. These objects implement the regulator configuration and monitoring
24 - Manager
25 - Top level class created in `main()`.
26 - Loads the JSON configuration file.
27 - Implements the D-Bus `configure` and `monitor` methods.
28 - Contains a System object.
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/qcom/ |
| H A D | msm8994-msft-lumia-octagon.dtsi | 1 // SPDX-License-Identifier: BSD-3-Clause
12 #include <dt-bindings/gpio/gpio.h>
13 #include <dt-bindings/input/gpio-keys.h>
14 #include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
20 /delete-node/ &adsp_mem;
21 /delete-node/ &audio_mem;
22 /delete-node/ &cont_splash_mem;
23 /delete-node/ &mba_mem;
24 /delete-node/ &mpss_mem;
25 /delete-node/ &peripheral_region;
[all …]
|
| H A D | msm8994-sony-xperia-kitakami.dtsi | 1 // SPDX-License-Identifier: BSD-3-Clause
9 #include <dt-bindings/gpio/gpio.h>
10 #include <dt-bindings/input/gpio-keys.h>
18 * and requires driver-side changes (including CPR, be warned!!).
21 qcom,msm-id = <207 0x20000>, <207 0x20001>;
23 qcom,pmic-id = <0x10009 0x1000a 0x00 0x00>;
25 qcom,board-id = <8 0>;
28 /delete-node/ psci;
30 gpio-keys {
31 compatible = "gpio-keys";
[all …]
|
| H A D | msm8956-sony-xperia-loire.dtsi | 1 // SPDX-License-Identifier: BSD-3-Clause
3 * Copyright (c) 2016-2022, AngeloGioacchino Del Regno
16 qcom,msm-id = <266 0x10001>; /* MSM8956 v1.1 */
17 qcom,board-id = <8 0>;
27 stdout-path = "serial0:115200n8";
30 reserved-memory {
31 cont-splash@83000000 {
38 record-size = <0x20000>;
39 console-size = <0x40000>;
40 ftrace-size = <0x20000>;
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | stericsson,db8500-prcmu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/stericsson,db8500-prcmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ST-Ericsson DB8500 PRCMU - Power Reset and Control Management Unit
10 - Linus Walleij <linus.walleij@linaro.org>
13 The DB8500 Power Reset and Control Management Unit is an XP70 8-bit
14 microprocessor that is embedded in the always-on power domain of the
20 pattern: '^prcmu@[0-9a-f]+$'
23 description: The device is compatible both to the device-specific
[all …]
|
| H A D | rockchip,rk805.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chris Zhong <zyw@rock-chips.com>
11 - Zhang Qing <zhangqing@rock-chips.com>
20 - rockchip,rk805
28 '#clock-cells':
30 See <dt-bindings/clock/rockchip,rk808.h> for clock IDs.
34 clock-output-names:
38 gpio-controller: true
[all …]
|
| H A D | rockchip,rk808.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chris Zhong <zyw@rock-chips.com>
11 - Zhang Qing <zhangqing@rock-chips.com>
20 - rockchip,rk808
28 '#clock-cells':
30 See <dt-bindings/clock/rockchip,rk808.h> for clock IDs.
33 clock-output-names:
38 rockchip,system-power-controller:
[all …]
|
| /openbmc/docs/designs/ |
| H A D | voltage-regulator-configuration.md | 1 # Voltage Regulator Configuration
8 Created: 2019-07-13
13 voltage, over-current limit, and pgood thresholds. The configuration is often
14 dependent on the system type and rail type. Regulators have a hardware default
15 configuration that is defined by hardware engineers early in system design.
17 new application is needed to configure regulators. It should be data-driven to
18 support a variety of regulator types and to avoid hard-coded logic.
22 ### Regulator Configuration Data ("Config File")
24 Hardware engineers must specify many low-level configuration values for a
25 regulator. Some simple examples include output voltage, over-current limit, and
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | phase_fault_detection.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
35 class System;
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
46 * regulator will continue to provide the desired output voltage. However, a
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
52 * could exist in the regulator or in a related I/O expander.
56 * provides "de-glitching" to ignore transient hardware problems.
[all …]
|
| H A D | chassis.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
32 class System;
37 * A chassis within the system.
40 * the BMC. Small and mid-sized systems may contain a single chassis. In a
41 * large rack-mounted system, each drawer may correspond to a chassis.
49 // Specify which compiler-generated methods we want
62 * @param number Chassis number within the system. Chassis numbers start at
63 * 1 because chassis 0 represents the entire system.
64 * @param inventoryPath D-Bus inventory path for this chassis
66 * contain regulator devices and any related devices required
[all …]
|
| H A D | manager.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
20 #include "system.hpp"
56 * @param bus the D-Bus bus
62 * Implements the D-Bus "configure" method.
64 * Configures all the voltage regulators in the system.
66 * This method should be called when the system is being powered on. It
72 * Implements the D-Bus "monitor" method.
74 * Sets whether regulator monitoring is enabled.
77 * - regulator sensors will be read and published on D-Bus
78 * - phase fault detection will be performed
[all …]
|
| H A D | phase_fault_detection.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
26 #include "system.hpp"
41 * "de-glitching" to ignore transient hardware problems.
45 void PhaseFaultDetection::execute(Services& services, System& system, in execute() argument
46 Chassis& /*chassis*/, Device& regulator) in execute() argument
51 // the ID of the specified regulator. in execute()
53 deviceID.empty() ? regulator.getID() : deviceID; in execute()
56 ActionEnvironment environment{system.getIDMap(), effectiveDeviceID, in execute()
63 checkForPhaseFault(PhaseFaultType::n, services, regulator, environment); in execute()
64 checkForPhaseFault(PhaseFaultType::n_plus_1, services, regulator, in execute()
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-regulator | 1 What: /sys/class/regulator/.../state
6 Some regulator directories will contain a field called
7 state. This reports the regulator enable control, for
16 'enabled' means the regulator output is ON and is supplying
17 power to the system (assuming no error prevents it).
19 'disabled' means the regulator output is OFF and is not
20 supplying power to the system (unless some non-Linux
27 or microamps to determine configured regulator output levels.
30 What: /sys/class/regulator/.../status
32 Some regulator directories will contain a field called
[all …]
|
| /openbmc/linux/include/linux/regulator/ |
| H A D | machine.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * machine.h -- SoC Regulator support, machine/board driver API.
9 * Regulator Machine/Board Interface.
15 #include <linux/regulator/consumer.h>
18 struct regulator;
21 * Regulator operation constraint flags. These flags are used to enable
22 * certain regulator operations and can be OR'ed together.
24 * VOLTAGE: Regulator output voltage can be changed by software on this
26 * CURRENT: Regulator output current can be changed by software on this
28 * MODE: Regulator operating mode can be changed by software on this
[all …]
|
| H A D | driver.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * driver.h -- SoC Regulator driver support.
9 * Regulator Driver Interface.
18 #include <linux/regulator/consumer.h>
37 /* The regulator is enabled but not regulating */
62 * struct regulator_ops - regulator operations.
64 * @enable: Configure the regulator as enabled.
65 * @disable: Configure the regulator as disabled.
66 * @is_enabled: Return 1 if the regulator is enabled, 0 if not.
69 * @set_voltage: Set the voltage for the regulator within the range specified.
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | regulator.rst | 1 .. Copyright 2007-2008 Wolfson Microelectronics
8 Voltage and current regulator API
20 The intention is to allow systems to dynamically control regulator power
27 ``Documentation/power/regulator``.
30 --------
32 The regulator API uses a number of terms which may not be familiar:
34 Regulator
42 Electronic device which consumes power provided by a regulator. These
44 requiring active management of the regulator at runtime.
48 The electronic circuit supplied by a given regulator, including the
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/test/ |
| H A D | phase_fault_detection_tests.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
33 #include "system.hpp"
65 * - Regulator Device
66 * - I/O expander Device
67 * - Chassis that contains the Devices
68 * - System that contains the Chassis
76 // Create mock I2CInterface for regulator Device and save pointer
78 this->regI2CInterface = regI2CInterface.get();
80 // Create regulator Device and save pointer
81 auto regulator = std::make_unique<Device>( member in PhaseFaultDetectionTests
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | max8907.txt | 1 MAX8907 regulator
4 - compatible: "maxim,max8907"
5 - reg: I2C slave address
6 - interrupts: The interrupt output of the controller
7 - mbatt-supply: The input supply for MBATT, BBAT, SDBY, VRTC.
8 - in-v1-supply: The input supply for SD1.
9 - in-v2-supply: The input supply for SD2.
10 - in-v3-supply: The input supply for SD3.
11 - in1-supply: The input supply for LDO1.
13 - in20-supply: The input supply for LDO20.
[all …]
|
| H A D | active-semi,act8846.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/regulator/active-semi,act8846.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Active-semi ACT8846 regulator
10 - Paul Cercueil <paul@crapouillou.net>
14 const: active-semi,act8846
19 system-power-controller:
22 the system.
25 active-semi,vsel-high:
[all …]
|
| H A D | tps6586x.txt | 4 - compatible: "ti,tps6586x"
5 - reg: I2C slave address
6 - interrupts: the interrupt outputs of the controller
7 - #gpio-cells: number of cells to describe a GPIO
8 - gpio-controller: mark the device as a GPIO controller
9 - regulators: A node that houses a sub-node for each regulator within the
10 device. Each sub-node is identified using the node's name (or the deprecated
11 regulator-compatible property if present), with valid values listed below.
12 The content of each sub-node is defined by the standard binding for
13 regulators; see regulator.txt.
[all …]
|
| H A D | regulator-max77620.txt | 1 Regulator DT binding for MAX77620 Power management IC from Maxim Semiconductor.
3 Device has multiple DCDC(sd[0-3] and LDOs(ldo[0-8]). The input supply
5 Details of regulator properties are defined as child node under
6 sub-node "regulators" which is child node of device node.
8 Please refer file <Documentation/devicetree/bindings/regulator/regulator.txt>
9 for common regulator bindings used by client.
14 -------------------
18 in-sd0-supply: Input supply for SD0, INA-SD0 or INB-SD0 pins.
19 in-sd1-supply: Input supply for SD1.
20 in-sd2-supply: Input supply for SD2.
[all …]
|
| H A D | palmas-pmic.txt | 1 * palmas regulator IP block devicetree bindings
11 - compatible : Should be from the list
12 ti,twl6035-pmic
13 ti,twl6036-pmic
14 ti,twl6037-pmic
15 ti,tps65913-pmic
16 ti,tps65914-pmic
17 ti,tps65917-pmic
18 ti,tps659038-pmic
20 ti,palmas-pmic
[all …]
|
| /openbmc/linux/Documentation/power/regulator/ |
| H A D | consumer.rst | 2 Regulator Consumer Driver Interface
5 This text describes the regulator interface for consumer device drivers.
9 1. Consumer Regulator Access (static & dynamic drivers)
12 A consumer driver can get access to its supply regulator by calling ::
14 regulator = regulator_get(dev, "Vcc");
17 then finds the correct regulator by consulting a machine specific lookup table.
19 regulator that supplies this consumer.
21 To release the regulator the consumer driver should call ::
23 regulator_put(regulator);
25 Consumers can be supplied by more than one regulator e.g. codec consumer with
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/config_files/ |
| H A D | Rainier.json | 3 "phosphor-regulators configuration file for IBM Rainier systems"
24 "comments": ["Rule to set output voltage of a PMBus regulator"],
43 "Rule to set output voltage of PAGE 0 of a PMBus regulator"
54 "Rule to set output voltage of PAGE 1 of a PMBus regulator"
65 "Rule to set output voltage of a PMBus regulator using",
99 "Rule to set IOUT_OC_WARN_LIMIT for a PMBus regulator"
106 "asserts at the roll-over bug identified in the",
128 "Set VOUT_MODE to exponent of -9 for VDD regulator",
138 "limit below 0.5V so the regulator does not trip."
149 "limit above 1.1V so the regulator does not trip."
[all …]
|
| H A D | BlueRidge.json | 3 "phosphor-regulators configuration file for IBM BlueRidge systems"
24 "comments": ["Rule to set output voltage of a PMBus regulator"],
43 "Rule to set output voltage of PAGE 0 of a PMBus regulator"
54 "Rule to set output voltage of PAGE 1 of a PMBus regulator"
65 "Rule to set output voltage of a PMBus regulator using",
99 "Rule to set IOUT_OC_WARN_LIMIT for a PMBus regulator"
106 "asserts at the roll-over bug identified in the",
128 "Set VOUT_MODE to exponent of -9 for VDD regulator",
138 "limit below 0.5V so the regulator does not trip."
149 "limit above 1.1V so the regulator does not trip."
[all …]
|