1# SPDX-License-Identifier: GPL-2.0-only 2# 3# For a description of the syntax of this configuration file, 4# see Documentation/kbuild/kconfig-language.rst. 5# 6 7menu "Firmware Drivers" 8 9source "drivers/firmware/arm_scmi/Kconfig" 10 11config ARM_SCPI_PROTOCOL 12 tristate "ARM System Control and Power Interface (SCPI) Message Protocol" 13 depends on ARM || ARM64 || COMPILE_TEST 14 depends on MAILBOX 15 help 16 System Control and Power Interface (SCPI) Message Protocol is 17 defined for the purpose of communication between the Application 18 Cores(AP) and the System Control Processor(SCP). The MHU peripheral 19 provides a mechanism for inter-processor communication between SCP 20 and AP. 21 22 SCP controls most of the power management on the Application 23 Processors. It offers control and management of: the core/cluster 24 power states, various power domain DVFS including the core/cluster, 25 certain system clocks configuration, thermal sensors and many 26 others. 27 28 This protocol library provides interface for all the client drivers 29 making use of the features offered by the SCP. 30 31config ARM_SDE_INTERFACE 32 bool "ARM Software Delegated Exception Interface (SDEI)" 33 depends on ARM64 34 help 35 The Software Delegated Exception Interface (SDEI) is an ARM 36 standard for registering callbacks from the platform firmware 37 into the OS. This is typically used to implement RAS notifications. 38 39config EDD 40 tristate "BIOS Enhanced Disk Drive calls determine boot disk" 41 depends on X86 42 help 43 Say Y or M here if you want to enable BIOS Enhanced Disk Drive 44 Services real mode BIOS calls to determine which disk 45 BIOS tries boot from. This information is then exported via sysfs. 46 47 This option is experimental and is known to fail to boot on some 48 obscure configurations. Most disk controller BIOS vendors do 49 not yet implement this feature. 50 51config EDD_OFF 52 bool "Sets default behavior for EDD detection to off" 53 depends on EDD 54 default n 55 help 56 Say Y if you want EDD disabled by default, even though it is compiled into the 57 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set 58 using the kernel parameter 'edd={on|skipmbr|off}'. 59 60config FIRMWARE_MEMMAP 61 bool "Add firmware-provided memory map to sysfs" if EXPERT 62 default X86 63 help 64 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap. 65 That memory map is used for example by kexec to set up parameter area 66 for the next kernel, but can also be used for debugging purposes. 67 68 See also Documentation/ABI/testing/sysfs-firmware-memmap. 69 70config DMIID 71 bool "Export DMI identification via sysfs to userspace" 72 depends on DMI 73 default y 74 help 75 Say Y here if you want to query SMBIOS/DMI system identification 76 information from userspace through /sys/class/dmi/id/ or if you want 77 DMI-based module auto-loading. 78 79config DMI_SYSFS 80 tristate "DMI table support in sysfs" 81 depends on SYSFS && DMI 82 default n 83 help 84 Say Y or M here to enable the exporting of the raw DMI table 85 data via sysfs. This is useful for consuming the data without 86 requiring any access to /dev/mem at all. Tables are found 87 under /sys/firmware/dmi when this option is enabled and 88 loaded. 89 90config DMI_SCAN_MACHINE_NON_EFI_FALLBACK 91 bool 92 93config ISCSI_IBFT_FIND 94 bool "iSCSI Boot Firmware Table Attributes" 95 depends on X86 && ISCSI_IBFT 96 default n 97 help 98 This option enables the kernel to find the region of memory 99 in which the ISCSI Boot Firmware Table (iBFT) resides. This 100 is necessary for iSCSI Boot Firmware Table Attributes module to work 101 properly. 102 103config ISCSI_IBFT 104 tristate "iSCSI Boot Firmware Table Attributes module" 105 select ISCSI_BOOT_SYSFS 106 select ISCSI_IBFT_FIND if X86 107 depends on ACPI && SCSI && SCSI_LOWLEVEL 108 default n 109 help 110 This option enables support for detection and exposing of iSCSI 111 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to 112 detect iSCSI boot parameters dynamically during system boot, say Y. 113 Otherwise, say N. 114 115config RASPBERRYPI_FIRMWARE 116 tristate "Raspberry Pi Firmware Driver" 117 depends on BCM2835_MBOX 118 help 119 This option enables support for communicating with the firmware on the 120 Raspberry Pi. 121 122config FW_CFG_SYSFS 123 tristate "QEMU fw_cfg device support in sysfs" 124 depends on SYSFS && (ARM || ARM64 || PARISC || PPC_PMAC || RISCV || SPARC || X86) 125 depends on HAS_IOPORT_MAP 126 default n 127 help 128 Say Y or M here to enable the exporting of the QEMU firmware 129 configuration (fw_cfg) file entries via sysfs. Entries are 130 found under /sys/firmware/fw_cfg when this option is enabled 131 and loaded. 132 133config FW_CFG_SYSFS_CMDLINE 134 bool "QEMU fw_cfg device parameter parsing" 135 depends on FW_CFG_SYSFS 136 help 137 Allow the qemu_fw_cfg device to be initialized via the kernel 138 command line or using a module parameter. 139 WARNING: Using incorrect parameters (base address in particular) 140 may crash your system. 141 142config INTEL_STRATIX10_SERVICE 143 tristate "Intel Stratix10 Service Layer" 144 depends on ARCH_INTEL_SOCFPGA && ARM64 && HAVE_ARM_SMCCC 145 default n 146 help 147 Intel Stratix10 service layer runs at privileged exception level, 148 interfaces with the service providers (FPGA manager is one of them) 149 and manages secure monitor call to communicate with secure monitor 150 software at secure monitor exception level. 151 152 Say Y here if you want Stratix10 service layer support. 153 154config INTEL_STRATIX10_RSU 155 tristate "Intel Stratix10 Remote System Update" 156 depends on INTEL_STRATIX10_SERVICE 157 help 158 The Intel Remote System Update (RSU) driver exposes interfaces 159 access through the Intel Service Layer to user space via sysfs 160 device attribute nodes. The RSU interfaces report/control some of 161 the optional RSU features of the Stratix 10 SoC FPGA. 162 163 The RSU provides a way for customers to update the boot 164 configuration of a Stratix 10 SoC device with significantly reduced 165 risk of corrupting the bitstream storage and bricking the system. 166 167 Enable RSU support if you are using an Intel SoC FPGA with the RSU 168 feature enabled and you want Linux user space control. 169 170 Say Y here if you want Intel RSU support. 171 172config MTK_ADSP_IPC 173 tristate "MTK ADSP IPC Protocol driver" 174 depends on MTK_ADSP_MBOX 175 help 176 Say yes here to add support for the MediaTek ADSP IPC 177 between host AP (Linux) and the firmware running on ADSP. 178 ADSP exists on some mtk processors. 179 Client might use shared memory to exchange information with ADSP. 180 181config SYSFB 182 bool 183 select BOOT_VESA_SUPPORT 184 select SCREEN_INFO 185 186config SYSFB_SIMPLEFB 187 bool "Mark VGA/VBE/EFI FB as generic system framebuffer" 188 depends on X86 || EFI 189 select SYSFB 190 help 191 Firmwares often provide initial graphics framebuffers so the BIOS, 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 195 to x86 BIOS or EFI systems. 196 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic 197 framebuffers so the new generic system-framebuffer drivers can be 198 used instead. If the framebuffer is not compatible with the generic 199 modes, it is advertised as fallback platform framebuffer so legacy 200 drivers like efifb, vesafb and uvesafb can pick it up. 201 If this option is not selected, all system framebuffers are always 202 marked as fallback platform framebuffers as usual. 203 204 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will 205 not be able to pick up generic system framebuffers if this option 206 is selected. You are highly encouraged to enable simplefb as 207 replacement if you select this option. simplefb can correctly deal 208 with generic system framebuffers. But you should still keep vesafb 209 and others enabled as fallback if a system framebuffer is 210 incompatible with simplefb. 211 212 If unsure, say Y. 213 214config TI_SCI_PROTOCOL 215 tristate "TI System Control Interface (TISCI) Message Protocol" 216 depends on TI_MESSAGE_MANAGER 217 help 218 TI System Control Interface (TISCI) Message Protocol is used to manage 219 compute systems such as ARM, DSP etc with the system controller in 220 complex System on Chip(SoC) such as those found on certain keystone 221 generation SoC from TI. 222 223 System controller provides various facilities including power 224 management function support. 225 226 This protocol library is used by client drivers to use the features 227 provided by the system controller. 228 229config TRUSTED_FOUNDATIONS 230 bool "Trusted Foundations secure monitor support" 231 depends on ARM && CPU_V7 232 help 233 Some devices (including most early Tegra-based consumer devices on 234 the market) are booted with the Trusted Foundations secure monitor 235 active, requiring some core operations to be performed by the secure 236 monitor instead of the kernel. 237 238 This option allows the kernel to invoke the secure monitor whenever 239 required on devices using Trusted Foundations. See the functions and 240 comments in linux/firmware/trusted_foundations.h or the device tree 241 bindings for "tlm,trusted-foundations" for details on how to use it. 242 243 Choose N if you don't know what this is about. 244 245config TURRIS_MOX_RWTM 246 tristate "Turris Mox rWTM secure firmware driver" 247 depends on ARCH_MVEBU || COMPILE_TEST 248 depends on HAS_DMA && OF 249 depends on MAILBOX 250 select HW_RANDOM 251 select ARMADA_37XX_RWTM_MBOX 252 help 253 This driver communicates with the firmware on the Cortex-M3 secure 254 processor of the Turris Mox router. Enable if you are building for 255 Turris Mox, and you will be able to read the device serial number and 256 other manufacturing data and also utilize the Entropy Bit Generator 257 for hardware random number generation. 258 259source "drivers/firmware/arm_ffa/Kconfig" 260source "drivers/firmware/broadcom/Kconfig" 261source "drivers/firmware/cirrus/Kconfig" 262source "drivers/firmware/google/Kconfig" 263source "drivers/firmware/efi/Kconfig" 264source "drivers/firmware/imx/Kconfig" 265source "drivers/firmware/meson/Kconfig" 266source "drivers/firmware/microchip/Kconfig" 267source "drivers/firmware/psci/Kconfig" 268source "drivers/firmware/qcom/Kconfig" 269source "drivers/firmware/smccc/Kconfig" 270source "drivers/firmware/tegra/Kconfig" 271source "drivers/firmware/xilinx/Kconfig" 272 273endmenu 274