| /openbmc/linux/drivers/regulator/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 bool "Voltage and Current Regulator Support"
6 Generic Voltage and Current Regulator support.
8 This framework is designed to provide a generic interface to voltage
9 and current regulators within the Linux kernel. It's intended to
10 provide voltage and current control to client or consumer drivers and
16 to both voltage regulators (where voltage output is controllable) and
21 regulators.
34 tristate "Fixed voltage regulator support"
36 This driver provides support for fixed voltage regulators,
[all …]
|
| H A D | bd71828-regulator.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 // bd71828-regulator.c ROHM BD71828GW-DS1 regulator driver
10 #include <linux/mfd/rohm-bd71828.h>
102 return rohm_regulator_set_dvs_levels(&data->dvs, np, desc, cfg->regmap); in buck_set_hw_dvs_levels()
112 struct regmap *regmap = cfg->regmap; in ldo6_parse_dt()
113 static const char * const props[] = { "rohm,dvs-run-voltage", in ldo6_parse_dt()
114 "rohm,dvs-idle-voltage", in ldo6_parse_dt()
115 "rohm,dvs-suspend-voltage", in ldo6_parse_dt()
116 "rohm,dvs-lpsr-voltage" }; in ldo6_parse_dt()
123 if (ret != -EINVAL) in ldo6_parse_dt()
[all …]
|
| H A D | helpers.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 // helpers.c -- Voltage/Current Regulator framework helper functions.
20 * regulator_is_enabled_regmap - standard is_enabled() for regmap users
24 * Regulators that use regmap for their register I/O can set the
33 ret = regmap_read(rdev->regmap, rdev->desc->enable_reg, &val); in regulator_is_enabled_regmap()
37 val &= rdev->desc->enable_mask; in regulator_is_enabled_regmap()
39 if (rdev->desc->enable_is_inverted) { in regulator_is_enabled_regmap()
40 if (rdev->desc->enable_val) in regulator_is_enabled_regmap()
41 return val != rdev->desc->enable_val; in regulator_is_enabled_regmap()
44 if (rdev->desc->enable_val) in regulator_is_enabled_regmap()
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/ |
| H A D | README.md | 1 # phosphor-regulators
5 The `phosphor-regulators` application configures and monitors voltage
6 regulators. The application is controlled by a JSON configuration file.
8 The application does not control how voltage regulators are enabled or how to
12 ## Configuring Voltage Regulators
14 The configuration of voltage regulators can be modified. Configuration changes
17 The most common configuration change is setting the output voltage for a
22 regulators are enabled.
24 ## Monitoring Voltage Regulators
28 - Sensor monitoring
[all …]
|
| /openbmc/u-boot/drivers/power/regulator/ |
| H A D | Kconfig | 4 ---help---
6 UCLASS_REGULATOR - designed to provide a common API for basic regulator's
7 functions, like get/set Voltage or Current value, enable state, etc...
10 - 'include/power/pmic.h'
11 - 'include/power/regulator.h'
12 - 'drivers/power/pmic/pmic-uclass.c'
13 - 'drivers/power/pmic/regulator-uclass.c'
20 bool "Enable regulators for SPL"
22 ---help---
23 Regulators are seldom needed in SPL. Even if they are accessed, some
[all …]
|
| /openbmc/docs/designs/ |
| H A D | voltage-regulator-configuration.md | 1 # Voltage Regulator Configuration
8 Created: 2019-07-13
12 [Voltage regulators][1] have many configurable properties such as output
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
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.
24 Hardware engineers must specify many low-level configuration values for a
25 regulator. Some simple examples include output voltage, over-current limit, and
33 non-volatile memory on the regulator. This provides the hardware/power-on
[all …]
|
| /openbmc/linux/Documentation/power/regulator/ |
| H A D | overview.rst | 2 Linux voltage and current regulator framework
9 voltage and current regulators.
12 in order to save power and prolong battery life. This applies to both voltage
13 regulators (where voltage output is controllable) and current sinks (where
26 - Regulator
27 - Electronic device that supplies power to other devices.
28 Most regulators can enable and disable their output while
29 some can control their output voltage and or current.
31 Input Voltage -> Regulator -> Output Voltage
34 - PMIC
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A D | max8998.txt | 1 * Maxim MAX8998, National/TI LP3974 multi-function device
3 The Maxim MAX8998 is a multi-function device which includes voltage/current
4 regulators, real time clock, battery charging controller and several
5 other sub-blocks. It is interfaced using an I2C interface. Each sub-block
8 PMIC sub-block
9 --------------
11 The PMIC sub-block contains a number of voltage and current regulators,
12 with controllable parameters and dynamic voltage scaling capability.
17 - compatible: Should be one of the following:
18 - "maxim,max8998" for Maxim MAX8998
[all …]
|
| H A D | samsung,s5m8767.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
16 The Samsung S5M8767 is a Power Management IC which includes voltage
17 and current regulators, RTC, clock outputs and other sub-blocks.
21 const: samsung,s5m8767-pmic
34 regulators:
37 List of child nodes that specify the regulators.
39 s5m8767,pmic-buck2-dvs-voltage:
[all …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-regulator | 8 regulators which can report that input value.
20 supplying power to the system (unless some non-Linux
34 regulators which can report that output value.
38 - off
39 - on
40 - error
41 - fast
42 - normal
43 - idle
44 - standby
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | nvidia,tegra-regulators-coupling.txt | 1 NVIDIA Tegra Regulators Coupling
4 NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators.
5 Thus on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30
8 Tegra20 voltage coupling
9 ------------------------
11 On Tegra20 SoC's there are 3 coupled regulators: CORE, RTC and CPU.
13 and they both shall be higher than the CPU voltage by at least 120mV.
15 Tegra30 voltage coupling
16 ------------------------
18 On Tegra30 SoC's there are 2 coupled regulators: CORE and CPU. The CORE
[all …]
|
| H A D | ltc3676.txt | 1 Linear Technology LTC3676 8-output regulators
4 - compatible: "lltc,ltc3676"
5 - reg: I2C slave address
8 - regulators: Contains eight regulator child nodes sw1, sw2, sw3, sw4,
12 Each regulator is defined using the standard binding for regulators. The
14 the resistor values of their external feedback voltage dividers:
17 - lltc,fb-voltage-divider: An array of two integers containing the resistor
18 values R1 and R2 of the feedback voltage divider in ohms.
20 Regulators sw1, sw2, sw3, sw4 can regulate the feedback reference from:
21 412.5mV to 800mV in 12.5 mV steps. The output voltage thus ranges between
[all …]
|
| H A D | ltc3589.txt | 1 Linear Technology LTC3589, LTC3589-1, and LTC3589-2 8-output regulators
4 - compatible: "lltc,ltc3589", "lltc,ltc3589-1" or "lltc,ltc3589-2"
5 - reg: I2C slave address
8 - regulators: Contains eight regulator child nodes sw1, sw2, sw3, bb-out,
12 Each regulator is defined using the standard binding for regulators. The
13 nodes for sw1, sw2, sw3, bb-out, ldo1, and ldo2 additionally need to specify
14 the resistor values of their external feedback voltage dividers:
17 - lltc,fb-voltage-divider: An array of two integers containing the resistor
18 values R1 and R2 of the feedback voltage divider in ohms.
20 Regulators sw1, sw2, sw3, and ldo2 can regulate the feedback reference from
[all …]
|
| H A D | regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Voltage/Current Regulators
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
14 regulator-name:
18 regulator-min-microvolt:
19 description: smallest voltage consumers may set
21 regulator-max-microvolt:
[all …]
|
| H A D | rohm,bd71847-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/regulator/rohm,bd71847-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ROHM BD71847 and BD71850 Power Management Integrated Circuit regulators
10 - Matti Vaittinen <mazziesaccount@gmail.com>
13 List of regulators provided by this controller. BD71847 regulators node
15 Documentation/devicetree/bindings/mfd/rohm,bd71847-pmic.yaml
18 binding for regulators at
21 regulator-boot-on at least for BUCK5. LDO6 is supplied by it and it must
[all …]
|
| H A D | nxp,pca9450-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/regulator/nxp,pca9450-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: NXP PCA9450A/B/C Power Management Integrated Circuit regulators
10 - Robin Gong <yibin.gong@nxp.com>
15 binding for regulators at
18 https://www.nxp.com/docs/en/data-sheet/PCA9450DS.pdf
28 - nxp,pca9450a
29 - nxp,pca9450b
[all …]
|
| H A D | rohm,bd71837-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/regulator/rohm,bd71837-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ROHM BD71837 Power Management Integrated Circuit regulators
10 - Matti Vaittinen <mazziesaccount@gmail.com>
13 List of regulators provided by this controller. BD71837 regulators node
15 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.yaml
18 binding for regulators at
21 regulator-boot-on at least for BUCK6 and BUCK7 so that those are not
[all …]
|
| H A D | maxim,max8997.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Krzysztof Kozlowski <krzk@kernel.org>
13 The Maxim MAX8997 is a Power Management IC which includes voltage and current
14 regulators, charger controller with fuel gauge, RTC, clock outputs, haptic
15 motor driver, flash LED driver and Micro-USB Interface Controller.
22 const: maxim,max8997-pmic
24 charger-supply:
30 - description: irq1 interrupt
[all …]
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | regulator.rst | 1 .. Copyright 2007-2008 Wolfson Microelectronics
8 Voltage and current regulator API
18 control voltage and current regulators.
22 both voltage regulators (where voltage output is controllable) and
30 --------
36 Electronic device that supplies power to other devices. Most regulators
38 output voltage or current.
54 An IC which contains numerous regulators and often also other
62 drivers use `get <#API-regulator-get>`__ and
63 `put <#API-regulator-put>`__ operations to acquire and release
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | README.md | 1 # phosphor-regulators Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Example](#example)
8 - [Name](#name)
9 - [Contents](#contents)
10 - [Validation](#validation)
11 - [Installation](#installation)
12 - [Loading and Reloading](#loading-and-reloading)
13 - [Testing](#testing)
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/opp/ |
| H A D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Viresh Kumar <viresh.kumar@linaro.org>
13 Devices work at voltage-current-frequency combinations and some implementations
25 pattern: '^opp-table(-[a-z0-9]+)?$'
27 opp-shared:
30 their DVFS state together, i.e. they share clock/voltage/current lines.
31 Missing property means devices have independent clock/voltage/current
[all …]
|
| H A D | ti,omap-opp-supply.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/opp/ti,omap-opp-supply.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 registers, which contain OPP-specific voltage information tailored
16 Also, some supplies may have an associated vbb-supply, an Adaptive
18 w.r.t the vdd-supply and clk when making an OPP transition. By
19 supplying two regulators to the device that will undergo OPP
20 transitions, we can use the multi-regulator support implemented by
21 the OPP core to describe both regulators the platform needs. The
[all …]
|
| /openbmc/linux/include/linux/mfd/ |
| H A D | max8998.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * max8998.h - Voltage regulator driver for the Maxim 8998
5 * Copyright (C) 2009-2010 Samsung Electrnoics
46 * max8998_regulator_data - regulator data
49 * @reg_node: DT node of regulator (unused on non-DT platforms)
58 * struct max8998_board - packages regulator init data
59 * @regulators: array of defined regulators
60 * @num_regulators: number of regulators used
64 * registers set by buck?_voltage?. The voltage of BUCK1/2 cannot
66 * @buck1_voltage: BUCK1 DVS mode 1 voltage registers
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/regulator/ |
| H A D | max77686.txt | 1 MAXIM, MAX77686 regulators
4 - drivers/power/pmic/max77686.c (as parent I/O device)
5 - drivers/power/regulator/max77686.c (for child regulators)
10 - doc/device-tree-bindings/pmic/max77686.txt
13 - voltage-regulators: required for the PMIC driver
16 - regulator-name: used for regulator uclass platform data '.name'
19 - regulator-min-microvolt: minimum allowed Voltage to set
20 - regulator-max-microvolt: minimum allowed Voltage to set
21 - regulator-always-on: regulator should be never disabled
22 - regulator-boot-on: regulator should be enabled by the bootloader
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/power/ |
| H A D | rockchip-io-domain.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/rockchip-io-domain.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Rockchip SRAM for IO Voltage Domains
10 - Heiko Stuebner <heiko@sntech.de>
14 kept in sync between the regulators and the SoC using a special
23 General Register File (GRF) in sync with the actual value of a voltage
27 any logic for deciding what voltage we should set regulators to
28 any logic for deciding whether regulators (or internal SoC blocks)
[all …]
|