voltage\-regulators (full) in projects: linux

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:voltage +full:- +full:regulators (Results 1 – 25 of 463) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...19

/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 …]
/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 …]`
/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	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	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 21 https://www.nxp.com/docs/en/data-sheet/PF9453_SDS.pdf 31 - nxp,pca9450a [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	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 …]`
H A D	qcom,spmi-regulator.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/regulator/qcom,spmi-regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Qualcomm SPMI Regulators 10 - Robert Marko <robimarko@gmail.com> 15 - qcom,pm6125-regulators 16 - qcom,pm660-regulators 17 - qcom,pm660l-regulators 18 - qcom,pm8004-regulators [all …]`
/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 …]
/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 …]
/linux/drivers/regulator/
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 …]
H A D	bd96801-regulator.c	1 // SPDX-License-Identifier: GPL-2.0 3 // bd96801-regulator.c ROHM BD96801 regulator driver 11 * regulator safety limits (like limits for the over/under -voltages, over 23 * which implements some of the safety limit configurations - but leaves the 36 #include <linux/mfd/rohm-generic.h> 37 #include <linux/mfd/rohm-bd96801.h> 145 * This is a voltage range that get's appended to selected 148 * and the range from 0x10 to 0x1f is bd96801_buck_init_volts - 150mV ... 149 * bd96801_buck_init_volts - 0. But as the members of linear_range 150 * are all unsigned I will apply offset of -150 mV to value in [all …]
H A D	hi6421-regulator.c	1 // SPDX-License-Identifier: GPL-2.0 3 // Device driver for regulators in Hi6421 IC 5 // Copyright (c) <2011-2014> HiSilicon Technologies Co., Ltd. 7 // Copyright (c) <2013-2014> Linaro Ltd. 22 #include <linux/mfd/hi6421-pmic.h> 25 * struct hi6421_regulator_pdata - Hi6421 regulator data of platform device 33 * struct hi6421_regulator_info - hi6421 regulator information 44 /* HI6421 regulators / 77 / LDO 0, 4~7, 9~14, 16~20 have same voltage table. / 83 / LDO 8, 15 have same voltage table. */ [all …]
H A D	tps65023-regulator.c	`1 // SPDX-License-Identifier: GPL-2.0-only 3 * tps65023-regulator.c 7 * Copyright (C) 2009 Texas Instrument Incorporated - https://www.ti.com/ 64 /* Number of step-down converters available / 66 / Number of LDO voltage regulators available / 68 / Number of total regulators available / 85 .regulators_node = of_match_ptr("regulators"), \ 93 .vsel_mask = ARRAY_SIZE(_t) - 1, \ 104 .regulators_node = of_match_ptr("regulators"), \ 117 / Supported voltage values for regulators */ [all …]`
H A D	max8998.c	1 // SPDX-License-Identifier: GPL-2.0+ 3 // max8998.c - Voltage regulator driver for the Maxim 8998 5 // Copyright (C) 2009-2010 Samsung Electronics 23 #include <linux/mfd/max8998-private.h> 31 unsigned int buck1_idx; /* index to last changed voltage / 51 shift = 3 - (ldo - MAX8998_LDO2); in max8998_get_enable_register() 55 shift = 7 - (ldo - MAX8998_LDO6); in max8998_get_enable_register() 59 shift = 7 - (ldo - MAX8998_LDO14); in max8998_get_enable_register() 63 shift = 7 - (ldo - MAX8998_BUCK1); in max8998_get_enable_register() 67 shift = 7 - (ldo - MAX8998_EN32KHZ_AP); in max8998_get_enable_register() [all …]
H A D	bd718x7-regulator.c	1 // SPDX-License-Identifier: GPL-2.0 3 // bd71837-regulator.c ROHM BD71837MWV/BD71847MWV regulator driver 10 #include <linux/mfd/rohm-bd718x7.h> 51 * controlled by software - or by PMIC internal HW state machine. Whether 52 * regulator should be under SW or HW control can be defined from device-tree. 53 * Let's provide separate ops for regulators to use depending on the "enable 97 /* These functions are used when regulators are under HW state machine control. 99 * status. Most of the regulators have fixed ON or OFF state at RUN/IDLE so for 103 * Note for next hacker - these PMICs have a register where the HW state can be 104 * read. If assuming RUN appears to be false in your use-case - you can [all …]
H A D	max77686-regulator.c	1 // SPDX-License-Identifier: GPL-2.0+ 3 // max77686.c - Regulator driver for the Maxim 77686 21 #include <linux/mfd/max77686-private.h> 38 * It is the same as 'off' for other regulators. 43 * Forcing low power mode: LDO1, 3-5, 9, 13, 17-26 48 * - LDO2, 6-8, 10-12, 14-16 49 * - buck[1234] 96 * Map normal mode to proper value for such regulators. 105 if (test_bit(id, max77686->gpio_enabled)) in max77686_map_normal_mode() 122 ret = regmap_update_bits(rdev->regmap, rdev->desc->enable_reg, in max77686_set_suspend_disable() [all …]
/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 …]
/linux/Documentation/devicetree/bindings/mfd/
H A D	maxim,max8998.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> 13 The Maxim MAX8998 is a Power Management IC which includes voltage/current 14 regulators, real time clock, battery charging controller and several other 15 sub-blocks. It is interfaced using an I2C interface. Each sub-block is 21 - maxim,max8998 22 - national,lp3974 23 - ti,lp3974 [all …]`
H A D	rohm,bd96801-pmic.yaml	`1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mfd/rohm,bd96801-pmic.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com> 13 BD96801 and BD96805 are automotive grade, single-chip power management ICs. 15 over-/under voltage and over current detection and a watchdog. 20 - rohm,bd96801 21 - rohm,bd96805 38 interrupt-names: [all …]`
H A D	rohm,bd71847-pmic.yaml	1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/mfd/rohm,bd71847-pmic.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Matti Vaittinen <mazziesaccount@gmail.com> 14 single-core, dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is 16 BD71850MWV integrate 6 Buck regulators and 6 LDOs. 18 …/www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applica… 19 …//www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applic… 24 - rohm,bd71847 [all …]
H A D	richtek,rt5033.yaml	`1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Jakob Hauser <jahau@rocketmail.com> 28 regulators: 30 The regulators of RT5033 have to be instantiated under a sub-node named 31 "regulators". For SAFE_LDO voltage there is only one value of 4.9 V. LDO 32 voltage ranges from 1.2 V to 3.0 V in 0.1 V steps. BUCK voltage ranges 44 $ref: /schemas/power/supply/richtek,rt5033-charger.yaml# 47 - compatible [all …]`
/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 Electronics 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 …]

12 3 4 5 6 7 8 9 10 >>...19