Searched +full:system +full:- +full:management (Results 1 – 25 of 1062) sorted by relevance
12345678910>>...43
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 1 What: /sys/devices/system/node/possible
3 Contact: Linux Memory Management list <linux-mm@kvack.org>
7 What: /sys/devices/system/node/online
9 Contact: Linux Memory Management list <linux-mm@kvack.org>
13 What: /sys/devices/system/node/has_normal_memory
15 Contact: Linux Memory Management list <linux-mm@kvack.org>
19 What: /sys/devices/system/node/has_cpu
21 Contact: Linux Memory Management list <linux-mm@kvack.org>
25 What: /sys/devices/system/node/has_high_memory
27 Contact: Linux Memory Management list <linux-mm@kvack.org>
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | dcdbas.rst | 2 Dell Systems Management Base Driver
8 The Dell Systems Management Base Driver provides a sysfs interface for
9 systems management software such as Dell OpenManage to perform system
10 management interrupts and host control actions (system power cycle or
24 System Management Interrupt
27 On some Dell systems, systems management software must access certain
28 management information via a system management interrupt (SMI). The SMI data
29 buffer must reside in 32-bit address space, and the physical address of the
32 The driver creates the following sysfs entries for systems management
33 software to perform these system management interrupts::
[all …]
|
| /kernel/linux/linux-6.6/Documentation/driver-api/ |
| D | dcdbas.rst | 2 Dell Systems Management Base Driver
8 The Dell Systems Management Base Driver provides a sysfs interface for
9 systems management software such as Dell OpenManage to perform system
10 management interrupts and host control actions (system power cycle or
24 System Management Interrupt
27 On some Dell systems, systems management software must access certain
28 management information via a system management interrupt (SMI). The SMI data
29 buffer must reside in 32-bit address space, and the physical address of the
32 The driver creates the following sysfs entries for systems management
33 software to perform these system management interrupts::
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 1 What: /sys/devices/system/node/possible
3 Contact: Linux Memory Management list <linux-mm@kvack.org>
7 What: /sys/devices/system/node/online
9 Contact: Linux Memory Management list <linux-mm@kvack.org>
13 What: /sys/devices/system/node/has_normal_memory
15 Contact: Linux Memory Management list <linux-mm@kvack.org>
19 What: /sys/devices/system/node/has_cpu
21 Contact: Linux Memory Management list <linux-mm@kvack.org>
25 What: /sys/devices/system/node/has_high_memory
27 Contact: Linux Memory Management list <linux-mm@kvack.org>
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | pci.rst | 2 PCI Power Management
8 management. Based on previous work by Patrick Mochel <mochel@transmeta.com>
11 This document only covers the aspects of power management specific to PCI
13 power management refer to Documentation/driver-api/pm/devices.rst and
18 1. Hardware and Platform Support for PCI Power Management
19 2. PCI Subsystem and Device Power Management
20 3. PCI Device Drivers and Power Management
24 1. Hardware and Platform Support for PCI Power Management
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
[all …]
|
| D | apm-acpi.rst | 5 If you have a relatively recent x86 mobile, desktop, or server system,
6 odds are it supports either Advanced Power Management (APM) or
8 of the two technologies and puts power management in the hands of the
9 operating system, allowing for more intelligent power management than
12 The best way to determine which, if either, your system supports is to
21 simply cannot mix and match the two. Only one power management
24 User-space Daemons
25 ------------------
26 Both APM and ACPI rely on user-space daemons, apmd and acpid
29 and be sure that they are started sometime in the system boot process.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/power/ |
| D | pci.rst | 2 PCI Power Management
8 management. Based on previous work by Patrick Mochel <mochel@transmeta.com>
11 This document only covers the aspects of power management specific to PCI
13 power management refer to Documentation/driver-api/pm/devices.rst and
18 1. Hardware and Platform Support for PCI Power Management
19 2. PCI Subsystem and Device Power Management
20 3. PCI Device Drivers and Power Management
24 1. Hardware and Platform Support for PCI Power Management
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
[all …]
|
| D | apm-acpi.rst | 5 If you have a relatively recent x86 mobile, desktop, or server system,
6 odds are it supports either Advanced Power Management (APM) or
8 of the two technologies and puts power management in the hands of the
9 operating system, allowing for more intelligent power management than
12 The best way to determine which, if either, your system supports is to
21 simply cannot mix and match the two. Only one power management
24 User-space Daemons
25 ------------------
26 Both APM and ACPI rely on user-space daemons, apmd and acpid
29 and be sure that they are started sometime in the system boot process.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/pm/ |
| D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 Power Management Strategies
13 The Linux kernel supports two major high-level power management strategies.
15 One of them is based on using global low-power states of the whole system in
16 which user space code cannot be executed and the overall system activity is
17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
18 kernel puts the system into one of these states when requested by user space
19 and the system stays in it until a special signal is received from one of
21 user space code can run. Because sleep states are global and the whole system
23 :doc:`system-wide power management <system-wide>`.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 Power Management Strategies
13 The Linux kernel supports two major high-level power management strategies.
15 One of them is based on using global low-power states of the whole system in
16 which user space code cannot be executed and the overall system activity is
17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
18 kernel puts the system into one of these states when requested by user space
19 and the system stays in it until a special signal is received from one of
21 user space code can run. Because sleep states are global and the whole system
23 :doc:`system-wide power management <system-wide>`.
[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.
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
34 System Sleep model:
[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.
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
34 System Sleep model:
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/x86/ |
| D | amd_hsmp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Newer Fam19h EPYC server line of processors from AMD support system
8 management functionality via HSMP (Host System Management Port).
10 The Host System Management Port (HSMP) is an interface to provide
11 OS-level software with access to system management functions via a
15 "7 Host System Management Port (HSMP)" of the family/model PPR
16 Eg: https://www.amd.com/system/files/TechDocs/55898_B1_pub_0.50.zip
27 $ ls -al /dev/hsmp
28 crw-r--r-- 1 root root 10, 123 Jan 21 21:41 /dev/hsmp
38 In-kernel integration:
[all …]
|
| /kernel/linux/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
20 it supports, Performance management which is the ability to control
[all …]
|
| /kernel/linux/linux-6.6/drivers/firmware/arm_scmi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "ARM System Control and Management Interface Protocol"
5 tristate "ARM System Control and Management Interface (SCMI) Message Protocol"
8 ARM System Control and Management Interface (SCMI) protocol is a
9 set of operating system-independent software interfaces that are
10 used in system management. SCMI is extensible and currently provides
11 interfaces for: Discovery and self-description of the interfaces
12 it supports, Power domain management which is the ability to place
13 a given device or domain into the various power-saving states that
14 it supports, Performance management which is the ability to control
[all …]
|
| /kernel/linux/linux-6.6/Documentation/misc-devices/ |
| D | ibmvmc.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
4 IBM Virtual Management Channel Kernel Driver (IBMVMC)
21 https://openpowerfoundation.org/wp-content/uploads/2016/05/LoPAPR_DRAFT_v11_24March2016_cmt1.pdf
23 The Virtual Management Channel (VMC) is a logical device which provides an
24 interface between the hypervisor and a management partition. This interface
25 is like a message passing interface. This management partition is intended
26 to provide an alternative to systems that use a Hardware Management
27 Console (HMC) - based system management.
29 The primary hardware management solution that is developed by IBM relies
30 on an appliance server named the Hardware Management Console (HMC),
[all …]
|
| /kernel/linux/linux-5.10/Documentation/misc-devices/ |
| D | ibmvmc.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
4 IBM Virtual Management Channel Kernel Driver (IBMVMC)
21 https://openpowerfoundation.org/wp-content/uploads/2016/05/LoPAPR_DRAFT_v11_24March2016_cmt1.pdf
23 The Virtual Management Channel (VMC) is a logical device which provides an
24 interface between the hypervisor and a management partition. This interface
25 is like a message passing interface. This management partition is intended
26 to provide an alternative to systems that use a Hardware Management
27 Console (HMC) - based system management.
29 The primary hardware management solution that is developed by IBM relies
30 on an appliance server named the Hardware Management Console (HMC),
[all …]
|
| /kernel/linux/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
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
66 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | highres.rst | 8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
15 design of the Linux time(r) system before hrtimers and other building blocks
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
40 - time ordered enqueueing into a rb-tree
[all …]
|
| /kernel/linux/linux-6.6/Documentation/timers/ |
| D | highres.rst | 8 https://www.kernel.org/doc/ols/2006/ols2006v1-pages-333-346.pdf
11 http://www.cs.columbia.edu/~nahum/w6998/papers/ols2006-hrtimers-slides.pdf
15 design of the Linux time(r) system before hrtimers and other building blocks
23 - hrtimer base infrastructure
24 - timeofday and clock source management
25 - clock event management
26 - high resolution timer functionality
27 - dynamic ticks
31 ---------------------------
40 - time ordered enqueueing into a rb-tree
[all …]
|
| /kernel/linux/linux-5.10/arch/m68k/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
80 bool "MMU-based Paged Memory Management Support"
83 Select if you want MMU-based virtualised addressing space
84 support by paged memory management. If unsure, say 'Y'.
97 bool "kexec system call"
101 kexec is a system call that implements the ability to shutdown your
103 but it is independent of the system firmware. And like a reboot
106 The name comes from the similarity to the exec system call.
136 menu "Power management options"
139 bool "Power Management support"
[all …]
|
| /kernel/linux/linux-6.6/drivers/mfd/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
24 bool "Altera Arria10 DevKit System Resource chip"
29 Support for the Altera Arria10 DevKit MAX5 System Resource chip
35 bool "Altera SOCFPGA System Manager"
39 Select this to get System Manager support for all Altera branded
40 SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by
45 tristate "Active-semi ACT8945A"
50 Support for the ACT8945A PMIC from Active-semi. This device
51 features three step-down DC/DC converters and four low-dropout
67 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/keystone/ |
| D | knav-qmss.rst | 2 Texas Instruments Keystone Navigator Queue Management SubSystem driver
9 The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of
10 the main hardware sub system which forms the backbone of the Keystone
11 multi-core Navigator. QMSS consist of queue managers, packed-data structure
15 management of the packet queues. Packets are queued/de-queued by writing or
17 perform QMSS related functions like accumulation, QoS, or event management.
21 queue pool management (allocation, push, pop and notify) and descriptor
22 pool management.
29 Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
40 git://git.ti.com/keystone-rtos/qmss-lld.git
[all …]
|
| /kernel/linux/linux-5.10/Documentation/arm/keystone/ |
| D | knav-qmss.rst | 2 Texas Instruments Keystone Navigator Queue Management SubSystem driver
9 The QMSS (Queue Manager Sub System) found on Keystone SOCs is one of
10 the main hardware sub system which forms the backbone of the Keystone
11 multi-core Navigator. QMSS consist of queue managers, packed-data structure
15 management of the packet queues. Packets are queued/de-queued by writing or
17 perform QMSS related functions like accumulation, QoS, or event management.
21 queue pool management (allocation, push, pop and notify) and descriptor
22 pool management.
29 Documentation/devicetree/bindings/soc/ti/keystone-navigator-qmss.txt
40 git://git.ti.com/keystone-rtos/qmss-lld.git
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/adc/ |
| D | xilinx-xadc.txt | 4 as the UltraScale/UltraScale+ System Monitor.
14 The Xilinx System Monitor is an ADC that is found in the UltraScale and
15 UltraScale+ FPGAs from Xilinx. The System Monitor provides a DRP interface for
17 System Monitor through an AXI interface in the FPGA fabric. This IP core is
18 called the Xilinx System Management Wizard. This document describes the bindings
22 - compatible: Should be one of
23 * "xlnx,zynq-xadc-1.00.a": When using the ZYNQ device
25 * "xlnx,axi-xadc-1.00.a": When using the axi-xadc pcore to
27 * "xlnx,system-management-wiz-1.3": When using the
28 Xilinx System Management Wizard fabric IP core to access the
[all …]
|
12345678910>>...43