| /freebsd/sys/contrib/device-tree/Bindings/clock/ |
| H A D | nvidia,tegra124-dfll.txt | 4 Documentation/devicetree/bindings/clock/clock-bindings.txt 7 the fast CPU cluster. It consists of a free-running voltage controlled 8 oscillator connected to the CPU voltage rail (VDD_CPU), and a closed loop 9 control module that will automatically adjust the VDD_CPU voltage by 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. [all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/mfd/ |
| H A D | max8998.txt | 1 * Maxim MAX8998, National/TI LP3974 multi-function device 3 The Maxim MAX8998 is a multi-function device which includes voltage/current 5 other sub-blocks. It is interfaced using an I2C interface. Each sub-block 8 PMIC sub-block 9 -------------- 11 The PMIC sub-block contains a number of voltage and current regulators, 12 with controllable parameters and dynamic voltage scaling capability. 17 - compatible: Should be one of the following: 18 - "maxim,max8998" for Maxim MAX8998 19 - "national,lp3974" or "ti,lp3974" for National/TI LP3974. [all …]
|
| /freebsd/share/man/man4/ |
| H A D | ads111x.4 | 35 .Bd -ragged -offset indent 42 .Bd -literal -offset indent 58 utility provides access to the voltage measurements made by the device. 60 .Va dev.ads111x.<unit>.<channel>.voltage 64 in microvolts. 75 making either single-ended or differential measurements. 82 the voltage variable for the channel number that corresponds the mux 101 Sysctl variables are used to access the voltage measurements, and to 107 .Bl -tag -width indent 125 Because measurements are always made in single-shot mode, think of [all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/iio/adc/ |
| H A D | aspeed,ast2600-adc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/iio/adc/aspeed,ast2600-adc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Billy Tsai <billy_tsai@aspeedtech.com> 13 • 10-bits resolution for 16 voltage channels. 14 • The device split into two individual engine and each contains 8 voltage 16 • Channel scanning can be non-continuous. 21 • Built-in a compensating method. 22 • Built-in a register to trim internal reference voltage. [all …]
|
| H A D | adi,ad7949.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Charles-Antoine Couret <charles-antoine.couret@essensium.com> 15 https://www.analog.com/media/en/technical-documentation/data-sheets/AD7949.pdf 17 https://www.analog.com/media/en/technical-documentation/data-sheets/AD7682_7689.pdf 22 - adi,ad7682 23 - adi,ad7689 24 - adi,ad7949 29 vrefin-supply: [all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/regulator/ |
| H A D | max8952.txt | 1 Maxim MAX8952 voltage regulator 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: [all …]
|
| H A D | pwm-regulator.txt | 6 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 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> 17 Voltage Table: 18 When in this mode, a voltage table (See below) of predefined voltage <=> 19 duty-cycle values must be provided via DT. Limitations are that the [all …]
|
| H A D | maxim,max8952.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Maxim MAX8952 voltage regulator 10 - Krzysztof Kozlowski <krzk@kernel.org> 13 - $ref: regulator.yaml# 19 max8952,default-mode: 23 index of default DVS voltage 25 max8952,dvs-mode-microvolt: 32 Array of 4 integer values defining DVS voltages in microvolts. All values [all …]
|
| H A D | gpio-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/regulator/gpio-regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Liam Girdwood <lgirdwood@gmail.com> 11 - Mark Brown <broonie@kernel.org> 18 - $ref: regulator.yaml# 22 const: regulator-gpio 24 regulator-name: true 26 enable-gpios: [all …]
|
| H A D | regulator.yaml | 1 # 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 - Mar [all...] |
| /freebsd/sys/contrib/device-tree/Bindings/input/ |
| H A D | allwinner,sun4i-a10-lradc-keys.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/input/allwinner,sun4i-a10-lradc-keys.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Chen-Yu Tsai <wens@csie.org> 11 - Maxime Ripard <mripard@kernel.org> 16 - const: allwinner,sun4i-a10-lradc-keys 17 - const: allwinner,sun8i-a83t-r-lradc 18 - items: 19 - enum: [all …]
|
| /freebsd/share/man/man9/ |
| H A D | regulator.9 | 69 The regulator framework allow drivers to enable, disable and change regulator voltage. 75 .Bl -tag -width indent 98 If the regulator supports a voltage range, the one configured in the hardware will be the output vo… 115 .Bl -tag -width indent 122 Get the current voltage set for the regulator in microvolts. 124 Change the voltage for the regulator. 128 if the regulator doesn't support this voltage range. 130 Checks if the regulator support the given voltage. 133 if the regulator doesn't support this voltage range.
|
| /freebsd/sys/dev/iicbus/adc/ |
| H A D | ads111x.c | 1 /*- 2 * SPDX-License-Identifier: BSD-2-Clause 72 * On config write, the operational-state bit starts a measurement, on read it 79 * The default values for config items that are not per-channel. Mostly, this 90 * Per-channel defaults. The chip only has one control register, and we load 91 * per-channel values into it every time we make a measurement on that channel. 93 * values we maintain on a per-channel basis. 99 * Full-scale ranges for each available amplifier setting, in microvolts. The 100 * ADS1x13 chips are fixed-range, the other chips contain a programmable gain 111 #define ADS101x_RANGEDIV ((1 << 15) - 15) [all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/power/supply/ |
| H A 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 …]
|
| H A D | twl4030-charger.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/power/supply/twl4030-charger.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 14 value in explicit configuration in device-tree. Rather if there is a sibling 15 of the BCI node which is compatible with "ti,twl4030-usb", then that is used 19 - Sebastian Reichel <sre@kernel.org> 22 - $ref: power-supply.yaml# 26 const: ti,twl4030-bci 32 ti,bb-uvolt: [all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/usb/ |
| H A D | msm-hsusb.txt | 6 - compatible: Should contain "qcom,ehci-host" 7 - regs: offset and length of the register set in the memory map 8 - usb-phy: phandle for the PHY device 13 compatible = "qcom,ehci-host"; 15 usb-phy = <&usb_otg>; 21 - compatible: Should contain: 22 "qcom,usb-otg-c [all...] |
| /freebsd/sys/contrib/device-tree/src/arm64/nvidia/ |
| H A D | tegra210-p2371-2180.dts | 1 // SPDX-License-Identifier: GPL-2.0 2 /dts-v1/; 4 #include "tegra210-p2180.dtsi" 5 #include "tegra210-p2597.dtsi" 9 compatible = "nvidia,p2371-2180", "nvidia,tegra210"; 14 hvddio-pex-supply = <&vdd_1v8>; 15 dvddio-pe [all...] |
| H A D | tegra210-p3450-0000.dts | 1 // SPDX-License-Identifier: GPL-2.0 2 /dts-v1/; 4 #include <dt-bindings/input/gpio-keys.h> 5 #include <dt-bindings/input/linux-event-codes.h> 6 #include <dt-binding [all...] |