Searched +full:range +full:- +full:microvolt (Results 1 – 25 of 248) sorted by relevance
12345678910
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/dac/ |
| D | adi,ad3552r.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Nuno Sá <nuno.sa@analog.com>
16 https://www.analog.com/media/en/technical-documentation/data-sheets/ad3542r.pdf
17 https://www.analog.com/media/en/technical-documentation/data-sheets/ad3552r.pdf
22 - adi,ad3542r
23 - adi,ad3552r
28 spi-max-frequency:
31 reset-gpios:
[all …]
|
| D | adi,ad5758.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michael Hennerich <Michael.Hennerich@analog.com>
19 spi-cpha: true
21 adi,dc-dc-mode:
25 Mode of operation of the dc-to-dc converter
32 In this mode, the VDPC+ voltage is user-programmable to a fixed level
47 adi,range-microvolt:
49 Voltage output range specified as <minimum, maximum>
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/ |
| D | battery.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
14 In smart batteries, these are typically stored in non-volatile memory
16 no appropriate non-volatile memory, or it is unprogrammed/incorrect.
27 Batteries must be referenced by chargers and/or fuel-gauges using a phandle.
28 The phandle's property should be named "monitored-battery".
32 const: simple-battery
34 over-voltage-threshold-microvolt:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/power/supply/ |
| D | battery.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Sebastian Reichel <sre@kernel.org>
14 In smart batteries, these are typically stored in non-volatile memory
16 no appropriate non-volatile memory, or it is unprogrammed/incorrect.
27 Batteries must be referenced by chargers and/or fuel-gauges using a phandle.
28 The phandle's property should be named "monitored-battery".
32 const: simple-battery
34 device-chemistry:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/regulator/ |
| D | pwm-regulator.yaml | 1 # 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#
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
21 Intermediary duty-cycle values which would normally allow finer grained
23 is given to the user if the assumptions made in continuous-voltage mode do
[all …]
|
| D | vctrl.txt | 5 --------------------
6 - compatible : must be "vctrl-regulator".
7 - regulator-min-microvolt : smallest voltage consumers may set
8 - regulator-max-microvolt : largest voltage consumers may set
9 - ctrl-supply : The regulator supplying the control voltage.
10 - ctrl-voltage-range : an array of two integer values describing the range
13 regulator-min/max-microvolt output voltage.
16 --------------------
17 - ovp-threshold-percent : overvoltage protection (OVP) threshold of the
28 - min-slew-down-rate : Describes how slowly the regulator voltage will decay
[all …]
|
| D | palmas-pmic.txt | 11 - compatible : Should be from the list
12 ti,twl6035-pmic
13 ti,twl6036-pmic
14 ti,twl6037-pmic
15 ti,tps65913-pmic
16 ti,tps65914-pmic
17 ti,tps65917-pmic
18 ti,tps659038-pmic
20 ti,palmas-pmic
21 - interrupts : The interrupt number and the type which can be looked up here:
[all …]
|
| D | nvidia,tegra-regulators-coupling.txt | 4 NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators.
9 ------------------------
12 The CORE and RTC voltages shall be in a range of 170mV from each other
16 ------------------------
19 and CPU voltages shall be in a range of 300mV from each other and CORE
24 - nvidia,tegra-core-regulator: Boolean property that designates regulator
26 - nvidia,tegra-rtc-regulator: Boolean property that designates regulator
28 - nvidia,tegra-cpu-regulator: Boolean property that designates regulator
36 regulator-name = "vdd_core";
37 regulator-min-microvolt = <950000>;
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/ |
| D | pwm-regulator.txt | 7 predefined voltage <=> duty-cycle values must be
10 Intermediary duty-cycle values which would normally
13 the user if the assumptions made in continuous-voltage
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
27 --------------------
28 - compatible: Should be "pwm-regulator"
30 - pwms: PWM specification (See: ../pwm/pwm.txt)
[all …]
|
| D | vctrl.txt | 5 --------------------
6 - compatible : must be "vctrl-regulator".
7 - regulator-min-microvolt : smallest voltage consumers may set
8 - regulator-max-microvolt : largest voltage consumers may set
9 - ctrl-supply : The regulator supplying the control voltage.
10 - ctrl-voltage-range : an array of two integer values describing the range
13 regulator-min/max-microvolt output voltage.
16 --------------------
17 - ovp-threshold-percent : overvoltage protection (OVP) threshold of the
28 - min-slew-down-rate : Describes how slowly the regulator voltage will decay
[all …]
|
| D | palmas-pmic.txt | 11 - compatible : Should be from the list
12 ti,twl6035-pmic
13 ti,twl6036-pmic
14 ti,twl6037-pmic
15 ti,tps65913-pmic
16 ti,tps65914-pmic
17 ti,tps65917-pmic
18 ti,tps659038-pmic
20 ti,palmas-pmic
21 - interrupts : The interrupt number and the type which can be looked up here:
[all …]
|
| D | nvidia,tegra-regulators-coupling.txt | 4 NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators.
9 ------------------------
12 The CORE and RTC voltages shall be in a range of 170mV from each other
16 ------------------------
19 and CPU voltages shall be in a range of 300mV from each other and CORE
24 - nvidia,tegra-core-regulator: Boolean property that designates regulator
26 - nvidia,tegra-rtc-regulator: Boolean property that designates regulator
28 - nvidia,tegra-cpu-regulator: Boolean property that designates regulator
36 regulator-name = "vdd_core";
37 regulator-min-microvolt = <950000>;
[all …]
|
| D | max77686.txt | 3 This is a part of the device tree bindings of MAX77686 multi-function device.
6 The MAX77686 PMIC has 9 high-efficiency Buck and 26 Low-DropOut (LDO)
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
24 -LDOn : for LDOs, where n can lie in range 1 to 26.
26 -BUCKn : for BUCKs, where n can lie in range 1 to 9.
30 -LDOn : 2, 6-8, 10-12, 14-16,
31 -BUCKn : 1-4.
32 Use standard regulator bindings for it ('regulator-off-in-suspend').
[all …]
|
| D | max8952.txt | 4 - compatible: must be equal to "maxim,max8952"
5 - reg: I2C slave address, usually 0x60
6 - max8952,dvs-mode-microvolt: array of 4 integer values defining DVS voltages
7 in microvolts. All values must be from range <770000, 1400000>
8 - any required generic properties defined in regulator.txt
11 - max8952,vid-gpios: array of two GPIO pins used for DVS voltage selection
12 - max8952,en-gpio: GPIO used to control enable status of regulator
13 - max8952,default-mode: index of default DVS voltage, from <0, 3> range
14 - max8952,sync-freq: sync frequency, must be one of following values:
15 - 0: 26 MHz
[all …]
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru-kevin.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Google Gru-Kevin Rev 6+ board device tree source
5 * Copyright 2016-2017 Google, Inc
8 /dts-v1/;
9 #include "rk3399-gru-chromebook.dtsi"
10 #include <dt-bindings/input/linux-event-codes.h>
13 * Kevin-specific things
21 compatible = "google,kevin-rev15", "google,kevin-rev14",
22 "google,kevin-rev13", "google,kevin-rev12",
23 "google,kevin-rev11", "google,kevin-rev10",
[all …]
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/rockchip/ |
| D | rk3399-gru-kevin.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
3 * Google Gru-Kevin Rev 6+ board device tree source
5 * Copyright 2016-2017 Google, Inc
8 /dts-v1/;
9 #include "rk3399-gru-chromebook.dtsi"
10 #include <dt-bindings/input/linux-event-codes.h>
13 * Kevin-specific things
21 compatible = "google,kevin-rev15", "google,kevin-rev14",
22 "google,kevin-rev13", "google,kevin-rev12",
23 "google,kevin-rev11", "google,kevin-rev10",
[all …]
|
| D | rk3399-gru.dtsi | 1 // 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
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
41 ppvar_sys: ppvar-sys {
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwmon/ |
| D | ti,tmp513.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Eric Tremblay <etremblay@distech-controls.com>
14 The TMP512 (dual-channel) and TMP513 (triple-channel) are system monitors
15 that include remote sensors, a local temperature sensor, and a high-side
17 remote temperatures, on-chip temperatures, and system voltage/power/current
28 - ti,tmp512
29 - ti,tmp513
34 shunt-resistor-micro-ohms:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/hwmon/ |
| D | ti,tmp513.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Eric Tremblay <etremblay@distech-controls.com>
14 The TMP512 (dual-channel) and TMP513 (triple-channel) are system monitors
15 that include remote sensors, a local temperature sensor, and a high-side
17 remote temperatures, on-chip temperatures, and system voltage/power/current
28 - ti,tmp512
29 - ti,tmp513
34 shunt-resistor-micro-ohms:
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/amlogic/ |
| D | meson8b-mxq.dts | 1 // 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-5.10/arch/arm/boot/dts/ |
| D | meson8b-mxq.dts | 1 // 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 …]
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/amlogic/ |
| D | meson-g12b-odroid-go-ultra.dts | 1 // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
6 /dts-v1/;
8 #include "meson-g12b-s922x.dtsi"
9 #include <dt-bindings/input/input.h>
10 #include <dt-bindings/leds/common.h>
11 #include <dt-bindings/gpio/meson-g12a-gpio.h>
12 #include <dt-bindings/sound/meson-g12a-toacodec.h>
13 #include <dt-bindings/sound/meson-g12a-tohdmitx.h>
16 compatible = "hardkernel,odroid-go-ultra", "amlogic,s922x", "amlogic,g12b";
17 model = "Hardkernel ODROID-GO-Ultra";
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | ti-lmu.txt | 6 ------ ---------------------------------
14 - compatible: Should be one of:
20 - reg: I2C slave address.
28 - enable-gpios: A GPIO specifier for hardware enable pin.
29 - ramp-up-us: Current ramping from one brightness level to
31 Range from 2048 us - 117.44 s
32 - ramp-down-us: Current ramping from one brightness level to
34 Range from 2048 us - 117.44 s
35 - ti,brightness-resolution - This determines whether to use 8 bit brightness
47 - backlight: All LMU devices have backlight child nodes.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mfd/ |
| D | ti-lmu.txt | 6 ------ ---------------------------------
14 - compatible: Should be one of:
20 - reg: I2C slave address.
28 - enable-gpios: A GPIO specifier for hardware enable pin.
29 - ramp-up-us: Current ramping from one brightness level to
31 Range from 2048 us - 117.44 s
32 - ramp-down-us: Current ramping from one brightness level to
34 Range from 2048 us - 117.44 s
35 - ti,brightness-resolution - This determines whether to use 8 bit brightness
47 - backlight: All LMU devices have backlight child nodes.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/dac/ |
| D | ad5758.txt | 4 - compatible: Must be "adi,ad5758"
5 - reg: SPI chip select number for the device
6 - spi-max-frequency: Max SPI frequency to use (< 50000000)
7 - spi-cpha: is the only mode that is supported
11 - adi,dc-dc-mode: Mode of operation of the dc-to-dc converter
19 In this mode, the VDPC+ voltage is user-programmable to
36 - adi,range-microvolt: Voltage output range
38 * <0 5000000>: 0 V to 5 V voltage range
39 * <0 10000000>: 0 V to 10 V voltage range
40 * <(-5000000) 5000000>: ±5 V voltage range
[all …]
|
12345678910