| /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 …]
|
| D | renesas,bsc.yaml | 2 ---
3 $id: http://devicetree.org/schemas/bus/renesas,bsc.yaml#
4 $schema: http://devicetree.org/meta-schemas/core.yaml#
6 title: Renesas Bus State Controller (BSC)
9 - Geert Uytterhoeven <geert+renesas@glider.be>
12 The Renesas Bus State Controller (BSC, sometimes called "LBSC within Bus
13 Bridge", or "External Bus Interface") can be found in several Renesas ARM
14 SoCs. It provides an external bus for connecting multiple external
18 While the BSC is a fairly simple memory-mapped bus, it may be part of a
19 PM domain, and may have a gateable functional clock. Before a device
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/bus/ |
| D | simple-pm-bus.txt | 1 Simple Power-Managed Bus
4 A Simple Power-Managed Bus is a transparent bus that doesn't need a real
7 However, its bus controller is part of a PM domain, or under the control of a
8 functional clock. Hence, the bus controller's PM domain and/or clock must be
9 enabled for child devices connected to the bus (either on-SoC or externally)
12 While "simple-pm-bus" follows the "simple-bus" set of properties, as specified
13 in the Devicetree Specification, it is not an extension of "simple-bus".
17 - compatible: Must contain at least "simple-pm-bus".
18 Must not contain "simple-bus".
20 vendor-specific compatible values.
[all …]
|
| D | renesas,bsc.txt | 1 Renesas Bus State Controller (BSC)
4 The Renesas Bus State Controller (BSC, sometimes called "LBSC within Bus
5 Bridge", or "External Bus Interface") can be found in several Renesas ARM SoCs.
6 It provides an external bus for connecting multiple external devices to the
9 While the BSC is a fairly simple memory-mapped bus, it may be part of a PM
11 Before a device connected to the BSC can be accessed, the PM domain
15 The bindings for the BSC extend the bindings for "simple-pm-bus".
19 - compatible: Must contain an SoC-specific value, and "renesas,bsc" and
20 "simple-pm-bus" as fallbacks.
21 SoC-specific values can be:
[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
18 #define pr_fmt(fmt) "PM: " fmt
23 #include <linux/pm.h>
25 #include <linux/pm-trace.h>
89 return "(unknown PM event)"; in pm_verb()
94 * device_pm_sleep_init - Initialize system suspend-related device fields.
99 dev->power.is_prepared = false; in device_pm_sleep_init()
100 dev->power.is_suspended = false; in device_pm_sleep_init()
[all …]
|
| D | clock_ops.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * drivers/base/power/clock_ops.c - Generic clock manipulation PM callbacks
11 #include <linux/pm.h>
38 * pm_clk_enable - Enable a clock, reporting any errors
40 * @ce: PM clock entry corresponding to the clock.
46 if (ce->status < PCE_STATUS_ERROR) { in __pm_clk_enable()
47 ret = clk_enable(ce->clk); in __pm_clk_enable()
49 ce->status = PCE_STATUS_ENABLED; in __pm_clk_enable()
52 __func__, ce->clk, ret); in __pm_clk_enable()
57 * pm_clk_acquire - Acquire a device clock.
[all …]
|
| /kernel/linux/linux-4.19/drivers/base/power/ |
| D | main.c | 2 * drivers/base/power/main.c - Where the driver meets power management.
12 * and add it to the list of power-controlled devices. sysfs entries for
23 #include <linux/pm.h>
25 #include <linux/pm-trace.h>
84 return "(unknown PM event)"; in pm_verb()
89 * device_pm_sleep_init - Initialize system suspend-related device fields.
94 dev->power.is_prepared = false; in device_pm_sleep_init()
95 dev->power.is_suspended = false; in device_pm_sleep_init()
96 dev->power.is_noirq_suspended = false; in device_pm_sleep_init()
97 dev->power.is_late_suspended = false; in device_pm_sleep_init()
[all …]
|
| /kernel/linux/linux-5.10/arch/mips/pci/ |
| D | pci-alchemy.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright 2001-2003, 2007-2008 MontaVista Software Inc.
21 #include <asm/dma-coherence.h>
22 #include <asm/mach-au1x00/au1000.h>
43 unsigned long pm[12]; member
94 ctx->wired_entry = read_c0_wired(); in alchemy_pci_wired_entry()
95 add_wired_entry(0, 0, (unsigned long)ctx->pci_cfg_vm->addr, PM_4K); in alchemy_pci_wired_entry()
96 ctx->last_elo0 = ctx->last_elo1 = ~0; in alchemy_pci_wired_entry()
99 static int config_access(unsigned char access_type, struct pci_bus *bus, in config_access() argument
102 struct alchemy_pci_context *ctx = bus->sysdata; in config_access()
[all …]
|
| /kernel/linux/linux-4.19/arch/mips/pci/ |
| D | pci-alchemy.c | 1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright 2001-2003, 2007-2008 MontaVista Software Inc.
21 #include <asm/dma-coherence.h>
22 #include <asm/mach-au1x00/au1000.h>
43 unsigned long pm[12]; member
94 ctx->wired_entry = read_c0_wired(); in alchemy_pci_wired_entry()
95 add_wired_entry(0, 0, (unsigned long)ctx->pci_cfg_vm->addr, PM_4K); in alchemy_pci_wired_entry()
96 ctx->last_elo0 = ctx->last_elo1 = ~0; in alchemy_pci_wired_entry()
99 static int config_access(unsigned char access_type, struct pci_bus *bus, in config_access() argument
102 struct alchemy_pci_context *ctx = bus->sysdata; in config_access()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/pm/ |
| D | devices.rst | 15 Copyright (c) 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
20 management (PM) code is also driver-specific. Most drivers will do very
24 This writeup gives an overview of how drivers interact with system-wide
27 background for the domain-specific work you'd do with any specific driver.
33 Drivers will use one or both of these models to put devices into low-power
38 Drivers can enter low-power states as part of entering system-wide
39 low-power states like "suspend" (also known as "suspend-to-RAM"), or
41 "suspend-to-disk").
43 This is something that device, bus, and class drivers collaborate on
44 by implementing various role-specific suspend and resume methods to
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
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
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
41 This is something that device, bus, and class drivers collaborate on
[all …]
|
| /kernel/linux/linux-4.19/drivers/bus/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 # Bus Devices
6 menu "Bus devices"
24 bool "Broadcom STB GISB bus arbiter"
28 Driver for the Broadcom Set Top Box System-on-a-chip internal bus
30 and internal bus master decoding.
38 Count bus on the HiSilicon Hip06/7 SoC.
45 The WEIM(Wireless External Interface Module) works like a bus.
52 Driver needed for the MIPS Common Device Memory Map bus in MIPS
53 cores. This bus is for per-CPU tightly coupled devices such as the
[all …]
|
| /kernel/linux/linux-5.10/drivers/bus/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
3 # Bus Devices
6 menu "Bus devices"
24 bool "ARM Integrator Logic Module bus"
29 Say y here to enable support for the ARM Logic Module bus
33 bool "Broadcom STB GISB bus arbiter"
37 Driver for the Broadcom Set Top Box System-on-a-chip internal bus
39 and internal bus master decoding.
42 bool "Baikal-T1 APB-bus driver"
46 Baikal-T1 AXI-APB bridge is used to access the SoC subsystem CSRs.
[all …]
|
| D | simple-pm-bus.c | 2 * Simple Power-Managed Bus Driver
4 * Copyright (C) 2014-2015 Glider bvba
19 const struct device *dev = &pdev->dev; in simple_pm_bus_probe()
20 struct device_node *np = dev->of_node; in simple_pm_bus_probe()
25 * transparent bus device which has a different compatible string in simple_pm_bus_probe()
27 * of the simple-pm-bus tasks for these devices, so return early. in simple_pm_bus_probe()
29 if (pdev->driver_override) in simple_pm_bus_probe()
32 match = of_match_device(dev->driver->of_match_table, dev); in simple_pm_bus_probe()
34 * These are transparent bus devices (not simple-pm-bus matches) that in simple_pm_bus_probe()
40 if (match && match->data) { in simple_pm_bus_probe()
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/nvkm/engine/device/ |
| D | base.c | 41 if (device->handle == handle) in nvkm_device_find_locked()
65 name[nr - 1] = device->handle; in nvkm_device_list()
81 .bus = nv04_bus_new,
102 .bus = nv04_bus_new,
123 .bus = nv04_bus_new,
143 .bus = nv04_bus_new,
165 .bus = nv04_bus_new,
187 .bus = nv04_bus_new,
209 .bus = nv04_bus_new,
231 .bus = nv04_bus_new,
[all …]
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/nouveau/nvkm/engine/device/ |
| D | base.c | 41 if (device->handle == handle) in nvkm_device_find_locked()
65 name[nr - 1] = device->handle; in nvkm_device_list()
81 .bus = nv04_bus_new,
102 .bus = nv04_bus_new,
123 .bus = nv04_bus_new,
143 .bus = nv04_bus_new,
165 .bus = nv04_bus_new,
187 .bus = nv04_bus_new,
209 .bus = nv04_bus_new,
231 .bus = nv04_bus_new,
[all …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | pci.txt | 11 power management refer to Documentation/driver-api/pm/devices.rst and
14 ---------------------------------------------------------------------------
25 1.1. Native and Platform-Based Power Management
26 -----------------------------------------------
28 devices into states in which they draw less power (low-power states) at the
31 Usually, a device is put into a low-power state when it is underutilized or
33 again, it has to be put back into the "fully functional" state (full-power
38 PCI devices may be put into low-power states in two ways, by using the device
39 capabilities introduced by the PCI Bus Power Management Interface Specification,
41 approach, that is referred to as the native PCI power management (native PCI PM)
[all …]
|
| D | runtime_pm.txt | 3 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
9 Support for runtime power management (runtime PM) of I/O devices is provided
10 at the power management core (PM core) level by means of:
12 * The power management workqueue pm_wq in which bus types and device drivers can
13 put their PM-related work items. It is strongly recommended that pm_wq be
14 used for queuing all work items related to runtime PM, because this allows
15 them to be synchronized with system-wide power transitions (suspend to RAM,
19 * A number of runtime PM fields in the 'power' member of 'struct device' (which
20 is of the type 'struct dev_pm_info', defined in include/linux/pm.h) that can
21 be used for synchronizing runtime PM operations with one another.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | pci.rst | 13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
42 capabilities introduced by the PCI Bus Power Management Interface Specification,
44 approach, that is referred to as the native PCI power management (native PCI PM)
50 Devices supporting the native PCI PM usually can generate wakeup signals called
[all …]
|
| D | runtime_pm.rst | 5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
14 Support for runtime power management (runtime PM) of I/O devices is provided
15 at the power management core (PM core) level by means of:
17 * The power management workqueue pm_wq in which bus types and device drivers can
18 put their PM-related work items. It is strongly recommended that pm_wq be
19 used for queuing all work items related to runtime PM, because this allows
20 them to be synchronized with system-wide power transitions (suspend to RAM,
24 * A number of runtime PM fields in the 'power' member of 'struct device' (which
25 is of the type 'struct dev_pm_info', defined in include/linux/pm.h) that can
26 be used for synchronizing runtime PM operations with one another.
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | pm.h | 2 * pm.h - Power management interface
18 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
67 * struct dev_pm_ops - device PM callbacks.
74 * registration of a child already in progress), it may return -EAGAIN, so
75 * that the PM core can execute it once again (e.g. after a new child has
81 * used to indicate to the PM core to leave the device in runtime suspend
82 * if applicable. Namely, if @prepare() returns a positive number, the PM
84 * runtime-suspended and it may be left in that state during the entire
89 * The PM core executes subsystem-level @prepare() for all devices before
105 * of the other devices that the PM core has unsuccessfully attempted to
[all …]
|
| /kernel/linux/linux-5.10/include/linux/device/ |
| D | bus.h | 1 // SPDX-License-Identifier: GPL-2.0
3 * bus.h - the bus-specific portions of the driver model
5 * Copyright (c) 2001-2003 Patrick Mochel <mochel@osdl.org>
6 * Copyright (c) 2004-2009 Greg Kroah-Hartman <gregkh@suse.de>
7 * Copyright (c) 2008-2009 Novell Inc.
8 * Copyright (c) 2012-2019 Greg Kroah-Hartman <gregkh@linuxfoundation.org>
9 * Copyright (c) 2012-2019 Linux Foundation
11 * See Documentation/driver-api/driver-model/ for more information.
19 #include <linux/pm.h>
25 * struct bus_type - The bus type of the device
[all …]
|
| /kernel/linux/linux-4.19/drivers/memory/ |
| D | Kconfig | 15 If you have an embedded system with an AMBA bus and a PL172
19 bool "Atmel (Multi-port DDR-)SDRAM Controller"
23 This driver is for Atmel SDRAM Controller or Atmel Multi-port
24 DDR-SDRAM Controller available on Atmel AT91SAM9 and SAMA5 SoCs.
26 LP-DDR memories.
36 Used to configure the EBI (external bus interface) when the device-
37 tree is used. This bus supports NANDs, external ethernet controller,
46 is intended to provide a glue-less interface to a variety of
60 functions of the driver includes re-configuring AC timing
80 configure devices connected to the GPMC bus.
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | pm.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * pm.h - Power management interface
55 * struct dev_pm_ops - device PM callbacks.
62 * registration of a child already in progress), it may return -EAGAIN, so
63 * that the PM core can execute it once again (e.g. after a new child has
69 * used to indicate to the PM core to leave the device in runtime suspend
70 * if applicable. Namely, if @prepare() returns a positive number, the PM
72 * runtime-suspended and it may be left in that state during the entire
77 * The PM core executes subsystem-level @prepare() for all devices before
93 * of the other devices that the PM core has unsuccessfully attempted to
[all …]
|
| /kernel/linux/linux-5.10/drivers/memory/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 access to attached peripherals through memory bus.
30 If you have an embedded system with an AMBA bus and a PL172
34 bool "Atmel (Multi-port DDR-)SDRAM Controller"
39 This driver is for Atmel SDRAM Controller or Atmel Multi-port
40 DDR-SDRAM Controller available on Atmel AT91SAM9 and SAMA5 SoCs.
42 LP-DDR memories.
53 Used to configure the EBI (external bus interface) when the device-
54 tree is used. This bus supports NANDs, external ethernet controller,
70 bool "Baikal-T1 CM2 L2-RAM Cache Control Block"
[all …]
|