Searched +full:power +full:- +full:down (Results 1 – 25 of 312) sorted by relevance
12345678910>>...13
| /Documentation/devicetree/bindings/sound/ |
| D | st,sta350.txt | 7 - compatible: "st,sta350"
8 - reg: the I2C address of the device for I2C
9 - reset-gpios: a GPIO spec for the reset pin. If specified, it will be
12 - power-down-gpios: a GPIO spec for the power down pin. If specified,
16 - vdd-dig-supply: regulator spec, providing 3.3V
17 - vdd-pll-supply: regulator spec, providing 3.3V
18 - vcc-supply: regulator spec, providing 5V - 26V
22 - st,output-conf: number, Selects the output configuration:
23 0: 2-channel (full-bridge) power, 2-channel data-out
24 1: 2 (half-bridge). 1 (full-bridge) on-board power
[all …]
|
| D | cs35l33.txt | 5 - compatible : "cirrus,cs35l33"
7 - reg : the I2C address of the device for I2C
9 - VA-supply, VP-supply : power supplies for the device,
15 - reset-gpios : gpio used to reset the amplifier
17 - interrupts : IRQ line info CS35L33.
18 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
21 - cirrus,boost-ctl : Booster voltage use to supply the amp. If the value is
26 - cirrus,ramp-rate : On power up, it affects the time from when the power
27 up sequence begins to the time the audio reaches a full-scale output.
28 On power down, it affects the time from when the power-down sequence
[all …]
|
| D | st,sta32x.txt | 7 - compatible: "st,sta32x"
8 - reg: the I2C address of the device for I2C
9 - reset-gpios: a GPIO spec for the reset pin. If specified, it will be
12 - power-down-gpios: a GPIO spec for the power down pin. If specified,
16 - Vdda-supply: regulator spec, providing 3.3V
17 - Vdd3-supply: regulator spec, providing 3.3V
18 - Vcc-supply: regulator spec, providing 5V - 26V
22 - clocks, clock-names: Clock specifier for XTI input clock.
24 and disabled when it is removed. The 'clock-names' must be set to 'xti'.
26 - st,output-conf: number, Selects the output configuration:
[all …]
|
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 2 Cluster-wide Power-up/power-down race avoidance algorithm
16 ---------
20 power consumption and thermal dissipation.
29 cluster-level operations are only performed when it is truly safe to do
35 disabling those mechanisms may itself be a non-atomic operation (such as
38 power-down and power-up at the cluster level.
46 -----------
50 - DOWN
51 - COMING_UP
52 - UP
[all …]
|
| /Documentation/userspace-api/ |
| D | dcdbas.rst | 10 management interrupts and host control actions (system power cycle or
11 power off after OS shutdown) on certain Dell systems.
29 buffer must reside in 32-bit address space, and the physical address of the
55 to perform a power cycle or power off of the system after the OS has finished
56 shutting down. On some Dell systems, this host control feature requires that
57 a driver perform a SMI after the OS has finished shutting down.
60 to schedule the driver to perform a power cycle or power off host control
61 action after the system has finished shutting down:
67 Dell OpenManage performs the following steps to execute a power cycle or
68 power off host control action using this driver:
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | maxim,max77693.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 MAX77693 MicroUSB and Companion Power Management IC LEDs
10 - Krzysztof Kozlowski <krzk@kernel.org>
16 There are two LED outputs available - FLED1 and FLED2. Each of them can
26 const: maxim,max77693-led
28 maxim,boost-mode:
34 See LEDS_BOOST_* in include/dt-bindings/leds/common.h.
38 maxim,boost-mvout:
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-consumer-common.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/gpio/gpio-consumer-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Bartosz Golaszewski <brgl@bgdev.pl>
11 - Linus Walleij <linus.walleij@linaro.org>
20 enable-gpios:
25 reset-gpios:
27 GPIO (or GPIOs for power sequence) connected to the device reset pin
30 powerdown-gpios:
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-max77620.txt | 1 Pincontrol driver for MAX77620 Power management IC from Maxim Semiconductor.
6 Please refer file <devicetree/bindings/pinctrl/pinctrl-bindings.txt>
11 --------------------------
14 - pinctrl-names: A pinctrl state named per <pinctrl-bindings.txt>.
15 - pinctrl[0...n]: Properties to contain the phandle for pinctrl states per
16 <pinctrl-bindings.txt>.
19 sub-node have following properties:
22 ------------------
23 - pins: List of pins. Valid values of pins properties are:
27 -------------------
[all …]
|
| D | samsung,pinctrl-pins-cfg.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/samsung,pinctrl-pins-cfg.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung S3C/S5P/Exynos SoC pin controller - pins configuration
10 - Krzysztof Kozlowski <krzk@kernel.org>
11 - Sylwester Nawrocki <s.nawrocki@samsung.com>
12 - Tomasz Figa <tomasz.figa@gmail.com>
21 manual and these values are programmed as-is into the pin pull up/down and
22 driver strength register of the pin-controller.
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | rockchip,rk3399-dmc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/rockchip,rk3399-dmc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Brian Norris <briannorris@chromium.org>
15 - rockchip,rk3399-dmc
17 devfreq-events:
26 clock-names:
28 - const: dmc_clk
30 operating-points-v2: true
[all …]
|
| /Documentation/devicetree/bindings/mmc/ |
| D | nvidia,tegra20-sdhci.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mmc/nvidia,tegra20-sdhci.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
18 mmc-controller.yaml and the properties for the Tegra SDHCI controller.
23 - enum:
24 - nvidia,tegra20-sdhci
25 - nvidia,tegra30-sdhci
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | max77620.txt | 1 MAX77620 Power management IC from Maxim Semiconductor.
4 -------------------
5 - compatible: Must be one of
9 - reg: I2C device address.
12 -------------------
13 - interrupts: The interrupt on the parent the controller is
15 - interrupt-controller: Marks the device node as an interrupt controller.
16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells
17 variant of <../interrupt-controller/interrupts.txt>
19 are defined at dt-bindings/mfd/max77620.h.
[all …]
|
| D | stericsson,db8500-prcmu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/stericsson,db8500-prcmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ST-Ericsson DB8500 PRCMU - Power Reset and Control Management Unit
10 - Linus Walleij <linus.walleij@linaro.org>
13 The DB8500 Power Reset and Control Management Unit is an XP70 8-bit
14 microprocessor that is embedded in the always-on power domain of the
15 DB8500 SoCs to manage the low power states, powering up and down parts
20 pattern: '^prcmu@[0-9a-f]+$'
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | ti-phy.txt | 6 - compatible: Should be one of
7 "ti,control-phy-otghs" - if it has otghs_control mailbox register as on OMAP4.
8 "ti,control-phy-usb2" - if it has Power down bit in control_dev_conf register
10 "ti,control-phy-pipe3" - if it has DPLL and individual Rx & Tx power control
12 "ti,control-phy-pcie" - for pcie to support external clock for pcie and to
15 "ti,control-phy-usb2-dra7" - if it has power down register like USB2 PHY on
17 "ti,control-phy-usb2-am437" - if it has power down register like USB2 PHY on
19 - reg : register ranges as listed in the reg-names property
20 - reg-names: "otghs_control" for control-phy-otghs
21 "power", "pcie_pcs" and "control_sma" for control-phy-pcie
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | qcom,rpm-regulator.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/regulator/qcom,rpm-regulator.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
15 The regulator node houses sub-nodes for each regulator within the device.
16 Each sub-node is identified using the node's name, with valid values listed
28 l29, lvs1, lvs2, lvs3, lvs4, lvs5, lvs6, lvs7, usb-switch, hdmi-switch,
37 - Bjorn Andersson <andersson@kernel.org>
42 - qcom,rpm-pm8058-regulators
43 - qcom,rpm-pm8901-regulators
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | mediatek-dwmac.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/mediatek-dwmac.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Biao Huang <biao.huang@mediatek.com>
21 - mediatek,mt2712-gmac
22 - mediatek,mt8188-gmac
23 - mediatek,mt8195-gmac
25 - compatible
28 - $ref: snps,dwmac.yaml#
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | gemini-poweroff.txt | 1 * Device-Tree bindings for Cortina Systems Gemini Poweroff
4 deals with different ways to power the system down.
7 - compatible: should be "cortina,gemini-power-controller"
8 - reg: should contain the physical memory base and size
9 - interrupts: should contain the power management interrupt
13 power-controller@4b000000 {
14 compatible = "cortina,gemini-power-controller";
|
| D | regulator-poweroff.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/reset/regulator-poweroff.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Force-disable power regulator to turn the power off.
10 - Michael Klein <michael@fossekall.de>
13 When the power-off handler is called, a power regulator is disabled by
14 calling regulator_force_disable(). If the power is still on and the
19 const: regulator-poweroff
21 cpu-supply:
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-qat | 4 Contact: qat-linux@intel.com
11 * down: the device is down
14 It is possible to transition the device from up to down only
22 Contact: qat-linux@intel.com
46 is in the `down` state (see /sys/bus/pci/devices/<BDF>/qat/state)
56 # echo down > /sys/bus/pci/devices/<BDF>/qat/state
67 Contact: qat-linux@intel.com
69 the MAX power state.
70 If idle support is enabled the device will transition to the `MIN` power state when
71 idle, otherwise will stay in the MAX power state.
[all …]
|
| /Documentation/devicetree/bindings/iio/frequency/ |
| D | adi,adrf6780.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Antoniu Miclaus <antoniu.miclaus@analog.com>
21 - adi,adrf6780
26 spi-max-frequency:
34 clock-names:
36 - const: lo_in
38 clock-output-names:
41 adi,vga-buff-en:
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-etm.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/arm/arm,coresight-etm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Mathieu Poirier <mathieu.poirier@linaro.org>
11 - Mike Leach <mike.leach@linaro.org>
12 - Leo Yan <leo.yan@linaro.org>
13 - Suzuki K Poulose <suzuki.poulose@arm.com>
23 The Embedded Trace Macrocell (ETM) is a real-time trace module providing
31 - arm,coresight-etm3x
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | maxim,max77693.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/power/supply/maxim,max77693.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Maxim MAX77693 MicroUSB and Companion Power Management IC Charger
10 - Krzysztof Kozlowski <krzk@kernel.org>
21 const: maxim,max77693-charger
23 maxim,constant-microvolt:
28 Also vsys (system voltage) will be set to this value when DC power is
30 Valid values: 3650000 - 4400000, step by 25000 (rounded down)
[all …]
|
| /Documentation/sound/soc/ |
| D | overview.rst | 6 provide better ALSA support for embedded system-on-chip processors (e.g.
9 had some limitations:-
12 CPU. This is not ideal and leads to code duplication - for example,
18 machine specific code to re-route audio, enable amps, etc., after such an
21 * Drivers tended to power up the entire codec when playing (or
23 power on portable devices. There was also no support for saving
24 power via changing codec oversampling rates, bias currents, etc.
31 features :-
41 * Dynamic Audio Power Management (DAPM). DAPM automatically sets the codec to
42 its minimum power state at all times. This includes powering up/down
[all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 9 ------------
11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
13 debug module and it is mainly used for two modes: self-hosted debug and
16 explore debugging method which rely on self-hosted debug mode, this document
19 The debug module provides sample-based profiling extension, which can be used
21 every CPU has one dedicated debug module to be connected. Based on self-hosted
29 --------------
31 - During driver registration, it uses EDDEVID and EDDEVID1 - two device ID
32 registers to decide if sample-based profiling is implemented or not. On some
36 - At the time this documentation was written, the debug driver mainly relies on
[all …]
|
| /Documentation/input/devices/ |
| D | joystick-parport.rst | 3 .. _joystick-parport:
9 :Copyright: |copy| 1998-2000 Vojtech Pavlik <vojtech@ucw.cz>
10 :Copyright: |copy| 1998 Andree Borrmann <a.borrmann@tu-bs.de>
18 Any information in this file is provided as-is, without any guarantee that
36 Many console and 8-bit computer gamepads and joysticks are supported. The
40 ------------
57 The main problem with PC parallel ports is that they don't have +5V power
58 source on any of their pins. So, if you want a reliable source of power
59 for your pads, use either keyboard or joystick port, and make a pass-through
60 cable. You can also pull the power directly from the power supply (the red
[all …]
|
12345678910>>...13