Lines Matching +full:system +full:- +full:power +full:- +full:controller

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
24 power states, various power domain DVFS including the core/cluster,
25 certain system clocks configuration, thermal sensors and many
32 tristate "SCPI power domain driver"
37 This enables support for the SCPI power domains which can be
58 obscure configurations. Most disk controller BIOS vendors do
71 bool "Add firmware-provided memory map to sysfs" if EXPERT
74 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
78 See also Documentation/ABI/testing/sysfs-firmware-memmap.
109 Say Y here if you want to query SMBIOS/DMI system identification
111 DMI-based module auto-loading.
146 detect iSCSI boot parameters dynamically during system boot, say Y.
174 may crash your system.
189 tristate "Intel Stratix10 Remote System Update"
192 The Intel Remote System Update (RSU) driver exposes interfaces
199 risk of corrupting the bitstream storage and bricking the system.
223 warm-restart enter a special debug mode that allows the user to
234 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
239 bootloader or kernel can show basic video-output during boot for
240 user-guidance and debugging. Historically, x86 used the VESA BIOS
241 Extensions and EFI-framebuffers for this, which are mostly limited
244 framebuffers so the new generic system-framebuffer drivers can be
248 If this option is not selected, all system framebuffers are always
252 not be able to pick up generic system framebuffers if this option
255 with generic system framebuffers. But you should still keep vesafb
256 and others enabled as fallback if a system framebuffer is
262 tristate "TI System Control Interface (TISCI) Message Protocol"
265 TI System Control Interface (TISCI) Message Protocol is used to manage
266 compute systems such as ARM, DSP etc with the system controller in
267 complex System on Chip(SoC) such as those found on certain keystone
270 System controller provides various facilities including power
274 provided by the system controller.
280 Some devices (including most early Tegra-based consumer devices on
288 bindings for "tlm,trusted-foundations" for details on how to use it.
300 This driver communicates with the firmware on the Cortex-M3 secure