Searched +full:bus +full:- +full:power (Results 1 – 25 of 1088) sorted by relevance
12345678910>>...44
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/bus/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/bus/ |
| 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 …]
|
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/base/power/ |
| 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>
40 #include "power.h"
95 * device_pm_sleep_init - Initialize system suspend-related device fields.
100 dev->power.is_prepared = false; in device_pm_sleep_init()
[all …]
|
| /kernel/linux/linux-6.6/drivers/base/power/ |
| 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"
94 * device_pm_sleep_init - Initialize system suspend-related device fields.
99 dev->power.is_prepared = false; in device_pm_sleep_init()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| 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 …]
|
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/interconnect/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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 …]
|
| 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
35 What: /sys/bus/usb/device/.../wusb_cdid
42 A devices's CDID, as 16 space-separated hex octets.
44 What: /sys/bus/usb/device/.../wusb_ck
53 space-separated hex octets.
[all …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/pm/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/devfreq/ |
| D | exynos-bus.txt | 1 * Generic Exynos Bus frequency device
4 and sub-blocks in SoC. Most Exynos SoCs share the common architecture
5 for buses. Generally, each bus of Exynos SoC includes a source clock
6 and a power line, which are able to change the clock frequency
7 of the bus in runtime. To monitor the usage of each bus in runtime,
9 is able to measure the current load of sub-blocks.
11 The Exynos SoC includes the various sub-blocks which have the each AXI bus.
12 The each AXI bus has the owned source clock but, has not the only owned
13 power line. The power line might be shared among one more sub-blocks.
14 So, we can divide into two type of device as the role of each sub-block.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/soc/imx/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/usb/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/media/ |
| D | qcom,sdm845-venus.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
4 ---
5 $id: "http://devicetree.org/schemas/media/qcom,sdm845-venus.yaml#"
6 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
11 - Stanimir Varbanov <stanimir.varbanov@linaro.org>
19 const: qcom,sdm845-venus
27 power-domains:
33 clock-names:
35 - const: core
36 - const: iface
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ssb/ |
| 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 …]
|
| /kernel/linux/linux-6.6/include/linux/ssb/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| 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 …]
|
12345678910>>...44