Home
last modified time | relevance | path

Searched +full:voltage +full:- +full:microvolt (Results 1 – 25 of 572) sorted by relevance

12345678910>>...23

/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/regulator/
H A Dltc3589.txt1 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,
13 nodes for sw1, sw2, sw3, bb-out, ldo1, and ldo2 additionally need to specify
14 the resistor values of their external feedback voltage dividers:
17 - lltc,fb-voltage-divider: An array of two integers containing the resistor
18 values R1 and R2 of the feedback voltage divider in ohms.
21 0.3625 V to 0.75 V in 12.5 mV steps. The output voltage thus ranges between
22 0.3625 * (1 + R1/R2) V and 0.75 * (1 + R1/R2) V. Regulators bb-out and ldo1
[all …]
H A Dltc3676.txt1 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,
14 the resistor values of their external feedback voltage dividers:
17 - lltc,fb-voltage-divider: An array of two integers containing the resistor
18 values R1 and R2 of the feedback voltage divider in ohms.
21 412.5mV to 800mV in 12.5 mV steps. The output voltage thus ranges between
26 regulator can not be disabled and thus should have the regulator-always-on
37 regulator-min-microvolt = <674400>;
[all …]
H A Dnxp,pca9450-regulator.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/regulator/nxp,pca9450-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Robin Gong <yibin.gong@nxp.com>
18 https://www.nxp.com/docs/en/data-sheet/PCA9450DS.pdf
28 - nxp,pca9450a
29 - nxp,pca9450b
30 - nxp,pca9450c
44 "^LDO[1-5]$":
[all …]
H A Dpwm-regulator.txt6 Voltage Table: When in this mode, a voltage table (See below) of
7 predefined voltage <=> duty-cycle values must be
10 Intermediary duty-cycle values which would normally
11 allow finer grained voltage selection are ignored and
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 …]
H A Dregulator.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Voltage/Current Regulators
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
14 regulator-name:
18 regulator-min-microvolt:
19 description: smallest voltage consumers may set
21 regulator-max-microvolt:
[all …]
H A Dvctrl.txt1 Bindings for Voltage controlled regulators
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
11 (min/max) of the control voltage. The values specify
12 the control voltage needed to generate the corresponding
13 regulator-min/max-microvolt output voltage.
[all …]
H A Dsamsung,s5m8767.txt4 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.
10 a sub-node named "regulators" with more sub-nodes for each regulator using the
12 - Documentation/devicetree/bindings/regulator/regulator.txt
16 - s5m8767,pmic-buck-ds-gpios: GPIO specifiers for three host gpio's used
17 for selecting GPIO DVS lines. It is one-to-one mapped to dvs gpio lines.
19 [1] If either of the 's5m8767,pmic-buck[2/3/4]-uses-gpio-dvs' optional
20 property is specified, then all the eight voltage values for the
21 's5m8767,pmic-buck[2/3/4]-dvs-voltage' should be specified.
24 - s5m8767,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
[all …]
H A Dnvidia,tegra-regulators-coupling.txt4 NVIDIA Tegra SoC's have a mandatory voltage-coupling between regulators.
8 Tegra20 voltage coupling
9 ------------------------
13 and they both shall be higher than the CPU voltage by at least 120mV.
15 Tegra30 voltage coupling
16 ------------------------
20 voltage shall be higher than the CPU by N mV, where N depends on the CPU
21 voltage.
24 - nvidia,tegra-core-regulator: Boolean property that designates regulator
25 as the "Core domain" voltage regulator.
[all …]
H A Dmax8997-regulator.txt1 * Maxim MAX8997 Voltage and Current Regulator
3 The Maxim MAX8997 is a multi-function device which includes voltage and
4 current regulators, rtc, charger controller and other sub-blocks. It is
5 interfaced to the host controller using a i2c interface. Each sub-block is
7 describes the bindings for 'pmic' sub-block of max8997.
10 - compatible: Should be "maxim,max8997-pmic".
11 - reg: Specifies the i2c slave address of the pmic block. It should be 0x66.
13 - max8997,pmic-buck1-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
14 units for buck1 when changing voltage using gpio dvs. Refer to [1] below
17 - max8997,pmic-buck2-dvs-voltage: A set of 8 voltage values in micro-volt (uV)
[all …]
H A Drk860x-regulator.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/regulator/rk860x-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Rockchip Rk860x voltage regulator
10 - Elaine Zhang <zhangqing@rock-chips.com>
14 The RK860X is a step-down switching voltage regulator that
15 delivers a digitally programmable output from an input voltage supply
16 of 2.5V to 5.5V. The output voltage is programmed through an I2C interface.
19 - $ref: regulator.yaml#
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/power/supply/
H A Dbattery.yaml1 # 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 …]
H A Drohm,bd99954.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
11 - Markus Laine <markus.laine@fi.rohmeurope.com>
12 - Mikko Mutanen <mikko.mutanen@fi.rohmeurope.com>
15 The ROHM BD99954 is a Battery Management LSI for 1-4 cell Lithium-Ion
16 secondary battery intended to be used in space-constraint equipment such
18 provides a Dual-source Battery Charger, two port BC1.2 detection and a
29 # Curve (2) represents battery voltage.
[all …]
/OK3568_Linux_fs/kernel/include/soc/rockchip/
H A Drockchip_system_monitor.h1 /* SPDX-License-Identifier: (GPL-2.0+ OR MIT) */
29 int volt; /* Voltage in microvolt */
38 * struct temp_opp_table - System monitor device OPP description structure
40 * @volt: Target voltage in microvolt
41 * @mem_volt: Target voltage for memory in microvolt
42 * @low_temp_volt: Target voltage when low temperature, in microvolt
43 * @low_temp_mem_volt: Target voltage for memory when low temperature,
44 * in microvolt
45 * @max_volt: Maximum voltage in microvolt
46 * @max_mem_volt: Maximum voltage for memory in microvolt
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mfd/
H A Drohm,bd71837-pmic.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71837-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
13 BD71837MWV is programmable Power Management ICs for powering single-core,
14 dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is optimized for low
18 …/www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applica…
35 "#clock-cells":
48 # crucial regulators must have the regulator-always-on and regulator-boot-on
[all …]
H A Drohm,bd71847-pmic.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71847-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
14 single-core, dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is
18 …/www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applica…
19 …//www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-applic…
24 - rohm,bd71847
25 - rohm,bd71850
[all …]
/OK3568_Linux_fs/u-boot/drivers/input/
H A Dspl_adc_key.c4 * SPDX-License-Identifier: GPL-2.0+
34 const void *fdt_blob = gd->fdt_blob; in key_read()
37 int t, down_threshold = -1, up_threshold; in key_read()
39 int mV, cd, voltage = -1; in key_read() local
49 adc_node = fdt_node_offset_by_compatible(fdt_blob, 0, "adc-keys"); in key_read()
51 debug("No 'adc-keys' node, ret=%d\n", adc_node); in key_read()
55 ret = fdtdec_get_int_array(fdt_blob, adc_node, "io-channels", in key_read()
58 debug("Can't read 'io-channels', ret=%d\n", ret); in key_read()
63 "keyup-threshold-microvolt", -ENODATA); in key_read()
65 debug("Can't read 'keyup-threshold-microvolt'\n"); in key_read()
[all …]
H A Dadc_key.c4 * SPDX-License-Identifier: GPL-2.0+
14 int t, down_threshold = -1, up_threshold; in adc_key_ofdata_to_platdata()
16 u32 voltage, chn[2]; in adc_key_ofdata_to_platdata() local
21 return -ENXIO; in adc_key_ofdata_to_platdata()
23 uc_key->type = ADC_KEY; in adc_key_ofdata_to_platdata()
24 uc_key->name = dev_read_string(dev, "label"); in adc_key_ofdata_to_platdata()
26 "io-channels", chn, ARRAY_SIZE(chn)); in adc_key_ofdata_to_platdata()
28 printf("%s: read 'io-channels' failed, ret=%d\n", in adc_key_ofdata_to_platdata()
29 uc_key->name, ret); in adc_key_ofdata_to_platdata()
30 return -EINVAL; in adc_key_ofdata_to_platdata()
[all …]
/OK3568_Linux_fs/kernel/arch/arm64/boot/dts/freescale/
H A Dimx8mq-pico-pi.dts1 // SPDX-License-Identifier: GPL-2.0+
9 /dts-v1/;
12 #include <dt-bindings/interrupt-controller/irq.h>
15 model = "TechNexion PICO-PI-8M";
16 compatible = "technexion,pico-pi-imx8m", "fsl,imx8mq";
19 stdout-path = &uart1;
22 pmic_osc: clock-pmic {
23 compatible = "fixed-clock";
24 #clock-cells = <0>;
25 clock-frequency = <32768>;
[all …]
H A Dimx8mq-phanbell.dts1 // SPDX-License-Identifier: (GPL-2.0 OR MIT)
3 * Copyright 2017-2019 NXP
6 /dts-v1/;
9 #include <dt-bindings/interrupt-controller/irq.h>
13 compatible = "google,imx8mq-phanbell", "fsl,imx8mq";
16 stdout-path = &uart1;
24 pmic_osc: clock-pmic {
25 compatible = "fixed-clock";
26 #clock-cells = <0>;
27 clock-frequency = <32768>;
[all …]
/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/regulator/
H A Dmax77686.txt4 - drivers/power/pmic/max77686.c (as parent I/O device)
5 - drivers/power/regulator/max77686.c (for child regulators)
10 - doc/device-tree-bindings/pmic/max77686.txt
13 - voltage-regulators: required for the PMIC driver
16 - regulator-name: used for regulator uclass platform data '.name'
19 - regulator-min-microvolt: minimum allowed Voltage to set
20 - regulator-max-microvolt: minimum allowed Voltage to set
21 - regulator-always-on: regulator should be never disabled
22 - regulator-boot-on: regulator should be enabled by the bootloader
26 voltage-regulators {
[all …]
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A Dimx53-usbarmory.dts8 * This file is dual-licensed: you can use it either under the terms
47 /dts-v1/;
52 compatible = "inversepath,imx53-usbarmory", "fsl,imx53";
57 stdout-path = &uart1;
66 compatible = "gpio-leds";
67 pinctrl-names = "default";
68 pinctrl-0 = <&pinctrl_led>;
73 linux,default-trigger = "heartbeat";
83 operating-points = <
92 pinctrl-names = "default";
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/opp/
H A Dallwinner,sun50i-h6-operating-points.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/opp/allwinner,sun50i-h6-operating-points.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Chen-Yu Tsai <wens@csie.org>
11 - Maxime Ripard <mripard@kernel.org>
14 For some SoCs, the CPU frequency subset and voltage value of each
16 Voltage Scaling Tables defines the voltage and frequency value based
18 sun50i-cpufreq-nvmem driver reads the efuse value from the SoC to
23 const: allwinner,sun50i-h6-operating-points
[all …]
H A 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>.
22 vol: voltage in microvolt
27 compatible = "arm,cortex-a9";
29 next-level-cache = <&L2>;
30 operating-points = <
[all …]
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/cpufreq/
H A Dcpufreq-rockchip.txt6 with 'prop' information which is used to determine opp-microvolt-<name>
8 on operating-points-v2, but the driver can also create the "cpufreq-dt"
9 platform_device to compatibility with operating-points.
14 In 'operating-points-v2' table:
15 - rockchip,leakage-voltage-sel: The property is an array of 3-tuples items, and
16 each item consists of leakage and voltage selector like
17 <min-leakage max-leakage volt-selector>.
18 min-leakage: minimum leakage in mA, ranges from 1 to 254.
19 max-leakage: maximum leakage in mA, ranges from 1 to 254.
20 voltage-selector: a sequence number which is used to math
[all …]
/OK3568_Linux_fs/kernel/arch/arm64/boot/dts/qcom/
H A Dmsm8992-bullhead-rev-101.dts1 // SPDX-License-Identifier: GPL-2.0-only
7 /dts-v1/;
15 qcom,msm-id = <251 0>, <252 0>;
16 qcom,board-id = <0xb64 0>;
17 qcom,pmic-id = <0x10009 0x1000A 0x0 0x0>;
20 /delete-node/ psci;
27 stdout-path = "serial0:115200n8";
30 reserved-memory {
31 #address-cells = <2>;
32 #size-cells = <2>;
[all …]

12345678910>>...23