Lines Matching +full:secure +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"
19 provides a mechanism for inter-processor communication between SCP
38 enabled or disabled via the SCP firmware
45 standard for registering callbacks from the platform firmware
70 bool "Add firmware-provided memory map to sysfs" if EXPERT
73 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
77 See also Documentation/ABI/testing/sysfs-firmware-memmap.
84 If your firmware supplies the PCDP table, and you want to
88 If your firmware supplies the HCDP table, and you want to
110 DMI-based module auto-loading.
120 under /sys/firmware/dmi when this option is enabled and
127 bool "iSCSI Boot Firmware Table Attributes"
132 in which the ISCSI Boot Firmware Table (iBFT) resides. This
133 is necessary for iSCSI Boot Firmware Table Attributes module to work
137 tristate "iSCSI Boot Firmware Table Attributes module"
144 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
149 tristate "Raspberry Pi Firmware Driver"
152 This option enables support for communicating with the firmware on the
161 Say Y or M here to enable the exporting of the QEMU firmware
163 found under /sys/firmware/fw_cfg when this option is enabled
182 and manages secure monitor call to communicate with secure monitor
183 software at secure monitor exception level.
213 warm-restart enter a special debug mode that allows the user to
229 bootloader or kernel can show basic video-output during boot for
230 user-guidance and debugging. Historically, x86 used the VESA BIOS
231 Extensions and EFI-framebuffers for this, which are mostly limited
234 framebuffers so the new generic system-framebuffer drivers can be
267 bool "Trusted Foundations secure monitor support"
270 Some devices (including most early Tegra-based consumer devices on
271 the market) are booted with the Trusted Foundations secure monitor
272 active, requiring some core operations to be performed by the secure
275 This option allows the kernel to invoke the secure monitor whenever
277 comments in linux/firmware/trusted_foundations.h or the device tree
278 bindings for "tlm,trusted-foundations" for details on how to use it.
283 tristate "Turris Mox rWTM secure firmware driver"
290 This driver communicates with the firmware on the Cortex-M3 secure
296 source "drivers/firmware/arm_ffa/Kconfig"
297 source "drivers/firmware/broadcom/Kconfig"
298 source "drivers/firmware/google/Kconfig"
299 source "drivers/firmware/efi/Kconfig"
300 source "drivers/firmware/imx/Kconfig"
301 source "drivers/firmware/meson/Kconfig"
302 source "drivers/firmware/psci/Kconfig"
303 source "drivers/firmware/smccc/Kconfig"
304 source "drivers/firmware/tegra/Kconfig"
305 source "drivers/firmware/xilinx/Kconfig"