Searched +full:system +full:- +full:management (Results 1 – 25 of 1017) sorted by relevance
12345678910>>...41
| /linux-6.14.4/Documentation/userspace-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 …]
|
| /linux-6.14.4/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 1 What: /sys/devices/system/node/possible
3 Contact: Linux Memory Management list <linux-[email protected]>
7 What: /sys/devices/system/node/online
9 Contact: Linux Memory Management list <linux-[email protected]>
13 What: /sys/devices/system/node/has_normal_memory
15 Contact: Linux Memory Management list <linux-[email protected]>
19 What: /sys/devices/system/node/has_cpu
21 Contact: Linux Memory Management list <linux-[email protected]>
25 What: /sys/devices/system/node/has_high_memory
27 Contact: Linux Memory Management list <linux-[email protected]>
[all …]
|
| /linux-6.14.4/Documentation/power/ |
| D | pci.rst | 2 PCI Power Management
8 management. Based on previous work by Patrick Mochel <[email protected]>
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 …]
|
| /linux-6.14.4/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 …]
|
| /linux-6.14.4/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 …]
|
| /linux-6.14.4/drivers/platform/x86/amd/hsmp/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
17 Host System Management Port (HSMP) interface is a mailbox interface
18 between the x86 core and the System Management Unit (SMU) firmware.
20 system management functionality on EPYC and MI300A server CPUs
34 Host System Management Port (HSMP) interface is a mailbox interface
35 between the x86 core and the System Management Unit (SMU) firmware.
37 system management functionality on EPYC and MI300A server CPUs
|
| /linux-6.14.4/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 <[email protected]>, 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 …]
|
| /linux-6.14.4/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 …]
|
| /linux-6.14.4/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 …]
|
| /linux-6.14.4/Documentation/arch/x86/ |
| 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-6.14.4/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 …]
|
| /linux-6.14.4/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 …]
|
| /linux-6.14.4/drivers/mfd/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
36 bool "Altera Arria10 DevKit System Resource chip"
41 Support for the Altera Arria10 DevKit MAX5 System Resource chip
47 bool "Altera SOCFPGA System Manager"
51 Select this to get System Manager support for all Altera branded
52 SOCFPGAs. The SOCFPGA System Manager handles all SOCFPGAs by
57 tristate "Active-semi ACT8945A"
62 Support for the ACT8945A PMIC from Active-semi. This device
63 features three step-down DC/DC converters and four low-dropout
79 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
[all …]
|
| /linux-6.14.4/net/netlabel/ |
| 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-6.14.4/Documentation/driver-api/media/ |
| D | camera-sensor.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 This document covers the in-kernel APIs only. For the best practices on
12 CSI-2, parallel and BT.656 buses
13 --------------------------------
15 Please see :ref:`transmitter-receiver`.
18 ---------------
23 and the link frequency. The two parameters generally are obtained from system
28 used in the system. Using another frequency may cause harmful effects
29 elsewhere. Therefore only the pre-determined frequencies are configurable by the
35 Read the ``clock-frequency`` _DSD property to denote the frequency. The driver
[all …]
|
| /linux-6.14.4/Documentation/admin-guide/mm/ |
| 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-6.14.4/Documentation/devicetree/bindings/clock/ |
| 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 <[email protected]>
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 …]
|
| /linux-6.14.4/Documentation/driver-api/ |
| D | ipmi.rst | 7 The Intelligent Platform Management Interface, or IPMI, is a
8 standard for controlling intelligent devices that monitor a system.
9 It provides for dynamic discovery of sensors in the system and the
12 standardized database for field-replaceable units (FRUs) and a watchdog
16 system (called a Baseboard Management Controller, or BMC) and
17 management software that can use the IPMI system.
25 -------------
32 No matter what, you must pick 'IPMI top-level message handler' to use
35 The message handler does not provide any user-level interfaces.
40 The driver interface depends on your hardware. If your system
[all …]
|
| 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-6.14.4/Documentation/devicetree/bindings/mfd/ |
| D | stericsson,db8500-prcmu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mfd/stericsson,db8500-prcmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ST-Ericsson DB8500 PRCMU - Power Reset and Control Management Unit
10 - Linus Walleij <[email protected]>
13 The DB8500 Power Reset and Control Management Unit is an XP70 8-bit
14 microprocessor that is embedded in the always-on power domain of the
20 pattern: '^prcmu@[0-9a-f]+$'
23 description: The device is compatible both to the device-specific
[all …]
|
| /linux-6.14.4/drivers/cxl/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 Say 'y' to enable support for the configuration and management of
25 The CXL specification defines a "CXL memory device" sub-class in the
28 memory to be mapped into the system address map (Host-managed Device
33 and management primarily via the mailbox interface. See Chapter 2.3
69 (https://www.computeexpresslink.org/spec-landing). The CXL core
71 hierarchy to map regions that represent System RAM, or Persistent
83 managed via a bridge driver from CXL to the LIBNVDIMM system
94 The CXL.mem protocol allows a device to act as a provider of "System
97 known as HDM "Host-managed Device Memory".
[all …]
|
| /linux-6.14.4/Documentation/driver-api/usb/ |
| 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-6.14.4/drivers/thermal/tegra/ |
| 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-6.14.4/kernel/power/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
7 Allow the system to enter sleep states in which main memory is
9 suspend-to-RAM state (e.g. the ACPI S3 state).
30 user-space before invoking suspend. There's a run-time switch
32 This setting changes the default for the run-tim switch. Say Y
48 system and powers it off; and restores that checkpoint on reboot.
60 for suspend states like suspend-to-RAM (STR) often don't work very
72 <file:Documentation/power/swsusp-and-swap-files.rst>).
122 The default resume partition is the partition that the suspend-
123 to-disk implementation will look for a suspended disk image.
[all …]
|
12345678910>>...41