Home
last modified time | relevance | path

Searched refs:regulators (Results 1 – 25 of 621) sorted by relevance

12345678910>>...25

/linux/Documentation/devicetree/bindings/regulator/
H A Dtps65217.txt1 TPS65217 family of regulators
6 - regulators: list of regulators provided by this controller, must be named
8 - regulators: This is the list of child nodes that specify the regulator
9 initialization data for defined regulators. Not all regulators for the given
11 using the standard binding for regulators found at
17 The valid names for regulators are:
20 Each regulator is defined using the standard binding for regulators.
28 regulators {
H A Dtps65023.txt1 TPS65023 family of regulators
9 - regulators: list of regulators provided by this controller, must be named
11 - regulators: This is the list of child nodes that specify the regulator
12 initialization data for defined regulators. The definition for each of
13 these nodes is defined using the standard binding for regulators found at
16 Each regulator is defined using the standard binding for regulators.
24 regulators {
H A Dtps65218.txt1 TPS65218 family of regulators
7 - List of regulators provided by this controller, must be named
10 initialization data for defined regulators. Not all regulators for the given
12 using the standard binding for regulators found at ./regulator.txt.
14 The valid names for regulators are:
17 Each regulator is defined using the standard binding for regulators.
H A D88pm800.txt6 - regulators: A node that houses a sub-node for each regulator within the
10 regulators; see regulator.txt.
12 The valid names for regulators are:
23 regulators {
H A Das3722-regulator.txt2 Name of the regulator subnode must be "regulators".
6 The input supply of regulators are the optional properties on the
7 regulator node. The AS3722 is having 7 DCDC step-down regulators as
9 regulators are provided through following properties:
23 - regulators : Must contain a sub-node per regulator from the list below.
49 regulators {
H A Dnvidia,tegra-regulators-coupling.txt4 NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators.
5 Thus on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30
11 On Tegra20 SoC's there are 3 coupled regulators: CORE, RTC and CPU.
18 On Tegra30 SoC's there are 2 coupled regulators: CORE and CPU. The CORE
34 regulators {
H A Dmt6380-regulator.txt3 All voltage regulators provided by the MT6380 PMIC are described as the
4 subnodes of the MT6380 regulators node. Each regulator is named according
6 of these nodes is defined using the standard binding for regulators at
9 The valid names for regulators are:
17 regulators {
H A Dhisilicon,hi655x-regulator.txt1 Hisilicon Hi655x Voltage regulators
11 The valid names for regulators are:
20 regulators {
H A Dlm363x-regulator.txt4 LM3631 has five regulators and LM3632 supports three regulators.
37 regulators {
79 regulators {
H A Dmax8907.txt14 - regulators: A node that houses a sub-node for each regulator within the
18 regulators; see regulator.txt.
24 The valid names for regulators are:
45 regulators {
H A Disl9305.txt7 - regulators: A node that houses a sub-node for each regulator within the
10 is defined by the standard binding for regulators; see regulator.txt.
30 regulators {
/linux/drivers/misc/lis3lv02d/
H A Dlis3lv02d_i2c.c35 ret = regulator_bulk_disable(ARRAY_SIZE(lis3->regulators), in lis3_reg_ctrl()
36 lis3->regulators); in lis3_reg_ctrl()
38 ret = regulator_bulk_enable(ARRAY_SIZE(lis3->regulators), in lis3_reg_ctrl()
39 lis3->regulators); in lis3_reg_ctrl()
140 lis3_dev.regulators[0].supply = reg_vdd; in lis3lv02d_i2c_probe()
141 lis3_dev.regulators[1].supply = reg_vdd_io; in lis3lv02d_i2c_probe()
143 ARRAY_SIZE(lis3_dev.regulators), in lis3lv02d_i2c_probe()
144 lis3_dev.regulators); in lis3lv02d_i2c_probe()
172 regulator_bulk_free(ARRAY_SIZE(lis3_dev.regulators), in lis3lv02d_i2c_probe()
173 lis3_dev.regulators); in lis3lv02d_i2c_probe()
[all …]
/linux/drivers/leds/
H A Dleds-aw2013.c65 struct regulator_bulk_data regulators[2]; member
109 ret = regulator_bulk_disable(ARRAY_SIZE(chip->regulators), in aw2013_chip_disable()
110 chip->regulators); in aw2013_chip_disable()
127 ret = regulator_bulk_enable(ARRAY_SIZE(chip->regulators), in aw2013_chip_enable()
128 chip->regulators); in aw2013_chip_enable()
359 chip->regulators[0].supply = "vcc"; in aw2013_probe()
360 chip->regulators[1].supply = "vio"; in aw2013_probe()
362 ARRAY_SIZE(chip->regulators), in aw2013_probe()
363 chip->regulators); in aw2013_probe()
371 ret = regulator_bulk_enable(ARRAY_SIZE(chip->regulators), in aw2013_probe()
[all …]
/linux/drivers/regulator/
H A Dwm8400-regulator.c115 static const struct regulator_desc regulators[] = { variable
204 struct wm8400 *wm8400 = container_of(pdev, struct wm8400, regulators[pdev->id]); in wm8400_regulator_probe()
213 rdev = devm_regulator_register(&pdev->dev, &regulators[pdev->id], in wm8400_regulator_probe()
247 if (wm8400->regulators[reg].name) in wm8400_register_regulator()
252 wm8400->regulators[reg].name = "wm8400-regulator"; in wm8400_register_regulator()
253 wm8400->regulators[reg].id = reg; in wm8400_register_regulator()
254 wm8400->regulators[reg].dev.parent = dev; in wm8400_register_regulator()
255 wm8400->regulators[reg].dev.platform_data = initdata; in wm8400_register_regulator()
257 return platform_device_register(&wm8400->regulators[reg]); in wm8400_register_regulator()
H A Drn5t618-regulator.c104 const struct regulator_desc *regulators; in rn5t618_regulator_probe() local
110 regulators = rn5t567_regulators; in rn5t618_regulator_probe()
114 regulators = rn5t618_regulators; in rn5t618_regulator_probe()
118 regulators = rc5t619_regulators; in rn5t618_regulator_probe()
130 &regulators[i], in rn5t618_regulator_probe()
134 regulators[i].name); in rn5t618_regulator_probe()
H A Dda9062-regulator.c891 struct da9062_regulators *regulators = data; in da9062_ldo_lim_event() local
892 struct da9062 *hw = regulators->regulator[0].hw; in da9062_ldo_lim_event()
904 for (i = regulators->n_regulators - 1; i >= 0; i--) { in da9062_ldo_lim_event()
905 regl = &regulators->regulator[i]; in da9062_ldo_lim_event()
923 struct da9062_regulators *regulators; in da9062_regulator_probe() local
945 regulators = devm_kzalloc(&pdev->dev, struct_size(regulators, regulator, in da9062_regulator_probe()
947 if (!regulators) in da9062_regulator_probe()
950 regulators->n_regulators = max_regulators; in da9062_regulator_probe()
951 platform_set_drvdata(pdev, regulators); in da9062_regulator_probe()
953 for (n = 0; n < regulators->n_regulators; n++) { in da9062_regulator_probe()
[all …]
/linux/Documentation/devicetree/bindings/mfd/
H A Dtps6507x.txt6 - regulators: This is the list of child nodes that specify the regulator
7 initialization data for defined regulators. Not all regulators for the
9 is defined using the standard binding for regulators found at
16 These entries are required if regulators are enabled for a device.
28 - defdcdc_default: It's property of DCDC2 and DCDC3 regulators.
43 regulators {
H A Dwm831x.txt34 - regulators : Contains sub-nodes for each of the regulators supplied by
35 the device. The regulators are bound using their names listed below:
69 regulators {
/linux/arch/arm/boot/dts/qcom/
H A Dqcom-msm8660-surf.dts69 regulators-0 {
70 compatible = "qcom,rpm-pm8901-regulators";
73 regulators-1 {
74 compatible = "qcom,rpm-pm8058-regulators";
/linux/arch/arm64/boot/dts/qcom/
H A Dipq6018-mp5496.dtsi3 * ipq6018-mp5496.dtsi describes common properties (e.g. regulators) that
26 regulators {
27 compatible = "qcom,rpm-mp5496-regulators";
H A Dmsm8916-pm8916.dtsi5 * Many regulators have a fixed purpose in the original reference design and
64 pm8916_rpm_regulators: regulators {
65 compatible = "qcom,rpm-pm8916-regulators";
85 * Some of the regulators are unused or managed by another
88 * dropped in case the regulators are already on during boot.
/linux/Documentation/driver-api/
H A Dregulator.rst18 control voltage and current regulators.
22 both voltage regulators (where voltage output is controllable) and
36 Electronic device that supplies power to other devices. Most regulators
54 An IC which contains numerous regulators and often also other
64 regulators. Functions are provided to `enable <#API-regulator-enable>`__
68 When requesting regulators consumers use symbolic names for their
79 regulators. Consumer devices use the :c:func:`regulator_enable()` and
81 regulators. Calls to the two functions must be balanced.
114 Drivers for regulator chips register the regulators with the regulator
125 This interface provides a way to define how regulators are connected to
/linux/drivers/mfd/
H A Drohm-bd9576.c138 struct mfd_cell *regulators; in bd957x_i2c_probe() local
140 regulators = &bd9576_mfd_cells[BD957X_REGULATOR_CELL]; in bd957x_i2c_probe()
141 regulators->resources = bd9576_regulator_irqs; in bd957x_i2c_probe()
142 regulators->num_resources = ARRAY_SIZE(bd9576_regulator_irqs); in bd957x_i2c_probe()
/linux/drivers/soc/tegra/
H A DMakefile8 obj-$(CONFIG_SOC_TEGRA20_VOLTAGE_COUPLER) += regulators-tegra20.o
9 obj-$(CONFIG_SOC_TEGRA30_VOLTAGE_COUPLER) += regulators-tegra30.o
/linux/Documentation/power/regulator/
H A Doverview.rst9 voltage and current regulators.
13 regulators (where voltage output is controllable) and current sinks (where
28 Most regulators can enable and disable their output while
36 regulators and often contains other subsystems.
75 A power domain may have regulators that are supplied power
76 by other regulators. i.e.::
82 This gives us two regulators and two power domains:
155 This allows regulator drivers to register their regulators and provide
167 allows the creation of a regulator tree whereby some regulators are

12345678910>>...25