| /linux/Documentation/userspace-api/ |
| H A 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 …]
|
| /linux/drivers/firmware/arm_scmi/ |
| H A 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 …]
|
| /linux/Documentation/admin-guide/pm/ |
| H A 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 …]
|
| /linux/drivers/firmware/imx/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
18 The System Controller Firmware (SCFW) is a low-level system function
19 which runs on a dedicated Cortex-M core to provide power, clock, and
20 resource management. It exists on some i.MX8 processors. e.g. i.MX8QM
31 The System Controller Management Interface firmware (SCMI FW) is
32 a low-level system function which runs on a dedicated Cortex-M
33 core that could provide cpu management features.
42 The System Controller Management Interface firmware (SCMI FW) is
43 a low-level system function which runs on a dedicated Cortex-M
44 core that could provide Logical Machine management features.
[all …]
|
| /linux/drivers/platform/x86/amd/hsmp/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
18 Host System Management Port (HSMP) interface is a mailbox interface
19 between the x86 core and the System Management Unit (SMU) firmware.
21 system management functionality on EPYC and MI300A server CPUs
36 Host System Management Port (HSMP) interface is a mailbox interface
37 between the x86 core and the System Management Unit (SMU) firmware.
39 system management functionality on EPYC and MI300A server CPUs
|
| /linux/Documentation/misc-devices/ |
| H A 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 …]
|
| /linux/Documentation/timers/ |
| H A 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 …]
|
| /linux/Documentation/devicetree/bindings/iio/adc/ |
| H A 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 …]
|
| /linux/Documentation/arch/arm/keystone/ |
| H A 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 …]
|
| /linux/Documentation/power/ |
| H A 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 …]
|
| /linux/Documentation/arch/x86/ |
| H A D | amd_hsmp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Newer Fam19h(model 0x00-0x1f, 0x30-0x3f, 0x90-0x9f, 0xa0-0xaf),
8 Fam1Ah(model 0x00-0x1f) EPYC server line of processors from AMD support
9 system management functionality via HSMP (Host System Management Port).
11 The Host System Management Port (HSMP) is an interface to provide
12 OS-level software with access to system management functions via a
16 "7 Host System Management Port (HSMP)" of the family/model PPR
17 Eg: https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/programmer-references/5589…
40 $ ls -al /dev/hsmp
41 crw-r--r-- 1 root root 10, 123 Jan 21 21:41 /dev/hsmp
[all …]
|
| /linux/net/netlabel/ |
| H A D | netlabel_mgmt.h | 1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * NetLabel Management Support
5 * This file defines the management functions for the NetLabel system. The
6 * NetLabel system manages static and dynamic label mappings for network
9 * Author: Paul Moore <paul@paul-moore.com>
13 * (c) Copyright Hewlett-Packard Development Company, L.P., 2006
23 * The following NetLabel payloads are supported by the management interface.
26 * Sent by an application to add a domain mapping to the NetLabel system.
54 * system.
91 * system.
[all …]
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | index.rst | 2 Memory Management
5 Linux memory management subsystem is responsible, as the name implies,
6 for managing the memory in the system. This includes implementation of
11 Linux memory management is a complex system with many configurable
14 are described in Documentation/admin-guide/sysctl/vm.rst and in `man 5 proc`_.
16 .. _man 5 proc: http://man7.org/linux/man-pages/man5/proc.5.html
18 Linux memory management has its own jargon and if you are not yet
19 familiar with it, consider reading Documentation/admin-guide/mm/concepts.rst.
22 the Linux memory management.
33 memory-hotplug
[all …]
|
| /linux/Documentation/devicetree/bindings/clock/ |
| H A D | imx7ulp-scg-clock.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/imx7ulp-scg-clock.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale i.MX7ULP System Clock Generation (SCG) modules Clock Controller
10 - A.s. Dong <aisheng.dong@nxp.com>
13 i.MX7ULP Clock functions are under joint control of the System
19 domains, such as the System Oscillator clock, the Slow IRC (SIRC),
21 management are separated and contained within each domain.
23 M4 clock management consists of SCG0, PCC0, PCC1, and CMC0 modules.
[all …]
|
| H A D | imx7ulp-pcc-clock.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/clock/imx7ulp-pcc-clock.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - A.s. Dong <aisheng.dong@nxp.com>
13 i.MX7ULP Clock functions are under joint control of the System
19 domains, such as the System Oscillator clock, the Slow IRC (SIRC),
21 management are separated and contained within each domain.
23 M4 clock management consists of SCG0, PCC0, PCC1, and CMC0 modules.
24 A7 clock management consists of SCG1, PCC2, PCC3, and CMC1 modules.
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm-mempolicy-weighted-interleave | 3 Contact: Linux memory management mailing list <linux-mm@kvack.org>
8 Contact: Linux memory management mailing list <linux-mm@kvack.org>
24 empty string, ...) will return -EINVAL.
27 switch the system to manual mode as well.
31 Contact: Linux memory management mailing list <linux-mm@kvack.org>
32 Description: Auto-weighting configuration interface
35 that the system is in auto mode, and a 'false' indicates that
36 the system is in manual mode.
38 In auto mode, all node weights are re-calculated and overwritten
51 return -EINVAL.
[all …]
|
| H A D | sysfs-devices-system-cpu | 1 What: /sys/devices/system/cpu/
2 Date: pre-git history
3 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
10 /sys/devices/system/cpu/cpuX/
12 What: /sys/devices/system/cpu/kernel_max
13 /sys/devices/system/cpu/offline
14 /sys/devices/system/cpu/online
15 /sys/devices/system/cpu/possible
16 /sys/devices/system/cpu/present
18 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
[all …]
|
| /linux/Documentation/driver-api/usb/ |
| H A D | power-management.rst | 1 .. _usb-power-management:
3 Power Management for USB
7 :Date: Last-updated: February 2014
11 ---------
12 * What is Power Management?
17 * Changing the default idle-delay time
19 * The driver interface for Power Management
23 * Interaction between dynamic PM and system PM
30 What is Power Management?
31 -------------------------
[all …]
|
| /linux/drivers/firmware/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
12 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
16 System Control and Power Interface (SCPI) Message Protocol is
18 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
19 provides a mechanism for inter-processor communication between SCP
22 SCP controls most of the power management on the Application
23 Processors. It offers control and management of: the core/cluster
25 certain system clocks configuration, thermal sensors and many
61 bool "Add firmware-provided memory map to sysfs" if EXPERT
[all …]
|
| /linux/Documentation/driver-api/ |
| H A D | ipmb.rst | 5 The Intelligent Platform Management Bus or IPMB, is an
8 between the baseboard management (BMC) and chassis electronics.
12 The devices using the IPMB are usually management
13 controllers that perform management functions such as servicing
15 hot-swapping disk drivers in the system chassis, etc...
17 When an IPMB is implemented in the system, the BMC serves as
18 a controller to give system software access to the IPMB. The BMC
19 sends IPMI requests to a device (usually a Satellite Management
27 ----------------------------
29 ipmb-dev-int - This is the driver needed on a Satellite MC to
[all …]
|
| /linux/drivers/thermal/tegra/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
6 tristate "Tegra SOCTHERM thermal management"
8 Enable this option for integrated thermal management support on NVIDIA
9 Tegra systems-on-chip. The driver supports four thermal zones
18 Enable this option for support for sensing system temperature of NVIDIA
19 Tegra systems-on-chip with the BPMP coprocessor (Tegra186).
25 Enable this option to support thermal management of NVIDIA Tegra30
26 system-on-chip.
|
| /linux/Documentation/core-api/ |
| H A D | boot-time-mm.rst | 2 Boot time memory management
5 Early system initialization cannot use "normal" memory management
11 boot time memory management. The architecture specific initialization
15 Once the early memory management is available it offers a variety of
18 particular node in a NUMA system. There are API variants that panic
26 .. kernel-doc:: mm/memblock.c
39 .. kernel-doc:: include/linux/memblock.h
40 .. kernel-doc:: mm/memblock.c
|
| /linux/Documentation/devicetree/bindings/reset/ |
| H A D | ti,sci-reset.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/reset/ti,sci-reset.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI-SCI reset controller
10 - Nishanth Menon <nm@ti.com>
13 Some TI SoCs contain a system controller (like the Power Management Micro
16 between the host processor running an OS and the system controller happens
17 through a protocol called TI System Control Interface (TI-SCI protocol).
20 management of various hardware modules present on the SoC. Must be a child
[all …]
|
| /linux/drivers/platform/x86/dell/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
10 Dell x86 platforms, including vendor-specific laptop extension drivers.
31 AlienFX USB MCU such as the X51 and X51-R2.
53 tristate "Dell Systems Management Base Driver"
57 The Dell Systems Management Base Driver provides a sysfs interface
58 for systems management software to perform System Management
59 Interrupts (SMIs) and Host Control Actions (system power cycle or
62 See <file:Documentation/userspace-api/dcdbas.rst> for more details on the driver
63 and the Dell systems on which Dell systems management software makes
67 management software such as Dell OpenManage.
[all …]
|
| /linux/drivers/soc/ti/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
12 tristate "Keystone Queue Manager Sub System"
17 is responsible for accelerating management of the packet queues.
18 Packets are queued/de-queued by writing/reading descriptor address
29 Queue Manager Sub System.
34 tristate "AMx3 Power Management"
38 Enable power management on AM335x and AM437x. Required for suspend to mem
40 c-states on AM335x. Also required for rtc and ddr in self-refresh low
44 tristate "TI AMx3 Wkup-M3 IPC Driver"
54 tristate "K3 Ring accelerator Sub System"
[all …]
|