/linux/Documentation/ABI/testing/ |
H A D | sysfs-driver-intel-xe-hwmon | 1 What: /sys/bus/pci/drivers/xe/.../hwmon/hwmon<i>/power1_max 4 Contact: intel-xe@lists.freedesktop.org 5 Description: RW. Card reactive sustained (PL1) power limit in microwatts. 7 The power controller will throttle the operating frequency 8 if the power averaged over a window (typically seconds) 10 power limit is disabled, writing 0 disables the 11 limit. Writing values > 0 and <= TDP will enable the power limit. 15 What: /sys/bus/pci/drivers/xe/.../hwmon/hwmon<i>/power1_rated_max 18 Contact: intel-xe@lists.freedesktop.org 19 Description: RO. Card default power limit (default TDP setting). [all …]
|
H A D | sysfs-driver-intel-i915-hwmon | 1 What: /sys/bus/pci/drivers/i915/.../hwmon/hwmon<i>/in0_input 4 Contact: intel-gfx@lists.freedesktop.org 9 What: /sys/bus/pci/drivers/i915/.../hwmon/hwmon<i>/power1_max 12 Contact: intel-gfx@lists.freedesktop.org 13 Description: RW. Card reactive sustained (PL1/Tau) power limit in microwatts. 15 The power controller will throttle the operating frequency 16 if the power averaged over a window (typically seconds) 18 power limit is disabled, writing 0 disables the 19 limit. Writing values > 0 will enable the power limit. 23 What: /sys/bus/pci/drivers/i915/.../hwmon/hwmon<i>/power1_rated_max [all …]
|
H A D | sysfs-bus-usb | 1 What: /sys/bus/usb/devices/<INTERFACE>/authorized 9 by writing INTERFACE to /sys/bus/usb/drivers_probe 10 This allows to avoid side-effects with drivers 15 What: /sys/bus/usb/devices/usbX/interface_authorized_default 22 What: /sys/bus/usb/device/.../authorized 28 drivers, non-authorized one are not. By default, wired 31 What: /sys/bus/usb/drivers/.../new_id 33 Contact: linux-usb@vger.kernel.org 48 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id 53 # echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id [all …]
|
H A D | sysfs-platform-dfl-fme | 1 What: /sys/bus/platform/devices/dfl-fme.0/ports_num 5 Description: Read-only. One DFL FPGA device may have more than 1 9 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_id 13 Description: Read-only. It returns Bitstream (static FPGA region) 17 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_metadata 21 Description: Read-only. It returns Bitstream (static FPGA region) meta 25 What: /sys/bus/platform/devices/dfl-fme.0/cache_size 29 Description: Read-only. It returns cache size of this FPGA device. 31 What: /sys/bus/platform/devices/dfl-fme.0/fabric_version 35 Description: Read-only. It returns fabric version of this FPGA device. [all …]
|
H A D | sysfs-platform-dptf | 1 What: /sys/bus/platform/devices/INT3407:00/dptf_power/charger_type 4 Contact: linux-acpi@vger.kernel.org 6 (RO) The charger type - Traditional, Hybrid or NVDC. 8 What: /sys/bus/platform/devices/INT3407:00/dptf_power/adapter_rating_mw 11 Contact: linux-acpi@vger.kernel.org 13 (RO) Adapter rating in milliwatts (the maximum Adapter power). 16 What: /sys/bus/platform/devices/INT3407:00/dptf_power/max_platform_power_mw 19 Contact: linux-acpi@vger.kernel.org 21 (RO) Maximum platform power that can be supported by the battery 24 What: /sys/bus/platform/devices/INT3407:00/dptf_power/platform_power_source [all …]
|
H A D | sysfs-platform-wilco-ec | 1 What: /sys/bus/platform/devices/GOOG000C\:00/boot_on_ac 6 when AC power is connected. This is useful for users who 11 What: /sys/bus/platform/devices/GOOG000C\:00/build_date 18 What: /sys/bus/platform/devices/GOOG000C\:00/build_revision 26 What: /sys/bus/platform/devices/GOOG000C\:00/model_number 34 What: /sys/bus/platform/devices/GOOG000C\:00/usb_charge 41 low power states: 43 - In S0, the port will always provide power. 44 - In S0ix, if usb_charge is enabled, then power will be 46 Else no power is supplied. [all …]
|
/linux/drivers/base/power/ |
H A D | main.c | 1 // SPDX-License-Identifier: GPL-2.0 3 * drivers/base/power/main.c - Where the driver meets power management. 10 * and add it to the list of power-controlled devices. sysfs entries for 11 * controlling device power management will also be added. 13 * A separate list is used for keeping track of power info, because the power 26 #include <linux/pm-trace.h> 33 #include <trace/events/power.h> 39 #include "power.h" 93 * device_pm_sleep_init - Initialize system suspend-related device fields. 98 dev->power.is_prepared = false; in device_pm_sleep_init() [all …]
|
/linux/Documentation/hwmon/ |
H A D | ina209.rst | 6 * Burr-Brown / Texas Instruments INA209 10 Addresses scanned: - 16 - Paul Hays <Paul.Hays@cattail.ca> 17 - Ira W. Snyder <iws@ovro.caltech.edu> 18 - Guenter Roeck <linux@roeck-us.net> 22 ----------- 24 The TI / Burr-Brown INA209 monitors voltage, current, and power on the high side 25 of a D.C. power supply. It can perform measurements and calculations in the 27 calibration multiplier to scale the displayed current and power values. 31 ------------- [all …]
|
H A D | ina2xx.rst | 10 Addresses: I2C 0x40 - 0x4f 20 Addresses: I2C 0x40 - 0x4f 30 Addresses: I2C 0x40 - 0x4f 40 Addresses: I2C 0x40 - 0x4f 50 Addresses: I2C 0x40 - 0x4f 60 Addresses: I2C 0x40 - 0x4f 70 Addresses: I2C 0x40 - 0x4f 80 ----------- 82 The INA219 is a high-side current shunt and power monitor with an I2C 86 The INA220 is a high or low side current shunt and power monitor with an I2C [all …]
|
/linux/Documentation/devicetree/bindings/bus/ |
H A D | simple-pm-bus.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/bus/simple-pm-bus.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Simple Power-Managed Bus 10 - Geert Uytterhoeven <geert+renesas@glider.be> 13 A Simple Power-Managed Bus is a transparent bus that doesn't need a real 16 However, its bus controller is part of a PM domain, or under the control 17 of a functional clock. Hence, the bus controller's PM domain and/or 18 clock must be enabled for child devices connected to the bus (either [all …]
|
H A D | qcom,ssc-block-bus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/bus/qcom,ssc-block-bus.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: The AHB Bus Providing a Global View of the SSC Block on (some) qcom SoCs 10 - Michael Srba <Michael.Srba@seznam.cz> 13 This binding describes the dependencies (clocks, resets, power domains) which 14 need to be turned on in a sequence before communication over the AHB bus 27 - const: qcom,msm8998-ssc-block-bus 28 - const: qcom,ssc-block-bus [all …]
|
H A D | fsl,imx8qxp-pixel-link-msi-bus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/bus/fsl,imx8qxp-pixel-link-msi-bus.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Freescale i.MX8qxp Pixel Link Medium Speed Interconnect (MSI) Bus 10 - Liu Ying <victor.liu@nxp.com> 13 i.MX8qxp pixel link MSI bus is used to control settings of PHYs, I/Os 14 sitting together with the PHYs. It is not the same as the MSI bus coming 15 from i.MX8 System Controller Unit (SCU) which is used to control power, 18 i.MX8qxp pixel link MSI bus is a simple memory-mapped bus. Two input clocks, [all …]
|
/linux/Documentation/devicetree/bindings/interconnect/ |
H A D | samsung,exynos-bus.yaml | 1 # SPDX-License-Identifier: GPL-2.0 3 --- 4 $id: http://devicetree.org/schemas/interconnect/samsung,exynos-bus.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Samsung Exynos SoC Bus and Interconnect 10 - Chanwoo Choi <cw00.choi@samsung.com> 11 - Krzysztof Kozlowski <krzk@kernel.org> 15 sub-blocks in SoC. Most Exynos SoCs share the common architecture for buses. 16 Generally, each bus of Exynos SoC includes a source clock and a power line, 17 which are able to change the clock frequency of the bus in runtime. To [all …]
|
/linux/Documentation/driver-api/pm/ |
H A D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 Device Power Management Basics 10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc. 17 Most of the code in Linux is device drivers, so most of the Linux power 18 management (PM) code is also driver-specific. Most drivers will do very 22 This writeup gives an overview of how drivers interact with system-wide 23 power management goals, emphasizing the models and interfaces that are 25 background for the domain-specific work you'd do with any specific driver. 28 Two Models for Device Power Management 31 Drivers will use one or both of these models to put devices into low-power [all …]
|
/linux/Documentation/usb/ |
H A D | chipidea.rst | 6 ----------------------------------- 12 ------------------------- 29 otg-rev = <0x0200>; 30 adp-disable; 33 ------------------- 35 1) Power up 2 Freescale i.MX6Q sabre SD boards with gadget class driver loaded 41 The A-device (with micro A plug inserted) should enumerate B-device. 45 On B-device:: 47 echo 1 > /sys/bus/platform/devices/ci_hdrc.0/inputs/b_bus_req 49 B-device should take host role and enumerate A-device. [all …]
|
/linux/Documentation/devicetree/bindings/soc/imx/ |
H A D | fsl,imx8mm-vpu-blk-ctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/soc/imx/fsl,imx8mm-vpu-blk-ctrl.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: NXP i.MX8MM VPU blk-ctrl 10 - Lucas Stach <l.stach@pengutronix.de> 13 The i.MX8MM VPU blk-ctrl is a top-level peripheral providing access to 14 the NoC and ensuring proper power sequencing of the VPU peripherals 20 - const: fsl,imx8mm-vpu-blk-ctrl 21 - const: syscon [all …]
|
/linux/arch/arm/boot/dts/samsung/ |
H A D | exynos5420.dtsi | 1 // SPDX-License-Identifier: GPL-2.0 14 #include <dt-bindings/clock/exynos5420.h> 15 #include <dt-bindings/clock/exynos-audss-clk.h> 16 #include <dt-bindings/interrupt-controller/arm-gic.h> 37 bus_disp1: bus-disp1 { 38 compatible = "samsung,exynos-bus"; 40 clock-names = "bus"; 44 bus_disp1_fimd: bus-disp1-fimd { 45 compatible = "samsung,exynos-bus"; 47 clock-names = "bus"; [all …]
|
/linux/include/linux/ssb/ |
H A D | ssb.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 12 #include <linux/dma-mapping.h> 66 u8 maxpwr_bg; /* 2.4GHz Amplifier Max Power (in dBm Q5.2) */ 67 u8 maxpwr_al; /* 5.2GHz Amplifier Max Power (in dBm Q5.2) */ 68 u8 maxpwr_a; /* 5.3GHz Amplifier Max Power (in dBm Q5.2) */ 69 u8 maxpwr_ah; /* 5.8GHz Amplifier Max Power (in dBm Q5.2) */ 70 u8 itssi_a; /* Idle TSSI Target for A-PHY */ 71 u8 itssi_bg; /* Idle TSSI Target for B/G-PHY */ 76 u8 txpid2g[4]; /* 2GHz TX power index */ 77 u8 txpid5gl[4]; /* 4.9 - 5.1GHz TX power index */ [all …]
|
/linux/Documentation/driver-api/ |
H A D | slimbus.rst | 9 ---------------- 10 SLIMbus (Serial Low Power Interchip Media Bus) is a specification developed by 11 MIPI (Mobile Industry Processor Interface) alliance. The bus uses master/slave 12 configuration, and is a 2-wire multi-drop implementation (clock, and data). 15 (System-on-Chip) and peripheral components (typically codec). SLIMbus uses 16 Time-Division-Multiplexing to accommodate multiple data channels, and 19 The control channel is used for various control functions such as bus 24 A data channel is used for data-transfer between 2 SLIMbus devices. Data 28 --------------------- 32 channel allocation. Every bus has 1 active manager. [all …]
|
/linux/Documentation/devicetree/bindings/media/ |
H A D | qcom,sdm845-venus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/media/qcom,sdm845-venus.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Stanimir Varbanov <stanimir.varbanov@linaro.org> 17 - $ref: qcom,venus-common.yaml# 21 const: qcom,sdm845-venus 23 power-domains: 29 clock-names: 31 - const: core [all …]
|
/linux/Documentation/ABI/stable/ |
H A D | sysfs-bus-usb | 1 What: /sys/bus/usb/devices/.../power/persist 6 USB device directories can contain a file named power/persist. 8 not the "USB-Persist" facility is enabled for the device. For 12 For more information, see Documentation/driver-api/usb/persist.rst. 14 What: /sys/bus/usb/devices/.../power/autosuspend 20 power/autosuspend. This file holds the time (in seconds) 27 The autosuspend delay for newly-created devices is set to 30 What: /sys/bus/usb/device/.../power/connected_duration 37 connected to the machine. This file is read-only. 42 What: /sys/bus/usb/device/.../power/active_duration [all …]
|
/linux/drivers/regulator/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 15 output in order to save power and prolong battery life. This applies 38 managed regulators and simple non-configurable regulators. 55 control power supplies for such devices. 64 the netlink mechanism. User-space applications can subscribe to these events 65 for real-time updates on various regulator events. 75 They provide two I2C-controlled DC/DC step-down converters with 79 tristate "Marvell 88PM800 Power regulators" 89 tristate "Marvell 88PM8607 Power regulators" 101 tristate "Active-semi act8865 voltage regulator" [all …]
|
/linux/Documentation/driver-api/driver-model/ |
H A D | overview.rst | 16 bus-specific drivers for bridges and devices by consolidating a set of data 19 Traditional driver models implemented some sort of tree-like structure 21 uniformity across the different bus types. 24 a bus and the devices that can appear under the bus. The unified bus 26 of common callbacks, such as device discovery during bus probing, bus 27 shutdown, bus power management, etc. 30 computer: namely the ability to do seamless device "plug and play", power 32 Microsoft (namely ACPI) ensures that almost every device on almost any bus 33 on an x86-compatible system can work within this paradigm. Of course, 34 not every bus is able to support all such operations, although most [all …]
|
/linux/Documentation/driver-api/thermal/ |
H A D | intel_dptf.rst | 1 .. SPDX-License-Identifier: GPL-2.0 12 ------------ 15 level hardware/software solution for power and thermal management. 17 As a container for multiple power/thermal technologies, DPTF provides 26 "Linux Thermal Daemon" to read platform specific thermal and power 31 ---------------------------- 33 :file:`/sys/bus/platform/devices/<N>/uuids`, where <N> 43 "42A441D6-AE6A-462b-A84B-4A8CE79027D3" : Passive 1 45 "3A95C389-E4B8-4629-A526-C52C88626BAE" : Active 47 "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" : Critical [all …]
|
/linux/sound/hda/ext/ |
H A D | hdac_ext_controller.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * hdac-ext-controller.c - HD-audio extended controller functions. 5 * Copyright (C) 2014-2015 Intel Corp 18 * processing pipe helpers - these helpers are useful for dealing with HDA 23 * snd_hdac_ext_bus_ppcap_enable - enable/disable processing pipe capability 24 * @bus: the pointer to HDAC bus object 27 void snd_hdac_ext_bus_ppcap_enable(struct hdac_bus *bus, bool enable) in snd_hdac_ext_bus_ppcap_enable() argument 30 if (!bus->ppcap) { in snd_hdac_ext_bus_ppcap_enable() 31 dev_err(bus->dev, "Address of PP capability is NULL"); in snd_hdac_ext_bus_ppcap_enable() 36 snd_hdac_updatel(bus->ppcap, AZX_REG_PP_PPCTL, in snd_hdac_ext_bus_ppcap_enable() [all …]
|