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
49           obscure configurations. Most disk controller BIOS vendors do
62     bool "Add firmware-provided memory map to sysfs" if EXPERT
65       Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
69       See also Documentation/ABI/testing/sysfs-firmware-memmap.
76 	  Say Y here if you want to query SMBIOS/DMI system identification
78 	  DMI-based module auto-loading.
113 	  detect iSCSI boot parameters dynamically during system boot, say Y.
141 	  may crash your system.
156 	tristate "Intel Stratix10 Remote System Update"
159 	  The Intel Remote System Update (RSU) driver exposes interfaces
166 	  risk of corrupting the bitstream storage and bricking the system.
188 	bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
193 	  bootloader or kernel can show basic video-output during boot for
194 	  user-guidance and debugging. Historically, x86 used the VESA BIOS
195 	  Extensions and EFI-framebuffers for this, which are mostly limited
198 	  framebuffers so the new generic system-framebuffer drivers can be
202 	  If this option is not selected, all system framebuffers are always
206 	  not be able to pick up generic system framebuffers if this option
209 	  with generic system framebuffers. But you should still keep vesafb
210 	  and others enabled as fallback if a system framebuffer is
216 	tristate "TI System Control Interface (TISCI) Message Protocol"
219 	  TI System Control Interface (TISCI) Message Protocol is used to manage
220 	  compute systems such as ARM, DSP etc with the system controller in
221 	  complex System on Chip(SoC) such as those found on certain keystone
224 	  System controller provides various facilities including power
228 	  provided by the system controller.
234 	  Some devices (including most early Tegra-based consumer devices on
242 	  bindings for "tlm,trusted-foundations" for details on how to use it.
254 	  This driver communicates with the firmware on the Cortex-M3 secure