Searched +full:regulator +full:- +full:fixed (Results 1 – 25 of 49) sorted by relevance
12
| /Documentation/devicetree/bindings/regulator/ |
| D | fixed-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/regulator/fixed-regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Fixed Voltage regulators 10 - Liam Girdwood <lgirdwood@gmail.com> 11 - Mark Brown <broonie@kernel.org> 14 Any property defined as part of the core regulator binding, defined in 15 regulator.yaml, can also be used. However a fixed voltage regulator is 16 expected to have the regulator-min-microvolt and regulator-max-microvolt [all …]
|
| D | mt6358-regulator.txt | 1 MediaTek MT6358 Regulator 4 subnodes of the MT6358 regulators node. Each regulator is named according 5 to its regulator type, buck_<name> and ldo_<name>. The definition for each 7 Documentation/devicetree/bindings/regulator/regulator.txt. 27 compatible = "mediatek,mt6358-regulator"; 30 regulator-compatible = "buck_vdram1"; 31 regulator-name = "vdram1"; 32 regulator-min-microvolt = <500000>; 33 regulator-max-microvolt = <2087500>; 34 regulator-ramp-delay = <12500>; [all …]
|
| D | sy8106a-regulator.txt | 1 SY8106A Voltage regulator 4 - compatible: Must be "silergy,sy8106a" 5 - reg: I2C slave address - must be <0x65> 6 - silergy,fixed-microvolt - the voltage when I2C regulating is disabled (set 7 by external resistor like a fixed voltage) 9 Any property defined as part of the core regulator binding, defined in 10 ./regulator.txt, can also be used. 17 regulator-name = "sy8106a-vdd"; 18 silergy,fixed-microvolt = <1200000>; 19 regulator-min-microvolt = <1000000>; [all …]
|
| D | cirrus,lochnagar.txt | 5 Logic devices on mini-cards, as well as allowing connection of 11 This binding document describes the binding for the regulator portion 15 [1] Regulator: ../regulator/regulator.txt 20 Optional sub-nodes: 22 - VDDCORE : Initialisation data for the VDDCORE regulator, which 23 supplies the CODECs digital core if it has no build regulator for that 26 - compatible : One of the following strings: 27 "cirrus,lochnagar2-vddcore" 28 - SYSVDD-supply: Primary power supply for the Lochnagar. 30 - MICVDD : Initialisation data for the MICVDD regulator, which [all …]
|
| 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, 10 documented in Documentation/devicetree/bindings/regulator/regulator.txt. 12 Each regulator is defined using the standard binding for regulators. The 17 - lltc,fb-voltage-divider: An array of two integers containing the resistor 24 Regulators ldo1, ldo2, and ldo4 have a fixed 0.725 V reference and thus output 25 0.725 * (1 + R1/R2) V. The ldo3 regulator is fixed to 1.8 V. The ldo1 standby 26 regulator can not be disabled and thus should have the regulator-always-on [all …]
|
| D | mt6397-regulator.txt | 1 Mediatek MT6397 Regulator 4 - compatible: "mediatek,mt6397-regulator" 5 - mt6397regulator: List of regulators provided by this controller. It is named 6 according to its regulator type, buck_<name> and ldo_<name>. 8 for regulators at Documentation/devicetree/bindings/regulator/regulator.txt. 24 compatible = "mediatek,mt6397-regulator"; 27 regulator-compatible = "buck_vpca15"; 28 regulator-name = "vpca15"; 29 regulator-min-microvolt = < 850000>; 30 regulator-max-microvolt = <1350000>; [all …]
|
| 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, 10 documented in Documentation/devicetree/bindings/regulator/regulator.txt. 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 17 - lltc,fb-voltage-divider: An array of two integers containing the resistor 22 0.3625 * (1 + R1/R2) V and 0.75 * (1 + R1/R2) V. Regulators bb-out and ldo1 23 have a fixed 0.8 V reference and thus output 0.8 * (1 + R1/R2) V. The ldo3 [all …]
|
| D | vexpress.txt | 2 ------------------------------------ 5 - "compatible" value: "arm,vexpress-volt" 6 - "arm,vexpress-sysreg,func" when controlled via vexpress-sysreg 7 (see Documentation/devicetree/bindings/arm/vexpress-sysreg.txt 10 Required regulator properties: 11 - "regulator-name" 12 - "regulator-always-on" 14 Optional regulator properties: 15 - "regulator-min-microvolt" 16 - "regulator-max-microvolt" [all …]
|
| D | st,stpmic1-regulator.txt | 3 Regulator Nodes are optional depending on needs. 6 - buck1 for Buck BUCK1 7 - buck2 for Buck BUCK2 8 - buck3 for Buck BUCK3 9 - buck4 for Buck BUCK4 10 - ldo1 for LDO LDO1 11 - ldo2 for LDO LDO2 12 - ldo3 for LDO LDO3 13 - ldo4 for LDO LDO4 14 - ldo5 for LDO LDO5 [all …]
|
| D | gpio-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Liam Girdwood <lgirdwood@gmail.com> 11 - Mark Brown <broonie@kernel.org> 14 Any property defined as part of the core regulator binding, defined in 15 regulator.txt, can also be used. 18 - $ref: "regulator.yaml#" 22 const: regulator-gpio [all …]
|
| D | qcom,rpmh-regulator.txt | 3 rpmh-regulator devices support PMIC regulator management via the Voltage 4 Regulator Manager (VRM) and Oscillator Buffer (XOB) RPMh accelerators. The APPS 7 parameters for a given regulator: enable state, output voltage, and operating 8 mode. The XOB allows changing only a single parameter for a given regulator: 10 enable state of any PMIC peripheral. It is used for clock buffers, low-voltage 11 switches, and LDO/SMPS regulators which have a fixed voltage and mode. 19 RPMh device node. The second level describes each regulator within the PMIC 23 The names used for regulator nodes must match those supported by a given PMIC. 24 Supported regulator node names: 25 PM8005: smps1 - smps4 [all …]
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | winstar,wf35ltiacd.txt | 4 - compatible: should be "winstar,wf35ltiacd" 5 - power-supply: regulator to provide the VCC supply voltage (3.3 volts) 7 This binding is compatible with the simple-panel binding, which is specified 8 in simple-panel.txt in this directory. 12 compatible = "pwm-backlight"; 14 brightness-levels = <0 31 63 95 127 159 191 223 255>; 15 default-brightness-level = <191>; 16 power-supply = <&bl_reg>; 20 compatible = "regulator-fixed"; 21 regulator-name = "backlight-power-supply"; [all …]
|
| /Documentation/devicetree/bindings/leds/irled/ |
| D | spi-ir-led.txt | 8 - compatible: should be "ir-spi-led". 11 - duty-cycle: 8 bit balue that represents the percentage of one period 13 - led-active-low: boolean value that specifies whether the output is 15 - power-supply: specifies the power source. It can either be a regulator 16 or a gpio which enables a regulator, i.e. a regulator-fixed as 18 Documentation/devicetree/bindings/regulator/fixed-regulator.yaml 23 compatible = "ir-spi-led"; 25 spi-max-frequency = <5000000>; 26 power-supply = <&vdd_led>; 27 led-active-low; [all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | qcom,spmi-pmic.txt | 1 Qualcomm SPMI PMICs multi-function device bindings 6 register space up into logical pieces, and set of fixed register 13 16-bit SPMI slave address space into 256 smaller fixed-size regions, 256 bytes 14 each. A function can consume one or more of these fixed-size register regions. 17 - compatible: Should contain one of: 35 or generalized "qcom,spmi-pmic". 36 - reg: Specifies the SPMI USID slave address for this device. 41 - compatible: Should contain "qcom,xxx", where "xxx" is a peripheral name. 44 - interrupts: Interrupts are specified as a 4-tuple. For more information 46 Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.txt [all …]
|
| D | rohm,bd70528-pmic.txt | 3 BD70528MWV is an ultra-low quiescent current general purpose, single-chip, 4 power management IC for battery-powered portable devices. The IC 5 integrates 3 ultra-low current consumption buck converters, 3 LDOs and 2 6 LED Drivers. Also included are 4 GPIOs, a real-time clock (RTC), a 32kHz 7 clock gate, high-accuracy VREF for use with an external ADC, flexible 8 dual-input power path, 10 bit SAR ADC for battery temperature monitor and 12 - compatible : Should be "rohm,bd70528" 13 - reg : I2C slave address. 14 - interrupts : The interrupt line the device is connected to. 15 - interrupt-controller : To indicate BD70528 acts as an interrupt controller. [all …]
|
| D | max14577.txt | 1 Maxim MAX14577/77836 Multi-Function Device 3 MAX14577 is a Multi-Function Device with Micro-USB Interface Circuit, Li+ 11 - compatible : Must be "maxim,max14577" or "maxim,max77836". 12 - reg : I2C slave address for the max14577 chip (0x25 for max14577/max77836) 13 - interrupts : IRQ line for the chip. 17 - charger : 20 - compatible : "maxim,max14577-charger" 21 or "maxim,max77836-charger" 22 - maxim,fast-charge-uamp : Current in uA for Fast Charge; 24 - for max14577: 90000 - 950000; [all …]
|
| D | rohm,bd71837-pmic.txt | 4 single-core, dual-core, and quad-core SoCs such as NXP-i.MX 8M. They are 10 https://www.rohm.com/datasheet/BD71837MWV/bd71837mwv-e 12 https://www.rohm.com/datasheet/BD71847AMWV/bd71847amwv-e 15 - compatible : Should be "rohm,bd71837" for bd71837 17 - reg : I2C slave address. 18 - interrupt-parent : Phandle to the parent interrupt controller. 19 - interrupts : The interrupt line the device is connected to. 20 - clocks : The parent clock connected to PMIC. If this is missing 22 - #clock-cells : Should be 0. 23 - regulators: : List of child nodes that specify the regulators. [all …]
|
| 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 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, 17 - compatible: Should be one of the following: 18 - "maxim,max8998" for Maxim MAX8998 19 - "national,lp3974" or "ti,lp3974" for National/TI LP3974. 20 - reg: Specifies the i2c slave address of the pmic block. It should be 0x66. [all …]
|
| /Documentation/devicetree/bindings/iio/dac/ |
| D | ti-dac082s085.txt | 1 Texas Instruments 8/10/12-bit 2/4-channel DAC driver 4 - compatible: Must be one of: 11 - reg: Chip select number. 12 - spi-cpha, spi-cpol: SPI mode (0,1) or (1,0) must be used, so specify 13 either spi-cpha or spi-cpol (but not both). 14 - vref-supply: Phandle to the external reference voltage supply. 17 ../../spi/spi-bus.txt. 20 vref_2v5_reg: regulator-vref { 21 compatible = "regulator-fixed"; 22 regulator-name = "2v5"; [all …]
|
| D | ltc2632.txt | 4 - compatible: Has to contain one of the following: 5 lltc,ltc2632-l12 6 lltc,ltc2632-l10 7 lltc,ltc2632-l8 8 lltc,ltc2632-h12 9 lltc,ltc2632-h10 10 lltc,ltc2632-h8 12 Property rules described in Documentation/devicetree/bindings/spi/spi-bus.txt 13 apply. In particular, "reg" and "spi-max-frequency" properties must be given. 16 - vref-supply: Phandle to the external reference voltage supply. This should [all …]
|
| /Documentation/devicetree/bindings/input/ |
| D | pwm-beeper.txt | 6 - compatible: should be "pwm-beeper" 7 - pwms: phandle to the physical PWM device 10 - amp-supply: phandle to a regulator that acts as an amplifier for the beeper 11 - beeper-hz: bell frequency in Hz 16 compatible = "fixed-regulator"; 21 compatible = "pwm-beeper"; 23 amp-supply = <&beeper_amp>;
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l32.txt | 5 - compatible : "cirrus,cs35l32" 7 - reg : the I2C address of the device for I2C. Address is determined by the level 10 - VA-supply, VP-supply : power supplies for the device, 11 as covered in Documentation/devicetree/bindings/regulator/regulator.txt. 15 - reset-gpios : a GPIO spec for the reset pin. If specified, it will be 18 - cirrus,boost-manager : Boost voltage control. 19 0 = Automatically managed. Boost-converter output voltage is the higher 21 1 = Automatically managed irrespective of audio, adapting for low-power 22 dissipation when LEDs are ON, and operating in Fixed-Boost Bypass Mode 24 2 = (Default) Boost voltage fixed in Bypass Mode (VBST = VP). [all …]
|
| D | cs42l56.txt | 5 - compatible : "cirrus,cs42l56" 7 - reg : the I2C address of the device for I2C 9 - VA-supply, VCP-supply, VLDO-supply : power supplies for the device, 10 as covered in Documentation/devicetree/bindings/regulator/regulator.txt. 14 - cirrus,gpio-nreset : GPIO controller's phandle and the number 17 - cirrus,chgfreq-divisor : Values used to set the Charge Pump Frequency. 24 - cirrus,ain1a-ref-cfg, ain1b-ref-cfg : boolean, If present, AIN1A or AIN1B are configured 25 as a pseudo-differential input referenced to AIN1REF/AIN3A. 27 - cirrus,ain2a-ref-cfg, ain2b-ref-cfg : boolean, If present, AIN2A or AIN2B are configured 28 as a pseudo-differential input referenced to AIN2REF/AIN3B. [all …]
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | mt7530.txt | 6 - compatible: may be compatible = "mediatek,mt7530" 8 - #address-cells: Must be 1. 9 - #size-cells: Must be 0. 10 - mediatek,mcm: Boolean; if defined, indicates that either MT7530 is the part 11 on multi-chip module belong to MT7623A has or the remotely standalone 16 - core-supply: Phandle to the regulator node necessary for the core power. 17 - io-supply: Phandle to the regulator node necessary for the I/O power. 18 See Documentation/devicetree/bindings/regulator/mt6323-regulator.txt 19 for details for the regulator setup on these boards. 23 - reset-gpios: Should be a gpio specifier for a reset line. [all …]
|
| /Documentation/driver-api/ |
| 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 43 may either be static, requiring only a fixed supply, or dynamic, 44 requiring active management of the regulator at runtime. [all …]
|
12