Home
last modified time | relevance | path

Searched +full:pwm +full:- +full:regulator (Results 1 – 25 of 987) sorted by relevance

12345678910>>...40

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/
Dpwm-regulator.txt1 Bindings for the Generic PWM Regulator
7 predefined voltage <=> duty-cycle values must be
8 provided via DT. Limitations are that the regulator can
10 Intermediary duty-cycle values which would normally
13 the user if the assumptions made in continuous-voltage
16 Continuous Voltage: This mode uses the regulator's maximum and minimum
18 regulator-{min,max}-microvolt properties to calculate
19 appropriate duty-cycle values. This allows for a much
21 voltage-table mode above. This solution does make an
22 assumption that a %50 duty-cycle value will cause the
[all …]
Dtps51632-regulator.txt4 - compatible: Must be "ti,tps51632"
5 - reg: I2C slave address
8 - ti,enable-pwm-dvfs: Enable the DVFS voltage control through the PWM interface.
9 - ti,dvfs-step-20mV: The 20mV step voltage when PWM DVFS enabled. Missing this
10 will set 10mV step voltage in PWM DVFS mode. In normal mode, the voltage
13 Any property defined as part of the core regulator binding, defined in
14 regulator.txt, can also be used.
21 regulator-name = "tps51632-vout";
22 regulator-min-microvolt = <500000>;
23 regulator-max-microvolt = <1500000>;
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/
Dpwm-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/pwm-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Generic PWM Regulator
10 - Brian Norris <briannorris@chromium.org>
11 - Lee Jones <lee@kernel.org>
12 - Alexandre Courbot <acourbot@nvidia.com>
19 duty-cycle values must be provided via DT. Limitations are that the
20 regulator can only operate at the voltages supplied in the table.
[all …]
Dtps51632-regulator.txt4 - compatible: Must be "ti,tps51632"
5 - reg: I2C slave address
8 - ti,enable-pwm-dvfs: Enable the DVFS voltage control through the PWM interface.
9 - ti,dvfs-step-20mV: The 20mV step voltage when PWM DVFS enabled. Missing this
10 will set 10mV step voltage in PWM DVFS mode. In normal mode, the voltage
13 Any property defined as part of the core regulator binding, defined in
14 regulator.txt, can also be used.
21 regulator-name = "tps51632-vout";
22 regulator-min-microvolt = <500000>;
23 regulator-max-microvolt = <1500000>;
[all …]
/kernel/linux/linux-6.6/drivers/regulator/
Dpwm-regulator.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Regulator driver for PWM Regulators
5 * Copyright (C) 2014 - STMicroelectronics Inc.
14 #include <linux/regulator/driver.h>
15 #include <linux/regulator/machine.h>
16 #include <linux/regulator/of_regulator.h>
18 #include <linux/pwm.h>
29 struct pwm_device *pwm; member
37 /* regulator descriptor */
52 * Voltage table call-backs
[all …]
/kernel/linux/linux-5.10/drivers/regulator/
Dpwm-regulator.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * Regulator driver for PWM Regulators
5 * Copyright (C) 2014 - STMicroelectronics Inc.
13 #include <linux/regulator/driver.h>
14 #include <linux/regulator/machine.h>
15 #include <linux/regulator/of_regulator.h>
18 #include <linux/pwm.h>
29 struct pwm_device *pwm; member
37 /* regulator descriptor */
52 * Voltage table call-backs
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/amlogic/
Dmeson-g12b-khadas-vim3.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
11 vddcpu_a: regulator-vddcpu-a {
13 * MP8756GD Regulator.
15 compatible = "pwm-regulator";
17 regulator-name = "VDDCPU_A";
18 regulator-min-microvolt = <690000>;
19 regulator-max-microvolt = <1050000>;
21 pwm-supply = <&dc_in>;
24 pwm-dutycycle-range = <100 0>;
26 regulator-boot-on;
[all …]
/kernel/linux/linux-6.6/arch/arm64/boot/dts/amlogic/
Dmeson-g12b-khadas-vim3.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
11 vddcpu_a: regulator-vddcpu-a {
13 * MP8756GD Regulator.
15 compatible = "pwm-regulator";
17 regulator-name = "VDDCPU_A";
18 regulator-min-microvolt = <690000>;
19 regulator-max-microvolt = <1050000>;
21 pwm-supply = <&dc_in>;
24 pwm-dutycycle-range = <100 0>;
26 regulator-boot-on;
[all …]
Dmeson-g12b-bananapi.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
8 #include <dt-bindings/input/input.h>
9 #include <dt-bindings/leds/common.h>
10 #include <dt-bindings/gpio/meson-g12a-gpio.h>
11 #include <dt-bindings/sound/meson-g12a-tohdmitx.h>
21 stdout-path = "serial0:115200n8";
29 adc-keys {
30 compatible = "adc-keys";
31 io-channels = <&saradc 2>;
32 io-channel-names = "buttons";
[all …]
/kernel/linux/linux-6.6/arch/arm64/boot/dts/qcom/
Dmsm8916-samsung-gt510.dts1 // SPDX-License-Identifier: GPL-2.0-only
3 /dts-v1/;
5 #include "msm8916-samsung-gt5-common.dtsi"
10 chassis-type = "tablet";
12 clk_pwm: pwm {
13 compatible = "clk-pwm";
14 #pwm-cells = <2>;
18 pinctrl-0 = <&motor_pwm_default>;
19 pinctrl-names = "default";
22 reg_motor_vdd: regulator-motor-vdd {
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/amlogic/
Dmeson8b-mxq.dts1 // SPDX-License-Identifier: GPL-2.0 OR MIT
7 /dts-v1/;
9 #include <dt-bindings/gpio/gpio.h>
22 stdout-path = "serial0:115200n8";
30 vcck: regulator-vcck {
31 compatible = "pwm-regulator";
33 regulator-name = "VCCK";
34 regulator-min-microvolt = <860000>;
35 regulator-max-microvolt = <1140000>;
37 pwm-supply = <&vcc_5v>;
[all …]
/kernel/linux/linux-6.6/arch/arm/boot/dts/ti/omap/
Dtwl6030.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/
12 interrupt-controller;
13 #interrupt-cells = <1>;
16 compatible = "ti,twl4030-rtc";
20 vaux1: regulator-vaux1 {
21 compatible = "ti,twl6030-vaux1";
22 regulator-min-microvolt = <1000000>;
23 regulator-max-microvolt = <3000000>;
26 vaux2: regulator-vaux2 {
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
Dtwl6030.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2011 Texas Instruments Incorporated - http://www.ti.com/
12 interrupt-controller;
13 #interrupt-cells = <1>;
16 compatible = "ti,twl4030-rtc";
20 vaux1: regulator-vaux1 {
21 compatible = "ti,twl6030-vaux1";
22 regulator-min-microvolt = <1000000>;
23 regulator-max-microvolt = <3000000>;
26 vaux2: regulator-vaux2 {
[all …]
Dmeson8b-mxq.dts1 // SPDX-License-Identifier: GPL-2.0 OR MIT
7 /dts-v1/;
9 #include <dt-bindings/gpio/gpio.h>
22 stdout-path = "serial0:115200n8";
30 iio-hwmon {
31 compatible = "iio-hwmon";
32 io-channels = <&saradc 8>;
35 vcck: regulator-vcck {
36 compatible = "pwm-regulator";
38 regulator-name = "VCCK";
[all …]
Dtegra20-colibri-iris.dts1 // SPDX-License-Identifier: GPL-2.0
2 /dts-v1/;
4 #include <dt-bindings/input/input.h>
5 #include "tegra20-colibri.dtsi"
9 compatible = "toradex,colibri_t20-iris", "toradex,colibri_t20",
22 stdout-path = "serial0:115200n8";
35 hdmi-supply = <&reg_5v0>;
41 bl-on {
49 hotplug-detect {
73 pwm-a-b {
[all …]
/kernel/linux/linux-6.6/Documentation/hwmon/
Dpwm-fan.rst1 Kernel driver pwm-fan
4 This driver enables the use of a PWM module to drive a fan. It uses the
5 generic PWM interface thus it is hardware independent. It can be used on
6 many SoCs, as long as the SoC supplies a PWM line driver that exposes
7 the generic PWM API.
12 -----------
15 a PWM output. It uses the generic PWM interface, thus it can be used with
27 0 -> disable pwm and regulator
28 1 -> enable pwm; if pwm==0, disable pwm, keep regulator enabled
29 2 -> enable pwm; if pwm==0, keep pwm and regulator enabled
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/zte/
Dzx296718-pcbox.dts5 * SPDX-License-Identifier: (GPL-2.0+ OR MIT)
8 /dts-v1/;
10 #include <dt-bindings/pwm/pwm.h>
14 compatible = "zte,zx296718-pcbox", "zte,zx296718";
17 stdout-path = "serial0:115200n8";
25 a53_vdd0v9: regulator-a53 {
26 compatible = "pwm-regulator";
27 pwms = <&pwm 3 1250 PWM_POLARITY_INVERTED>;
28 regulator-name = "A53_VDD0V9";
29 regulator-min-microvolt = <855000>;
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/rockchip/
Drk3399-gru-chromebook.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Google Gru-Chromebook shared properties
8 #include "rk3399-gru.dtsi"
11 pp900_ap: pp900-ap {
12 compatible = "regulator-fixed";
13 regulator-name = "pp900_ap";
16 regulator-always-on;
17 regulator-boot-on;
18 regulator-min-microvolt = <900000>;
19 regulator-max-microvolt = <900000>;
[all …]
Drk3399-gru.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
5 * Copyright 2016-2017 Google, Inc
8 #include <dt-bindings/input/input.h>
10 #include "rk3399-op1-opp.dtsi"
14 stdout-path = "serial2:115200n8";
23 * - Rails that only connect to the EC (or devices that the EC talks to)
25 * - Rails _are_ included if the rails go to the AP even if the AP
31 * view, though, we won't create a full fixed regulator. We'll just
34 * - The EC controls the enable and the EC always enables a rail as
36 * - The rails are actually connected to each other by a jumper and
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/
Dnvidia,tegra124-dfll.txt4 Documentation/devicetree/bindings/clock/clock-bindings.txt
7 the fast CPU cluster. It consists of a free-running voltage controlled
10 communicating with an off-chip PMIC either via an I2C bus or via PWM signals.
13 - compatible : should be one of:
14 - "nvidia,tegra124-dfll": for Tegra124
15 - "nvidia,tegra210-dfll": for Tegra210
16 - reg : Defines the following set of registers, in the order listed:
17 - registers for the DFLL control logic.
18 - registers for the I2C output logic.
19 - registers for the integrated I2C master controller.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/clock/
Dnvidia,tegra124-dfll.txt4 Documentation/devicetree/bindings/clock/clock-bindings.txt
7 the fast CPU cluster. It consists of a free-running voltage controlled
10 communicating with an off-chip PMIC either via an I2C bus or via PWM signals.
13 - compatible : should be one of:
14 - "nvidia,tegra124-dfll": for Tegra124
15 - "nvidia,tegra210-dfll": for Tegra210
16 - reg : Defines the following set of registers, in the order listed:
17 - registers for the DFLL control logic.
18 - registers for the I2C output logic.
19 - registers for the integrated I2C master controller.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dmax77693.txt1 Maxim MAX77693 multi-function device
4 - PMIC,
5 - CHARGER,
6 - LED,
7 - MUIC,
8 - HAPTIC
14 - compatible : Must be "maxim,max77693".
15 - reg : Specifies the i2c slave address of PMIC block.
16 - interrupts : This i2c device has an IRQ line connected to the main SoC.
19 - regulators : The regulators of max77693 have to be instantiated under subnode
[all …]
/kernel/linux/linux-6.6/drivers/input/misc/
Dmax8997_haptic.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * MAX8997-haptic controller driver
15 #include <linux/pwm.h>
17 #include <linux/mfd/max8997-private.h>
19 #include <linux/regulator/consumer.h>
36 struct regulator *regulator; member
44 struct pwm_device *pwm; member
60 if (chip->mode == MAX8997_EXTERNAL_MODE) { in max8997_haptic_set_duty_cycle()
61 unsigned int duty = chip->pwm_period * chip->level / 100; in max8997_haptic_set_duty_cycle()
62 ret = pwm_config(chip->pwm, duty, chip->pwm_period); in max8997_haptic_set_duty_cycle()
[all …]
/kernel/linux/linux-6.6/arch/arm64/boot/dts/rockchip/
Drk3399-gru.dtsi1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
5 * Copyright 2016-2017 Google, Inc
8 #include <dt-bindings/input/input.h>
10 #include "rk3399-op1-opp.dtsi"
19 stdout-path = "serial2:115200n8";
28 * - Rails that only connect to the EC (or devices that the EC talks to)
30 * - Rails _are_ included if the rails go to the AP even if the AP
36 * view, though, we won't create a full fixed regulator. We'll just
39 * - The EC controls the enable and the EC always enables a rail as
41 * - The rails are actually connected to each other by a jumper and
[all …]
/kernel/linux/linux-5.10/drivers/input/misc/
Dmax8997_haptic.c1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * MAX8997-haptic controller driver
15 #include <linux/pwm.h>
17 #include <linux/mfd/max8997-private.h>
19 #include <linux/regulator/consumer.h>
36 struct regulator *regulator; member
44 struct pwm_device *pwm; member
60 if (chip->mode == MAX8997_EXTERNAL_MODE) { in max8997_haptic_set_duty_cycle()
61 unsigned int duty = chip->pwm_period * chip->level / 100; in max8997_haptic_set_duty_cycle()
62 ret = pwm_config(chip->pwm, duty, chip->pwm_period); in max8997_haptic_set_duty_cycle()
[all …]

12345678910>>...40