Searched +full:regulator +full:- +full:system +full:- +full:load (Results 1 – 10 of 10) sorted by relevance
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/regulator/regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Liam Girdwood <lgirdwood@gmail.com>
11 - Mark Brown <broonie@kernel.org>
14 regulator-name:
15 description: A string used as a descriptive name for regulator outputs
18 regulator-min-microvolt:
21 regulator-max-microvolt:
[all …]
|
| /Documentation/power/regulator/ |
| D | consumer.rst | 2 Regulator Consumer Driver Interface
5 This text describes the regulator interface for consumer device drivers.
9 1. Consumer Regulator Access (static & dynamic drivers)
12 A consumer driver can get access to its supply regulator by calling ::
14 regulator = regulator_get(dev, "Vcc");
17 then finds the correct regulator by consulting a machine specific lookup table.
19 regulator that supplies this consumer.
21 To release the regulator the consumer driver should call ::
23 regulator_put(regulator);
25 Consumers can be supplied by more than one regulator e.g. codec consumer with
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 1 What: /sys/class/regulator/.../state
6 Some regulator directories will contain a field called
7 state. This reports the regulator enable control, for
16 'enabled' means the regulator output is ON and is supplying
17 power to the system (assuming no error prevents it).
19 'disabled' means the regulator output is OFF and is not
20 supplying power to the system (unless some non-Linux
27 or microamps to determine configured regulator output levels.
30 What: /sys/class/regulator/.../status
32 Some regulator directories will contain a field called
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | ti,twl.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Andreas Kemnade <andreas@kemnade.info>
19 - if:
26 "^regulator-":
30 - ti,twl4030-vaux1
31 - ti,twl4030-vaux2
32 - ti,twl4030-vaux3
33 - ti,twl4030-vaux4
[all …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | wkup-m3-ipc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/ti/wkup-m3-ipc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Dave Gerlach <d-gerlach@ti.com>
11 - Drew Fustini <dfustini@baylibre.com>
14 The TI AM33xx and AM43xx family of devices use a small Cortex M3 co-processor
17 C-states for CPU Idle. Once the wkup_m3_ipc driver uses the wkup_m3_rproc driver
29 On some boards like the AM335x EVM-SK and the AM437x GP EVM, a GPIO pin is
30 connected to the enable pin on the DDR VTT regulator. This allows the
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l36.txt | 5 - compatible : "cirrus,cs35l36"
7 - reg : the I2C address of the device for I2C
9 - VA-supply, VP-supply : power supplies for the device,
11 Documentation/devicetree/bindings/regulator/regulator.txt.
13 - cirrus,boost-ctl-millivolt : Boost Voltage Value. Configures the boost
18 - cirrus,boost-peak-milliamp : Boost-converter peak current limit in mA.
24 - cirrus,boost-ind-nanohenry : Inductor estimation LBST reference value.
32 - cirrus,multi-amp-mode : Boolean to determine if there are more than
33 one amplifier in the system. If more than one it is best to Hi-Z the ASP
36 - cirrus,boost-ctl-select : Boost converter control source selection.
[all …]
|
| /Documentation/hwmon/ |
| D | ltc2978.rst | 10 Addresses scanned: -
18 Addresses scanned: -
26 Addresses scanned: -
34 Addresses scanned: -
42 Addresses scanned: -
52 Addresses scanned: -
60 Addresses scanned: -
68 Addresses scanned: -
76 Addresses scanned: -
84 Addresses scanned: -
[all …]
|
| /Documentation/arch/arm64/ |
| D | arm-acpi.rst | 6 the BSA (Arm Base System Architecture) [0] and BBR (Arm
10 of rules defined in SBSA (Server Base System Architecture) [2].
18 If an Arm system does not meet the requirements of the BSA and BBR,
23 industry-standard Arm systems, they also apply to more than one operating
24 system. The purpose of this document is to describe the interaction between
25 ACPI and Linux only, on an Arm system -- that is, what Linux expects of
30 ----------------
33 exist in Linux for describing non-enumerable hardware, after all. In this
40 - ACPI’s byte code (AML) allows the platform to encode hardware behavior,
43 system releases on new hardware.
[all …]
|
| /Documentation/driver-api/ |
| D | pin-control.rst | 9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up, pull-down, open drain,
15 load capacitance etc.
17 Top-level interface
22 - A PIN CONTROLLER is a piece of hardware, usually a set of registers, that
23 can control PINs. It may be able to multiplex, bias, set load capacitance,
26 - PINS are equal to pads, fingers, balls or whatever packaging input or
29 there may be several such number spaces in a system. This pin space may
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
41 If set to vendor, prefer vendor-specific driver
73 Documentation/firmware-guide/acpi/debug.rst for more information about
[all …]
|