Lines Matching +full:system +full:- +full:firmware
1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
7 menu "Firmware Drivers"
9 source "drivers/firmware/arm_scmi/Kconfig"
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
25 certain system clocks configuration, thermal sensors and many
38 enabled or disabled via the SCP firmware
46 standard for registering callbacks from the platform firmware
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.
85 If your firmware supplies the PCDP table, and you want to
89 If your firmware supplies the HCDP table, and you want to
109 Say Y here if you want to query SMBIOS/DMI system identification
111 DMI-based module auto-loading.
121 under /sys/firmware/dmi when this option is enabled and
128 bool "iSCSI Boot Firmware Table Attributes"
133 in which the ISCSI Boot Firmware Table (iBFT) resides. This
134 is necessary for iSCSI Boot Firmware Table Attributes module to work
138 tristate "iSCSI Boot Firmware Table Attributes module"
145 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
146 detect iSCSI boot parameters dynamically during system boot, say Y.
150 tristate "Raspberry Pi Firmware Driver"
153 This option enables support for communicating with the firmware on the
162 Say Y or M here to enable the exporting of the QEMU firmware
164 found under /sys/firmware/fw_cfg when this option is enabled
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.
211 between host AP (Linux) and the firmware running on ADSP.
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
287 comments in linux/firmware/trusted_foundations.h or the device tree
288 bindings for "tlm,trusted-foundations" for details on how to use it.
293 tristate "Turris Mox rWTM secure firmware driver"
300 This driver communicates with the firmware on the Cortex-M3 secure
306 source "drivers/firmware/arm_ffa/Kconfig"
307 source "drivers/firmware/broadcom/Kconfig"
308 source "drivers/firmware/cirrus/Kconfig"
309 source "drivers/firmware/google/Kconfig"
310 source "drivers/firmware/efi/Kconfig"
311 source "drivers/firmware/imx/Kconfig"
312 source "drivers/firmware/meson/Kconfig"
313 source "drivers/firmware/psci/Kconfig"
314 source "drivers/firmware/smccc/Kconfig"
315 source "drivers/firmware/tegra/Kconfig"
316 source "drivers/firmware/xilinx/Kconfig"