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
36 standard for registering callbacks from the platform firmware
61 bool "Add firmware-provided memory map to sysfs" if EXPERT
64 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
68 See also Documentation/ABI/testing/sysfs-firmware-memmap.
75 Say Y here if you want to query SMBIOS/DMI system identification
77 DMI-based module auto-loading.
87 under /sys/firmware/dmi when this option is enabled and
94 bool "iSCSI Boot Firmware Table Attributes"
99 in which the ISCSI Boot Firmware Table (iBFT) resides. This
100 is necessary for iSCSI Boot Firmware Table Attributes module to work
104 tristate "iSCSI Boot Firmware Table Attributes module"
111 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
112 detect iSCSI boot parameters dynamically during system boot, say Y.
116 tristate "Raspberry Pi Firmware Driver"
119 This option enables support for communicating with the firmware on the
128 Say Y or M here to enable the exporting of the QEMU firmware
130 found under /sys/firmware/fw_cfg when this option is enabled
140 may crash your system.
155 tristate "Intel Stratix10 Remote System Update"
158 The Intel Remote System Update (RSU) driver exposes interfaces
165 risk of corrupting the bitstream storage and bricking the system.
177 between host AP (Linux) and the firmware running on ADSP.
187 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
192 bootloader or kernel can show basic video-output during boot for
193 user-guidance and debugging. Historically, x86 used the VESA BIOS
194 Extensions and EFI-framebuffers for this, which are mostly limited
197 framebuffers so the new generic system-framebuffer drivers can be
201 If this option is not selected, all system framebuffers are always
205 not be able to pick up generic system framebuffers if this option
208 with generic system framebuffers. But you should still keep vesafb
209 and others enabled as fallback if a system framebuffer is
215 tristate "Always-On firmware protocol"
220 managed by the E902 core. Firmware running on this core communicates with
221 the kernel through the Always-On protocol, using hardware mailbox as a medium.
225 tristate "TI System Control Interface (TISCI) Message Protocol"
229 TI System Control Interface (TISCI) Message Protocol is used to manage
230 compute systems such as ARM, DSP etc with the system controller in
231 complex System on Chip(SoC) such as those found on certain keystone
234 System controller provides various facilities including power
238 provided by the system controller.
244 Some devices (including most early Tegra-based consumer devices on
251 comments in linux/firmware/trusted_foundations.h or the device tree
252 bindings for "tlm,trusted-foundations" for details on how to use it.
257 tristate "Turris Mox rWTM secure firmware driver"
264 This driver communicates with the firmware on the Cortex-M3 secure
287 source "drivers/firmware/arm_ffa/Kconfig"
288 source "drivers/firmware/broadcom/Kconfig"
289 source "drivers/firmware/cirrus/Kconfig"
290 source "drivers/firmware/google/Kconfig"
291 source "drivers/firmware/efi/Kconfig"
292 source "drivers/firmware/imx/Kconfig"
293 source "drivers/firmware/meson/Kconfig"
294 source "drivers/firmware/microchip/Kconfig"
295 source "drivers/firmware/psci/Kconfig"
296 source "drivers/firmware/qcom/Kconfig"
297 source "drivers/firmware/samsung/Kconfig"
298 source "drivers/firmware/smccc/Kconfig"
299 source "drivers/firmware/tegra/Kconfig"
300 source "drivers/firmware/xilinx/Kconfig"