Home
last modified time | relevance | path

Searched +full:regulator +full:- +full:on +full:- +full:in +full:- +full:suspend (Results 1 – 23 of 23) sorted by relevance

/Documentation/devicetree/bindings/regulator/
Dmcp16502-regulator.txt4 - compatible: "microchip,mcp16502"
5 - reg: I2C slave address
6 - lpm-gpios: GPIO for LPM pin. Note that this GPIO *must* remain high during
7 suspend-to-ram, keeping the PMIC into HIBERNATE mode.
8 - regulators: A node that houses a sub-node for each regulator within
9 the device. Each sub-node is identified using the node's
10 name. The content of each sub-node is defined by the
11 standard binding for regulators; see regulator.txt.
14 1) VDD_IO - Buck (1.2 - 3.7 V)
15 2) VDD_DDR - Buck (0.6 - 1.85 V)
[all …]
Dregulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
14 regulator-name:
15 description: A string used as a descriptive name for regulator outputs
18 regulator-min-microvolt:
21 regulator-max-microvolt:
[all …]
Dact8945a-regulator.txt1 Device-Tree bindings for regulators of Active-semi ACT8945A Multi-Function Device
4 - compatible: "active-semi,act8945a", please refer to ../mfd/act8945a.txt.
7 - active-semi,vsel-high: Indicates if the VSEL pin is set to logic-high.
8 If this property is missing, assume the VSEL pin is set to logic-low.
11 - vp1-supply: The input supply for REG_DCDC1
12 - vp2-supply: The input supply for REG_DCDC2
13 - vp3-supply: The input supply for REG_DCDC3
14 - inl45-supply: The input supply for REG_LDO1 and REG_LDO2
15 - inl67-supply: The input supply for REG_LDO3 and REG_LDO4
17 Any standard regulator properties can be used to configure the single regulator.
[all …]
Dmax77802.txt3 This is a part of device tree bindings of MAX77802 multi-function device.
4 More information can be found in bindings/mfd/max77802.txt file.
6 The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout (LDO)
9 Following properties should be present in main device node of the MFD chip.
12 - inb1-supply: The input supply for BUCK1
13 - inb2-supply: The input supply for BUCK2
14 - inb3-supply: The input supply for BUCK3
15 - inb4-supply: The input supply for BUCK4
16 - inb5-supply: The input supply for BUCK5
17 - inb6-supply: The input supply for BUCK6
[all …]
Dregulator-max77620.txt1 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 -------------------
15 The input supply of regulators are the optional properties on the
18 in-sd0-supply: Input supply for SD0, INA-SD0 or INB-SD0 pins.
19 in-sd1-supply: Input supply for SD1.
[all …]
Dact8865-regulator.txt2 -------------------
5 - compatible: "active-semi,act8846" or "active-semi,act8865" or "active-semi,act8600"
6 - reg: I2C slave address
9 - system-power-controller: Telling whether or not this pmic is controlling
10 the system power. See Documentation/devicetree/bindings/power/power-controller.txt .
11 - active-semi,vsel-high: Indicates the VSEL pin is high.
15 - for act8600:
16 - vp1-supply: The input supply for DCDC_REG1
17 - vp2-supply: The input supply for DCDC_REG2
18 - vp3-supply: The input supply for DCDC_REG3
[all …]
Dmax77686.txt3 This is a part of the device tree bindings of MAX77686 multi-function device.
4 More information can be found in ../mfd/max77686.txt file.
6 The MAX77686 PMIC has 9 high-efficiency Buck and 26 Low-DropOut (LDO)
9 Following properties should be present in main device node of the MFD chip.
12 - voltage-regulators : The regulators of max77686 have to be instantiated
13 under subnode named "voltage-regulators" using the following format.
16 regulator-compatible = LDOn/BUCKn
17 standard regulator constraints....
19 refer Documentation/devicetree/bindings/regulator/regulator.txt
21 The regulator node's name should be initialized with a string
[all …]
Drohm,bd71837-regulator.txt1 ROHM BD71837 and BD71847 Power Management Integrated Circuit regulator bindings
4 - regulator-name: should be "buck1", ..., "buck8" and "ldo1", ..., "ldo7" for
10 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt
11 Regulator nodes should be named to BUCK_<number> and LDO_<number>. The
14 Documentation/devicetree/bindings/regulator/regulator.txt.
16 regulator-boot-on at least for BUCK6 and BUCK7 so that those are not
21 The valid names for BD71837 regulator nodes are:
25 The valid names for BD71847 regulator nodes are:
30 - rohm,dvs-run-voltage : PMIC default "RUN" state voltage in uV.
32 - rohm,dvs-idle-voltage : PMIC default "IDLE" state voltage in uV.
[all …]
Dsamsung,s5m8767.txt1 Binding for Samsung S5M8767 regulator block
4 This is a part of device tree bindings for S5M family multi-function devices.
5 More information can be found in bindings/mfd/sec-core.txt file.
9 To register these with regulator framework instantiate under main device node
10 a sub-node named "regulators" with more sub-nodes for each regulator using the
11 common regulator binding documented in:
12 - Documentation/devicetree/bindings/regulator/regulator.txt
16 - s5m8767,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
20 - s5m8767,pmic-buck3-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
24 - s5m8767,pmic-buck4-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
[all …]
/Documentation/ABI/testing/
Dsysfs-class-regulator1 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
19 'disabled' means the regulator output is OFF and is not
20 supplying power to the system (unless some non-Linux
26 NOTE: this field can be used in conjunction with microvolts
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 …]
/Documentation/devicetree/bindings/mmc/
Dti-omap-hsmmc.txt3 The Highspeed MMC Host Controller on TI OMAP and 66AK2G family
10 --------------------
11 - compatible:
12 Should be "ti,omap2-hsmmc", for OMAP2 controllers
13 Should be "ti,omap3-hsmmc", for OMAP3 controllers
14 Should be "ti,omap3-pre-es3-hsmmc" for OMAP3 controllers pre ES3.0
15 Should be "ti,omap4-hsmmc", for OMAP4 controllers
16 Should be "ti,am33xx-hsmmc", for AM335x controllers
17 Should be "ti,k2g-hsmmc", "ti,omap4-hsmmc" for 66AK2G controllers.
20 ---------------------------------
[all …]
/Documentation/devicetree/bindings/pwm/
Dnvidia,tegra20-pwm.txt4 - compatible: Must be:
5 - "nvidia,tegra20-pwm": for Tegra20
6 - "nvidia,tegra30-pwm", "nvidia,tegra20-pwm": for Tegra30
7 - "nvidia,tegra114-pwm", "nvidia,tegra20-pwm": for Tegra114
8 - "nvidia,tegra124-pwm", "nvidia,tegra20-pwm": for Tegra124
9 - "nvidia,tegra132-pwm", "nvidia,tegra20-pwm": for Tegra132
10 - "nvidia,tegra210-pwm", "nvidia,tegra20-pwm": for Tegra210
11 - "nvidia,tegra186-pwm": for Tegra186
12 - reg: physical base address and length of the controller's registers
13 - #pwm-cells: should be 2. See pwm.txt in this directory for a description of
[all …]
/Documentation/devicetree/bindings/mfd/
Dmax77620.txt4 -------------------
5 - compatible: Must be one of
9 - reg: I2C device address.
12 -------------------
13 - interrupts: The interrupt on the parent the controller is
15 - interrupt-controller: Marks the device node as an interrupt controller.
16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells
17 variant of <../interrupt-controller/interrupts.txt>
19 are defined at dt-bindings/mfd/max77620.h.
21 - system-power-controller: Indicates that this PMIC is controlling the
[all …]
Dbd9571mwv.txt4 - compatible : Should be "rohm,bd9571mwv".
5 - reg : I2C slave address.
6 - interrupts : The interrupt line the device is connected to.
7 - interrupt-controller : Marks the device node as an interrupt controller.
8 - #interrupt-cells : The number of cells to describe an IRQ, should be 2.
11 masks from ../interrupt-controller/interrupts.txt.
12 - gpio-controller : Marks the device node as a GPIO Controller.
13 - #gpio-cells : Should be two. The first cell is the pin number and
16 - regulators: : List of child nodes that specify the regulator
19 - vd09
[all …]
/Documentation/devicetree/bindings/display/
Dtruly,nt35597.txt4 for use in the 2K display on the Qualcomm SDM845 MTP board.
7 - compatible: should be "truly,nt35597-2K-display"
8 - vdda-supply: phandle of the regulator that provides the supply voltage
10 - vdispp-supply: phandle of the regulator that provides the supply voltage
12 - vdispn-supply: phandle of the regulator that provides the supply voltage
14 - reset-gpios: phandle of gpio for reset line
15 This should be 8mA, gpio can be configured using mux, pinctrl, pinctrl-names
17 - mode-gpios: phandle of the gpio for choosing the mode of the display
20 - ports: This device has two video ports driven by two DSIs. Their connections
21 are modeled using the OF graph bindings specified in
[all …]
/Documentation/devicetree/bindings/net/wireless/
Dmarvell-8xxx.txt2 ------
10 - compatible : should be one of the following:
19 - marvell,caldata* : A series of properties with marvell,caldata prefix,
21 initialization. This is an array of unsigned 8-bit values.
24 "marvell,caldata-txpwrlimit-2g" (length = 566).
25 "marvell,caldata-txpwrlimit-5g-sub0" (length = 502).
26 "marvell,caldata-txpwrlimit-5g-sub1" (length = 688).
27 "marvell,caldata-txpwrlimit-5g-sub2" (length = 750).
28 "marvell,caldata-txpwrlimit-5g-sub3" (length = 502).
29 - marvell,wakeup-pin : a wakeup pin number of wifi chip which will be configured
[all …]
/Documentation/power/
Dcharger-manager.rst7 Charger Manager provides in-kernel battery charger management that
8 requires temperature monitoring during suspend-to-RAM state
12 Charger Manager is a platform_driver with power-supply-class entries.
13 An instance of Charger Manager (a platform-device created with Charger-Manager)
15 batteries with their own chargers acting independently in a system,
26 own power-supply-class and each power-supply-class can provide
28 aggregates charger-related information from multiple sources and
29 shows combined information as a single power-supply-class.
31 * Support for in suspend-to-RAM polling (with suspend_again callback)
32 While the battery is being charged and the system is in suspend-to-RAM,
[all …]
/Documentation/devicetree/bindings/usb/
Ddwc2.txt2 -----------------------------------------------------
5 - compatible : One of:
6 - brcm,bcm2835-usb: The DWC2 USB controller instance in the BCM2835 SoC.
7 - hisilicon,hi6220-usb: The DWC2 USB controller instance in the hi6220 SoC.
8 - rockchip,rk3066-usb: The DWC2 USB controller instance in the rk3066 Soc;
9 - "rockchip,px30-usb", "rockchip,rk3066-usb", "snps,dwc2": for px30 Soc;
10 - "rockchip,rk3188-usb", "rockchip,rk3066-usb", "snps,dwc2": for rk3188 Soc;
11 - "rockchip,rk3288-usb", "rockchip,rk3066-usb", "snps,dwc2": for rk3288 Soc;
12 - "lantiq,arx100-usb": The DWC2 USB controller instance in Lantiq ARX SoCs;
13 - "lantiq,xrx200-usb": The DWC2 USB controller instance in Lantiq XRX SoCs;
[all …]
/Documentation/devicetree/bindings/sound/
Dda7218.txt8 - compatible : Should be "dlg,da7217" or "dlg,da7218"
9 - reg: Specifies the I2C slave address
11 - VDD-supply: VDD power supply for the device
12 - VDDMIC-supply: VDDMIC power supply for the device
13 - VDDIO-supply: VDDIO power supply for the device
14 (See Documentation/devicetree/bindings/regulator/regulator.txt for further
18 - interrupts: IRQ line info for DA7218 chip.
19 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt for
21 - interrupt-names : Name associated with interrupt line. Should be "wakeup" if
23 - wakeup-source: Flag to indicate this device can wake system (suspend/resume).
[all …]
/Documentation/driver-api/driver-model/
Ddriver.rst12 be multiple devices in a system that a driver supports, struct
29 driver. This declaration is hypothetical only; it relies on the driver
38 .suspend = eepro100_suspend,
43 model because the bus they belong to has a bus-specific structure with
44 bus-specific fields that cannot be generalized.
49 completely bus-specific. Defining them as bus-specific entities would
50 sacrifice type-safety, so we keep bus-specific structures around.
52 Bus-specific drivers should include a generic struct device_driver in
53 the definition of the bus-specific driver. Like this::
60 A definition that included bus-specific fields would look like
[all …]
/Documentation/devicetree/bindings/opp/
Dopp.txt2 ----------------------------------------------------
4 Devices work at voltage-current-frequency combinations and some implementations
13 Binding 1: operating-points
16 This binding only supports voltage-frequency pairs.
19 - operating-points: An array of 2-tuples items, and each item consists
20 of frequency and voltage like <freq-kHz vol-uV>.
21 freq: clock frequency in kHz
22 vol: voltage in microvolt
27 compatible = "arm,cortex-a9";
29 next-level-cache = <&L2>;
[all …]
/Documentation/sound/soc/
Ddapm.rst11 such, can easily co-exist with the other PM systems.
28 Usually controlled at codec probe/remove and suspend/resume, although
60 Audio DAPM widgets fall into a number of types:-
88 Regulator
89 External regulator that supplies power to audio components.
92 AIF IN
98 DAI IN
127 (Widgets are defined in include/sound/soc-dapm.h)
130 There are convenience macros defined in soc-dapm.h that can be used to quickly
138 ---------------------
[all …]
/Documentation/admin-guide/laptops/
Dthinkpad-acpi.rst9 - Borislav Deianov <borislav@users.sf.net>
10 - Henrique de Moraes Holschuh <hmh@hmh.eng.br>
12 http://ibm-acpi.sf.net/
19 This driver used to be named ibm-acpi until kernel 2.6.21 and release
20 0.13-20070314. It used to be in the drivers/acpi tree, but it was
21 moved to the drivers/misc tree and renamed to thinkpad-acpi for kernel
25 The driver is named "thinkpad-acpi". In some places, like module
29 "tpacpi" is used as a shorthand where "thinkpad-acpi" would be too
30 long due to length limitations on some Linux kernel versions.
33 ------
[all …]