Searched full:management (Results 1 – 25 of 3121) sorted by relevance
12345678910>>...125
| /Linux-v6.1/Documentation/misc-devices/ |
| D | ibmvmc.rst | 4 IBM Virtual Management Channel Kernel Driver (IBMVMC)
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),
35 Management Application
38 In the management partition, a management application exists which enables
[all …]
|
| /Linux-v6.1/drivers/soc/xilinx/ |
| D | Kconfig | 5 bool "Enable Xilinx Zynq MPSoC Power Management driver"
11 Say yes to enable power management support for ZyqnMP SoC.
13 management request to firmware. It registers isr to handle
14 power management callbacks from firmware. It registers mailbox client
15 to handle power management callbacks from firmware.
25 Say yes to enable device power management through PM domains
29 bool "Enable Xilinx Event Management Driver"
33 Say yes to enable event management support for Xilinx.
35 management request to firmware.
|
| /Linux-v6.1/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
32 The driver creates the following sysfs entries for systems management
33 software to perform these system management interrupts::
40 Systems management software must perform the following steps to execute
[all …]
|
| /Linux-v6.1/drivers/net/wwan/iosm/ |
| D | iosm_ipc_pm.h | 62 * power management state.
85 * struct iosm_pm - Power management instance
92 * @pm_cond: Conditions for power management
93 * @ap_state: Current power management state, the
113 * enum ipc_pm_unit - Power management units.
125 * ipc_pm_init - Allocate power management component
131 * ipc_pm_deinit - Free power management component, invalidating its pointer.
141 * @ipc_pm: Pointer to power management component
151 * @ipc_pm: Pointer to power management component
159 * @ipc_pm: Pointer to power management component
[all …]
|
| /Linux-v6.1/drivers/mfd/ |
| D | Kconfig | 81 tristate "ams AS3722 Power Management IC"
97 Multifunction Power Management IC. This includes
193 management ICs (PMICs) controlled with I2C.
209 management ICs (PMICs) controlled with RSB.
305 ARAVA) and DA9034 (a.k.a MICCO), these are Power Management IC
347 a Power Management IC. This driver provides common support for
474 management functions.
588 System Management Bus and General Purpose I/O.
601 thermal, charger and related power management functions
616 thermal, charger and related power management functions
[all …]
|
| /Linux-v6.1/drivers/fpga/ |
| D | Kconfig | 158 devices (e.g. FPGA Management Engine, Port and Accelerator
169 The FPGA Management Engine (FME) is a feature device implemented
172 FPGA platform level management features. There shall be one FME
179 Say Y to enable FPGA Manager driver for FPGA Management Engine.
185 Say Y to enable FPGA Bridge driver for FPGA Management Engine.
191 Say Y to enable FPGA Region driver for FPGA Management Engine.
198 implements AFU and Port management features. A User AFU connects
211 the card's BMC (Board Management Controller).
222 management functions such as FPGA partial reconfiguration, power
223 management and virtualization with DFL framework and DFL feature
[all …]
|
| /Linux-v6.1/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 3 Contact: Linux Memory Management list <linux-mm@kvack.org>
9 Contact: Linux Memory Management list <linux-mm@kvack.org>
15 Contact: Linux Memory Management list <linux-mm@kvack.org>
21 Contact: Linux Memory Management list <linux-mm@kvack.org>
27 Contact: Linux Memory Management list <linux-mm@kvack.org>
34 Contact: Linux Memory Management list <linux-mm@kvack.org>
42 Contact: Linux Memory Management list <linux-mm@kvack.org>
48 Contact: Linux Memory Management list <linux-mm@kvack.org>
54 Contact: Linux Memory Management list <linux-mm@kvack.org>
61 Contact: Linux Memory Management list <linux-mm@kvack.org>
[all …]
|
| /Linux-v6.1/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
30 In general, power management is a feature allowing one to save energy by putting
[all …]
|
| /Linux-v6.1/Documentation/driver-api/xilinx/ |
| D | eemi.rst | 10 used by any driver to communicate with PMC(Platform Management Controller).
12 Embedded Energy Management Interface (EEMI)
14 The embedded energy management interface is used to allow software
16 device to communicate with a power management controller (PMC) on a
17 device to issue or respond to power management requests.
39 [0] Embedded Energy Management Interface (EEMI) API guide:
|
| /Linux-v6.1/drivers/staging/greybus/Documentation/firmware/ |
| D | firmware-management | 2 Firmware Management
11 Firmware Management Protocol. To support Firmware Management by the AP, the
12 Interface Manifest shall at least contain the Firmware Management Bundle and a
13 Firmware Management Protocol CPort within it.
18 For example, this is how the Firmware Management part of the Interface Manifest
21 ; Firmware Management Bundle (Bundle 1):
25 ; (Mandatory) Firmware Management Protocol on CPort 1
46 Sysfs Interfaces - Firmware Management
49 The Firmware Management Protocol interacts with Userspace using the character
58 firmware-management for a particular interface.
[all …]
|
| /Linux-v6.1/drivers/firmware/arm_scmi/ |
| D | Kconfig | 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
10 used in system management. SCMI is extensible and currently provides
12 it supports, Power domain management which is the ability to place
14 it supports, Performance management which is the ability to control
17 management which is the ability to set and inquire rates on platform
18 managed clocks and Sensor management which is the ability to read
|
| /Linux-v6.1/Documentation/driver-api/mei/ |
| D | iamt.rst | 3 Intel(R) Active Management Technology (Intel AMT)
7 Active Management Technology (Intel AMT) implemented in firmware running on
22 on policies set by a remote management console
23 - IDE device redirection from remote management console
26 starting with Release 6.0) over HTTP/S or WS-Management protocol over
27 HTTP/S that are received from a remote management console application.
36 1) Intel Local Management Service (Intel LMS)
40 over HTTP (deprecated starting with Release 6.0) or with WS-Management over
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| D | sysfs-class-scsi_host | 37 (interface) power management.
46 max_performance: Generally, this means no power management.
48 management.
56 management) on top, which makes it match the Windows IRST (Intel
70 em_message: (RW) Enclosure management support. For the LED
78 em_message_type: (RO) Displays the current enclosure management
104 (RW) Allows access to AHCI EM (enclosure management) buffer
119 (RO) Displays supported enclosure management message types.
|
| /Linux-v6.1/Documentation/admin-guide/mm/ |
| D | index.rst | 2 Memory Management
5 Linux memory management subsystem is responsible, as the name implies,
11 Linux memory management is a complex system with many configurable
18 Linux memory management has its own jargon and if you are not yet
23 the Linux memory management.
|
| /Linux-v6.1/drivers/soc/fsl/ |
| D | Kconfig | 15 The global utilities block controls power management, I/O device
31 buffer management facilities for software to interact with
43 which can be used to dump the Management Complex and AIOP
51 (Run Control and Power Management), which performs all device-level
52 tasks associated with power management, such as wakeup source control.
|
| /Linux-v6.1/drivers/base/power/ |
| D | clock_ops.c | 233 * pm_clk_add - Start using a device clock for power management.
234 * @dev: Device whose clock is going to be used for power management.
238 * the power management of @dev.
247 * pm_clk_add_clk - Start using a device clock for power management.
248 * @dev: Device whose clock is going to be used for power management.
251 * Add the clock to the list of clocks used for the power management of @dev.
252 * The power-management code will take control of the clock reference, so
264 * of_pm_clk_add_clk - Start using a device clock for power management.
265 * @dev: Device whose clock is going to be used for power management.
266 * @name: Name of clock that is going to be used for power management.
[all …]
|
| /Linux-v6.1/Documentation/admin-guide/pm/ |
| D | strategies.rst | 5 Power Management Strategies
13 The Linux kernel supports two major high-level power management strategies.
23 :doc:`system-wide power management <system-wide>`.
25 The other strategy, referred to as the :doc:`working-state power management
49 Moreover, the two power management strategies address different usage scenarios.
54 use the working-state power management in case it becomes idle, because the user
|
| /Linux-v6.1/Documentation/driver-api/pm/ |
| D | devices.rst | 7 Device Power Management Basics
18 management (PM) code is also driver-specific. Most drivers will do very
23 power management goals, emphasizing the models and interfaces that are
28 Two Models for Device Power Management
53 Runtime Power Management model:
56 running, independently of other power management activity in principle.
67 the PM core are involved in runtime power management. As in the system
68 sleep power management case, they need to collaborate by implementing
93 management of devices they are concerned with. These interfaces cover both
94 system sleep and runtime power management.
[all …]
|
| /Linux-v6.1/Documentation/scsi/ |
| D | libsas.rst | 7 The SAS Layer is a management infrastructure which manages
11 phy/OOB/link management, the SAS layer is concerned with:
13 * SAS Phy/Port/HA event management (LLDD generates,
15 * SAS Port management (creation/destruction),
17 * SAS Domain device management,
21 * Expander management and exporting expander control
25 phy/OOB management, and vendor specific tasks and generates
205 Management Functions (TMFs) described in SAM::
207 /* Task Management Functions. Must be called from process context. */
217 Port and Adapter management::
[all …]
|
| /Linux-v6.1/Documentation/networking/devlink/ |
| D | devlink-port.rst | 138 Subfunction management is done using devlink port user interface.
139 User performs setup on the subfunction management device.
145 kernel code calls down to subfunction management driver (devlink ops) and asks
162 activation, subfunction management driver asks the subfunction management
167 Rate object management
225 * - ``Subfunction management device``
226 - A PCI physical function that supports subfunction management.
227 * - ``Subfunction management driver``
229 subfunction management using devlink port interface.
232 devices. In most cases it is same as subfunction management driver. When
[all …]
|
| /Linux-v6.1/arch/m68k/ |
| D | Kconfig | 72 bool "MMU-based Paged Memory Management Support"
76 support by paged memory management. If unsure, say 'Y'.
128 menu "Power management options"
131 bool "Power Management support"
133 Support processor power management modes
|
| /Linux-v6.1/Documentation/devicetree/bindings/arm/marvell/ |
| D | armada-37xx.txt | 1 Power management
4 For power management (particularly DVFS and AVS), the North Bridge
5 Power Management component is needed:
10 Power Management
|
| /Linux-v6.1/Documentation/x86/ |
| D | amd_hsmp.rst | 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
81 "7 Host System Management Port (HSMP)" of the respective family/model PPR
|
| /Linux-v6.1/drivers/infiniband/ulp/srpt/ |
| D | ib_dm_mad.h | 53 * See also the Device Management chapter, section 16.3.3 Attributes,
54 * table 279 Device Management Attributes in the InfiniBand
68 * Structure of management datagram sent by the SRP target implementation.
69 * Contains a management datagram header, reliable multi-packet transaction
72 * management datagrams.
75 * - The maximum supported size for a management datagram when not using RMPP
|
| /Linux-v6.1/drivers/platform/x86/dell/ |
| D | Kconfig | 31 tristate "Dell Systems Management Base Driver"
35 The Dell Systems Management Base Driver provides a sysfs interface
36 for systems management software to perform System Management
41 and the Dell systems on which Dell systems management software makes
45 management software such as Dell OpenManage.
202 tristate "Dell WMI-based Systems management driver"
|
12345678910>>...125
