Searched +full:system +full:- +full:power +full:- +full:controller (Results 1 – 25 of 994) sorted by relevance
12345678910>>...40
| /linux-5.10/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 | 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 | 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 | as3722.txt | 1 * ams AS3722 Power management IC.
4 -------------------
5 - compatible: Must be "ams,as3722".
6 - reg: I2C device address.
7 - interrupt-controller: AS3722 has internal interrupt controller which takes the
8 interrupt request from internal sub-blocks like RTC, regulators, GPIOs as well
10 - #interrupt-cells: Should be set to 2 for IRQ number and flags.
12 of AS3722 are defined at dt-bindings/mfd/as3722.h
14 interrupts.txt, using dt-bindings/irq.
17 --------------------
[all …]
|
| /linux-5.10/drivers/usb/typec/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Support"
6 USB Type-C Specification defines a cable and connector for USB where
8 be Type-A plug on one end of the cable and Type-B plug on the other.
9 Determination of the host-to-device relationship happens through a
10 specific Configuration Channel (CC) which goes through the USB Type-C
12 Accessory Modes - Analog Audio and Debug - and if USB Power Delivery
16 USB Power Delivery Specification defines a protocol that can be used
18 partners. USB Power Delivery allows higher voltages then the normal
19 5V, up to 20V, and current up to 5A over the cable. The USB Power
[all …]
|
| /linux-5.10/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 …]
|
| /linux-5.10/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 …]
|
| /linux-5.10/Documentation/devicetree/bindings/power/ |
| 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 …]
|
| 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 …]
|
| /linux-5.10/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 …]
|
| /linux-5.10/drivers/mfd/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
23 bool "Altera Arria10 DevKit System Resource chip"
28 Support for the Altera Arria10 DevKit MAX5 System Resource chip
31 power supply alarms (hwmon).
34 bool "Altera SOCFPGA System Manager"
38 Select this to get System Manager support for all Altera branded
39 SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by
44 tristate "Active-semi ACT8945A"
49 Support for the ACT8945A PMIC from Active-semi. This device
50 features three step-down DC/DC converters and four low-dropout
[all …]
|
| /linux-5.10/drivers/firmware/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
10 tristate "ARM System Control and Management Interface (SCMI) Message Protocol"
14 ARM System Control and Management Interface (SCMI) protocol is a
15 set of operating system-independent software interfaces that are
16 used in system management. SCMI is extensible and currently provides
17 interfaces for: Discovery and self-description of the interfaces
18 it supports, Power domain management which is the ability to place
19 a given device or domain into the various power-saving states that
31 tristate "SCMI power domain driver"
[all …]
|
| /linux-5.10/drivers/acpi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
10 bool "ACPI (Advanced Configuration and Power Interface) Support"
16 Advanced Configuration and Power Interface (ACPI) support for
17 Linux requires an ACPI-compliant platform (hardware/firmware),
18 and assumes the presence of OS-directed configuration and power
23 legacy configuration and power management interfaces, including
24 the Plug-and-Play BIOS specification (PnP BIOS), the
25 MultiProcessor Specification (MPS), and the Advanced Power
30 <https://01.org/linux-acpi>
37 ACPI is an open industry specification originally co-developed by
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | samsung-phy.txt | 2 -------------------------------------------------
5 - compatible : should be one of the listed compatibles:
6 - "samsung,s5pv210-mipi-video-phy"
7 - "samsung,exynos5420-mipi-video-phy"
8 - "samsung,exynos5433-mipi-video-phy"
9 - #phy-cells : from the generic phy bindings, must be 1;
12 - syscon - phandle to the PMU system controller
15 - samsung,pmu-syscon - phandle to the PMU system controller
16 - samsung,disp-sysreg - phandle to the DISP system registers controller
17 - samsung,cam0-sysreg - phandle to the CAM0 system registers controller
[all …]
|
| /linux-5.10/Documentation/x86/ |
| D | earlyprintk.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Mini-HOWTO for using the earlyprintk=dbgp boot option with a
13 [host/target] <-------> [USB debug key] <-------> [client/console]
18 a) Host/target system needs to have USB debug port capability.
21 the lspci -vvv output::
23 # lspci -vvv
25 …00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) (p…
27 …Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisIN…
28 …Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- I…
31 Region 0: Memory at fe227000 (32-bit, non-prefetchable) [size=1K]
[all …]
|
| /linux-5.10/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 …]
|
| /linux-5.10/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 …]
|
| /linux-5.10/Documentation/driver-api/thermal/ |
| D | power_allocator.rst | 2 Power allocator governor tunables
6 -----------
19 PID Controller
20 --------------
22 The power allocator governor implements a
23 Proportional-Integral-Derivative controller (PID controller) with
24 temperature as the control input and power as the controlled output:
29 - e = desired_temperature - current_temperature
30 - err_integral is the sum of previous errors
31 - diff_err = e - previous_error
[all …]
|
| /linux-5.10/drivers/firmware/imx/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 The System Controller Firmware (SCFW) is a low-level system function
18 which runs on a dedicated Cortex-M core to provide power, clock, and
26 bool "IMX SCU Power Domain driver"
29 The System Controller Firmware (SCFW) based power domain driver.
|
| /linux-5.10/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,brcmstb.txt | 2 -----------------------------------------------
3 Boards with Broadcom Brahma15 ARM-based BCMxxxx (generally BCM7xxx variants)
7 - compatible: "brcm,bcm<chip_id>", "brcm,brcmstb"
11 #address-cells = <2>;
12 #size-cells = <2>;
16 Further, syscon nodes that map platform-specific registers used for general
17 system control is required:
19 - compatible: "brcm,bcm<chip_id>-sun-top-ctrl", "syscon"
20 - compatible: "brcm,bcm<chip_id>-cpu-biu-ctrl",
21 "brcm,brcmstb-cpu-biu-ctrl",
[all …]
|
| /linux-5.10/arch/arm/mach-u300/ |
| D | regulator.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * arch/arm/mach-u300/regulator.c
5 * Copyright (C) 2009 ST-Ericsson AB
6 * Handle board-bound regulators and board power not related
21 /* Power Management Control 16bit (R/W) */
27 * Regulators that power the board and chip and which are
34 * This function is used from pm.h to shut down the system by
36 * LDO D (main power).
44 /* Disable LDO D to shut down the system */ in u300_pm_poweroff()
48 pr_err("regulator not available to shut down system\n"); in u300_pm_poweroff()
[all …]
|
| /linux-5.10/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 …]
|
| /linux-5.10/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 …]
|
| /linux-5.10/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 …]
|
12345678910>>...40