Searched +full:system +full:- +full:power +full:- +full:controller (Results 1 – 25 of 226) sorted by relevance
12345678910
| /Documentation/devicetree/bindings/power/ |
| D | power-controller.txt | 1 * Generic system power control capability
3 Power-management integrated circuits or miscellaneous hardware components are
4 sometimes able to control the system power. The device driver associated with these
6 it can be used to switch off the system. The corresponding device must have the
7 standard property "system-power-controller" in its device node. This property
8 marks the device as able to control the system power. In order to test if this
15 compatible = "active-semi,act8846";
16 system-power-controller;
|
| D | renesas,sysc-rmobile.txt | 1 DT bindings for the Renesas R-Mobile System Controller
3 == System Controller Node ==
5 The R-Mobile System Controller provides the following functions:
6 - Boot mode management,
7 - Reset generation,
8 - Power management.
11 - compatible: Should be "renesas,sysc-<soctype>", "renesas,sysc-rmobile" as
14 - "renesas,sysc-r8a73a4" (R-Mobile APE6)
15 - "renesas,sysc-r8a7740" (R-Mobile A1)
16 - "renesas,sysc-sh73a0" (SH-Mobile AG5)
[all …]
|
| D | renesas,rcar-sysc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/power/renesas,rcar-sysc.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: Renesas R-Car and RZ/G System Controller
10 - Geert Uytterhoeven <geert+renesas@glider.be>
11 - Magnus Damm <magnus.damm@gmail.com>
14 The R-Car (RZ/G) System Controller provides power management for the CPU
20 - renesas,r8a7742-sysc # RZ/G1H
21 - renesas,r8a7743-sysc # RZ/G1M
[all …]
|
| /Documentation/devicetree/bindings/soc/bcm/ |
| D | brcm,bcm2835-pm.txt | 1 BCM2835 PM (Power domains, watchdog)
3 The PM block controls power domains and some reset lines, and includes
4 a watchdog timer. This binding supersedes the brcm,bcm2835-pm-wdt
9 - compatible: Should be "brcm,bcm2835-pm"
10 - reg: Specifies base physical address and size of the two
13 - clocks: a) v3d: The V3D clock from CPRMAN
17 - #reset-cells: Should be 1. This property follows the reset controller
19 - #power-domain-cells: Should be 1. This property follows the power domain
24 - timeout-sec: Contains the watchdog timeout in seconds
25 - system-power-controller: Whether the watchdog is controlling the
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | twl4030-power.txt | 1 Texas Instruments TWL family (twl4030) reset and power management module
3 The power management module inside the TWL family provides several facilities
4 to control the power resources, including power scripts. For now, the
5 binding only supports the complete shutdown of the system after poweroff.
8 - compatible : must be one of the following
9 "ti,twl4030-power"
10 "ti,twl4030-power-reset"
11 "ti,twl4030-power-idle"
12 "ti,twl4030-power-idle-osc-off"
14 The use of ti,twl4030-power-reset is recommended at least on
[all …]
|
| 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 | rn5t618.txt | 3 Ricoh RN5T567/RN5T618/RC5T619 is a power management IC family which
4 integrates 3 to 5 step-down DCDC converters, 7 to 10 low-dropout regulators,
6 The RN5T618/RC5T619 provides additionally a Li-ion battery charger,
11 - compatible: must be one of
15 - reg: the I2C slave address of the device
18 - interrupts: interrupt mapping for IRQ
19 See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
20 - system-power-controller:
21 See Documentation/devicetree/bindings/power/power-controller.txt
23 Sub-nodes:
[all …]
|
| D | ene-kb3930.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/ene-kb3930.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ENE KB3930 Embedded Controller bindings
10 This binding describes the ENE KB3930 Embedded Controller attached to an
14 - Lubomir Rintel <lkundrak@v3.sk>
19 - enum:
20 - dell,wyse-ariel-ec # Dell Wyse Ariel board (3020)
21 - const: ene,kb3930
[all …]
|
| D | mps,mp2629.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: MP2629 Battery Charger PMIC from Monolithic Power System.
10 - Saravanan Sekar <sravanhome@gmail.com>
13 MP2629 is a PMIC providing battery charging and power supply for smartphones,
16 The battery charge management device handles battery charger controller and
17 ADC IIO device for battery, system voltage
29 interrupt-controller: true
31 "#interrupt-cells":
[all …]
|
| /Documentation/driver-api/usb/ |
| D | persist.rst | 1 .. _usb-persist:
3 USB device persistence during system suspend
14 bus must continue to supply suspend current (around 1-5 mA). This
16 detect connect-change events (devices being plugged in or unplugged).
17 The technical term is "power session".
19 If a USB device's power session is interrupted then the system is
24 device plugged into the port. The system must assume the worst.
27 controller loses power during a system suspend, then when the system
28 wakes up all the devices attached to that controller are treated as
34 while the system was asleep and a new keyboard was plugged in when the
[all …]
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | panel-common.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/display/panel/panel-common.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
24 width-mm:
29 height-mm:
38 on the system (e.g. as an affixed label) or specified in the system's
43 non-descriptive information. For instance an LCD panel in a system that
[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";
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | cortina,gemini-pinctrl.txt | 1 Cortina Systems Gemini pin controller
3 This pin controller is found in the Cortina Systems Gemini SoC family,
4 see further arm/gemini.txt. It is a purely group-based multiplexing pin
5 controller.
7 The pin controller node must be a subnode of the system controller node.
10 - compatible: "cortina,gemini-pinctrl"
12 Subnodes of the pin controller contain pin control multiplexing set-up
15 Please refer to pinctrl-bindings.txt for generic pin multiplexing nodes
19 - skew-delay is supported on the Ethernet pins
20 - drive-strength with 4, 8, 12 or 16 mA as argument is supported for
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | lpit.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Low Power Idle Table (LPIT)
7 To enumerate platform Low Power Idle states, Intel platforms are using
8 “Low Power Idle Table” (LPIT). More details about this table can be
12 Residencies for each low power state can be read via FFH
18 - CPU PKG C10 (Read via FFH interface)
19 - Platform Controller Hub (PCH) SLP_S0 (Read via memory mapped interface)
24 /sys/devices/system/cpu/cpuidle/low_power_idle_cpu_residency_us
25 /sys/devices/system/cpu/cpuidle/low_power_idle_system_residency_us
31 residency, or system time spent with the SLP_S0# signal asserted.
[all …]
|
| /Documentation/devicetree/bindings/arm/mediatek/ |
| D | mediatek,vcodecsys.txt | 1 Mediatek vcodecsys controller
4 The Mediatek vcodecsys controller provides various clocks to the system.
8 - compatible: Should be one of:
9 - "mediatek,mt6765-vcodecsys", "syscon"
10 - #clock-cells: Must be 1
12 The vcodecsys controller uses the common clk binding from
13 Documentation/devicetree/bindings/clock/clock-bindings.txt
14 The available clocks are defined in dt-bindings/clock/mt*-clk.h.
16 The vcodecsys controller also uses the common power domain from
18 The available power doamins are defined in dt-bindings/power/mt*-power.h.
[all …]
|
| D | mediatek,mipi0a.txt | 1 Mediatek mipi0a (mipi_rx_ana_csi0a) controller
4 The Mediatek mipi0a controller provides various clocks
5 to the system.
9 - compatible: Should be one of:
10 - "mediatek,mt6765-mipi0a", "syscon"
11 - #clock-cells: Must be 1
13 The mipi0a controller uses the common clk binding from
14 Documentation/devicetree/bindings/clock/clock-bindings.txt
15 The available clocks are defined in dt-bindings/clock/mt*-clk.h.
17 The mipi0a controller also uses the common power domain from
[all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | rtc-omap.txt | 4 - compatible:
5 - "ti,da830-rtc" - for RTC IP used similar to that on DA8xx SoC family.
6 - "ti,am3352-rtc" - for RTC IP used similar to that on AM335x SoC family.
7 This RTC IP has special WAKE-EN Register to enable
11 - "ti,am4372-rtc" - for RTC IP used similar to that on AM437X SoC family.
12 - reg: Address range of rtc register set
13 - interrupts: rtc timer, alarm interrupts in order
16 - system-power-controller: whether the rtc is controlling the system power
18 - clocks: Any internal or external clocks feeding in to rtc
19 - clock-names: Corresponding names of the clocks
[all …]
|
| /Documentation/hwmon/ |
| D | occ.rst | 1 Kernel driver occ-hwmon
12 -----------
14 This driver supports hardware monitoring for the On-Chip Controller (OCC)
15 embedded on POWER processors. The OCC is a device that collects and aggregates
16 sensor data from the processor and the system. The OCC can provide the raw
17 sensor data as well as perform thermal and power management on the system.
20 manually if an "ibm,p8-occ-hwmon" compatible device is found under the
21 appropriate I2C bus node in the device-tree.
23 The P9 version of this driver is a client driver of the FSI-based OCC driver.
24 It will be probed automatically by the FSI-based OCC driver.
[all …]
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | sci-pm-domain.txt | 1 Texas Instruments TI-SCI Generic Power Domain
2 ---------------------------------------------
4 Some TI SoCs contain a system controller (like the PMMC, etc...) that is
6 Communication between the host processor running an OS and the system
7 controller happens through a protocol known as TI-SCI [1].
15 bindings in Documentation/devicetree/bindings/power/power-domain.yaml. Because
20 --------------------
21 - compatible: should be "ti,sci-pm-domain"
22 - #power-domain-cells: Can be one of the following:
33 -------------
[all …]
|
| /Documentation/devicetree/bindings/spmi/ |
| D | spmi.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: System Power Management Interface (SPMI) Controller
10 - Stephen Boyd <sboyd@kernel.org>
13 The System Power Management (SPMI) controller is a 2-wire bus defined
14 by the MIPI Alliance for power management control to be used on SoC designs.
17 bindings defined here, plus any bus controller specific properties, if
20 Each SPMI controller has zero or more child nodes (up to 16 ones), each
30 "#address-cells":
[all …]
|
| /Documentation/devicetree/bindings/iommu/ |
| D | samsung,sysmmu.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung Exynos IOMMU H/W, System MMU (System Memory Management Unit)
10 - Marek Szyprowski <m.szyprowski@samsung.com>
13 Samsung's Exynos architecture contains System MMUs that enables scattered
14 physical memory chunks visible as a contiguous region to DMA-capable peripheral
15 devices like MFC, FIMC, FIMD, GScaler, FIMC-IS and so forth.
17 System MMU is an IOMMU and supports identical translation table format to
19 permissions, shareability and security protection. In addition, System MMU has
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | max8907.txt | 4 - compatible: "maxim,max8907"
5 - reg: I2C slave address
6 - interrupts: The interrupt output of the controller
7 - mbatt-supply: The input supply for MBATT, BBAT, SDBY, VRTC.
8 - in-v1-supply: The input supply for SD1.
9 - in-v2-supply: The input supply for SD2.
10 - in-v3-supply: The input supply for SD3.
11 - in1-supply: The input supply for LDO1.
13 - in20-supply: The input supply for LDO20.
14 - regulators: A node that houses a sub-node for each regulator within the
[all …]
|
| /Documentation/devicetree/bindings/soc/mediatek/ |
| D | scpsys.txt | 4 The System Control Processor System (SCPSYS) has several power management
5 related tasks in the system. The tasks include thermal measurement, dynamic
7 The System Power Manager (SPM) inside the SCPSYS is for the MTCMOS power
11 power/power-domain.yaml. It provides the power domains defined in
12 - include/dt-bindings/power/mt8173-power.h
13 - include/dt-bindings/power/mt6797-power.h
14 - include/dt-bindings/power/mt6765-power.h
15 - include/dt-bindings/power/mt2701-power.h
16 - include/dt-bindings/power/mt2712-power.h
17 - include/dt-bindings/power/mt7622-power.h
[all …]
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | sleep.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rob Herring <robh@kernel.org>
13 Devices on SOCs often have mechanisms for placing devices into low-power
15 this information is more complicated than a cell-index property can
20 which consists of a phandle to a sleep controller, followed by a
21 controller-specific sleep specifier of zero or more cells.
23 The semantics of what type of low power modes are possible are defined
24 by the sleep controller. Some examples of the types of low power modes
[all …]
|
| /Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,sci.txt | 1 Texas Instruments System Control Interface (TI-SCI) Message Protocol
2 --------------------------------------------------------------------
6 management of the System on Chip (SoC) system. These include various system
9 An example of such an SoC is K2G, which contains the system control hardware
10 block called Power Management Micro Controller (PMMC). This hardware block is
16 TI-SCI controller Device Node:
19 The TI-SCI node describes the Texas Instrument's System Controller entity node.
21 specific functionality such as clocks, power domain, reset or additional
23 relationship between the TI-SCI parent node to the child node.
26 -------------------
[all …]
|
12345678910