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 9config ARM_SCMI_PROTOCOL 10 tristate "ARM System Control and Management Interface (SCMI) Message Protocol" 11 depends on ARM || ARM64 || COMPILE_TEST 12 depends on MAILBOX || HAVE_ARM_SMCCC_DISCOVERY 13 help 14 ARM System Control and Management Interface (SCMI) protocol is a 15 set of operating system-independent software interfaces that are 16 used in system management. SCMI is extensible and currently provides 17 interfaces for: Discovery and self-description of the interfaces 18 it supports, Power domain management which is the ability to place 19 a given device or domain into the various power-saving states that 20 it supports, Performance management which is the ability to control 21 the performance of a domain that is composed of compute engines 22 such as application processors and other accelerators, Clock 23 management which is the ability to set and inquire rates on platform 24 managed clocks and Sensor management which is the ability to read 25 sensor data, and be notified of sensor value. 26 27 This protocol library provides interface for all the client drivers 28 making use of the features offered by the SCMI. 29 30config ARM_SCMI_POWER_DOMAIN 31 tristate "SCMI power domain driver" 32 depends on ARM_SCMI_PROTOCOL || (COMPILE_TEST && OF) 33 default y 34 select PM_GENERIC_DOMAINS if PM 35 help 36 This enables support for the SCMI power domains which can be 37 enabled or disabled via the SCP firmware 38 39 This driver can also be built as a module. If so, the module 40 will be called scmi_pm_domain. Note this may needed early in boot 41 before rootfs may be available. 42 43config ARM_SCPI_PROTOCOL 44 tristate "ARM System Control and Power Interface (SCPI) Message Protocol" 45 depends on ARM || ARM64 || COMPILE_TEST 46 depends on MAILBOX 47 help 48 System Control and Power Interface (SCPI) Message Protocol is 49 defined for the purpose of communication between the Application 50 Cores(AP) and the System Control Processor(SCP). The MHU peripheral 51 provides a mechanism for inter-processor communication between SCP 52 and AP. 53 54 SCP controls most of the power managament on the Application 55 Processors. It offers control and management of: the core/cluster 56 power states, various power domain DVFS including the core/cluster, 57 certain system clocks configuration, thermal sensors and many 58 others. 59 60 This protocol library provides interface for all the client drivers 61 making use of the features offered by the SCP. 62 63config ARM_SCPI_POWER_DOMAIN 64 tristate "SCPI power domain driver" 65 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF) 66 default y 67 select PM_GENERIC_DOMAINS if PM 68 help 69 This enables support for the SCPI power domains which can be 70 enabled or disabled via the SCP firmware 71 72config ARM_SDE_INTERFACE 73 bool "ARM Software Delegated Exception Interface (SDEI)" 74 depends on ARM64 75 depends on ACPI_APEI_GHES 76 help 77 The Software Delegated Exception Interface (SDEI) is an ARM 78 standard for registering callbacks from the platform firmware 79 into the OS. This is typically used to implement RAS notifications. 80 81config EDD 82 tristate "BIOS Enhanced Disk Drive calls determine boot disk" 83 depends on X86 84 help 85 Say Y or M here if you want to enable BIOS Enhanced Disk Drive 86 Services real mode BIOS calls to determine which disk 87 BIOS tries boot from. This information is then exported via sysfs. 88 89 This option is experimental and is known to fail to boot on some 90 obscure configurations. Most disk controller BIOS vendors do 91 not yet implement this feature. 92 93config EDD_OFF 94 bool "Sets default behavior for EDD detection to off" 95 depends on EDD 96 default n 97 help 98 Say Y if you want EDD disabled by default, even though it is compiled into the 99 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set 100 using the kernel parameter 'edd={on|skipmbr|off}'. 101 102config FIRMWARE_MEMMAP 103 bool "Add firmware-provided memory map to sysfs" if EXPERT 104 default X86 105 help 106 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap. 107 That memory map is used for example by kexec to set up parameter area 108 for the next kernel, but can also be used for debugging purposes. 109 110 See also Documentation/ABI/testing/sysfs-firmware-memmap. 111 112config EFI_PCDP 113 bool "Console device selection via EFI PCDP or HCDP table" 114 depends on ACPI && EFI && IA64 115 default y if IA64 116 help 117 If your firmware supplies the PCDP table, and you want to 118 automatically use the primary console device it describes 119 as the Linux console, say Y here. 120 121 If your firmware supplies the HCDP table, and you want to 122 use the first serial port it describes as the Linux console, 123 say Y here. If your EFI ConOut path contains only a UART 124 device, it will become the console automatically. Otherwise, 125 you must specify the "console=hcdp" kernel boot argument. 126 127 Neither the PCDP nor the HCDP affects naming of serial devices, 128 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending 129 on how the driver discovers devices. 130 131 You must also enable the appropriate drivers (serial, VGA, etc.) 132 133 See DIG64_HCDPv20_042804.pdf available from 134 <http://www.dig64.org/specifications/> 135 136config DMIID 137 bool "Export DMI identification via sysfs to userspace" 138 depends on DMI 139 default y 140 help 141 Say Y here if you want to query SMBIOS/DMI system identification 142 information from userspace through /sys/class/dmi/id/ or if you want 143 DMI-based module auto-loading. 144 145config DMI_SYSFS 146 tristate "DMI table support in sysfs" 147 depends on SYSFS && DMI 148 default n 149 help 150 Say Y or M here to enable the exporting of the raw DMI table 151 data via sysfs. This is useful for consuming the data without 152 requiring any access to /dev/mem at all. Tables are found 153 under /sys/firmware/dmi when this option is enabled and 154 loaded. 155 156config DMI_SCAN_MACHINE_NON_EFI_FALLBACK 157 bool 158 159config ISCSI_IBFT_FIND 160 bool "iSCSI Boot Firmware Table Attributes" 161 depends on X86 && ISCSI_IBFT 162 default n 163 help 164 This option enables the kernel to find the region of memory 165 in which the ISCSI Boot Firmware Table (iBFT) resides. This 166 is necessary for iSCSI Boot Firmware Table Attributes module to work 167 properly. 168 169config ISCSI_IBFT 170 tristate "iSCSI Boot Firmware Table Attributes module" 171 select ISCSI_BOOT_SYSFS 172 select ISCSI_IBFT_FIND if X86 173 depends on ACPI && SCSI && SCSI_LOWLEVEL 174 default n 175 help 176 This option enables support for detection and exposing of iSCSI 177 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to 178 detect iSCSI boot parameters dynamically during system boot, say Y. 179 Otherwise, say N. 180 181config RASPBERRYPI_FIRMWARE 182 tristate "Raspberry Pi Firmware Driver" 183 depends on BCM2835_MBOX 184 help 185 This option enables support for communicating with the firmware on the 186 Raspberry Pi. 187 188config FW_CFG_SYSFS 189 tristate "QEMU fw_cfg device support in sysfs" 190 depends on SYSFS && (ARM || ARM64 || PARISC || PPC_PMAC || SPARC || X86) 191 depends on HAS_IOPORT_MAP 192 default n 193 help 194 Say Y or M here to enable the exporting of the QEMU firmware 195 configuration (fw_cfg) file entries via sysfs. Entries are 196 found under /sys/firmware/fw_cfg when this option is enabled 197 and loaded. 198 199config FW_CFG_SYSFS_CMDLINE 200 bool "QEMU fw_cfg device parameter parsing" 201 depends on FW_CFG_SYSFS 202 help 203 Allow the qemu_fw_cfg device to be initialized via the kernel 204 command line or using a module parameter. 205 WARNING: Using incorrect parameters (base address in particular) 206 may crash your system. 207 208config INTEL_STRATIX10_SERVICE 209 tristate "Intel Stratix10 Service Layer" 210 depends on (ARCH_STRATIX10 || ARCH_AGILEX) && HAVE_ARM_SMCCC 211 default n 212 help 213 Intel Stratix10 service layer runs at privileged exception level, 214 interfaces with the service providers (FPGA manager is one of them) 215 and manages secure monitor call to communicate with secure monitor 216 software at secure monitor exception level. 217 218 Say Y here if you want Stratix10 service layer support. 219 220config INTEL_STRATIX10_RSU 221 tristate "Intel Stratix10 Remote System Update" 222 depends on INTEL_STRATIX10_SERVICE 223 help 224 The Intel Remote System Update (RSU) driver exposes interfaces 225 access through the Intel Service Layer to user space via sysfs 226 device attribute nodes. The RSU interfaces report/control some of 227 the optional RSU features of the Stratix 10 SoC FPGA. 228 229 The RSU provides a way for customers to update the boot 230 configuration of a Stratix 10 SoC device with significantly reduced 231 risk of corrupting the bitstream storage and bricking the system. 232 233 Enable RSU support if you are using an Intel SoC FPGA with the RSU 234 feature enabled and you want Linux user space control. 235 236 Say Y here if you want Intel RSU support. 237 238config QCOM_SCM 239 tristate "Qcom SCM driver" 240 depends on ARM || ARM64 241 depends on HAVE_ARM_SMCCC 242 select RESET_CONTROLLER 243 244config QCOM_SCM_DOWNLOAD_MODE_DEFAULT 245 bool "Qualcomm download mode enabled by default" 246 depends on QCOM_SCM 247 help 248 A device with "download mode" enabled will upon an unexpected 249 warm-restart enter a special debug mode that allows the user to 250 "download" memory content over USB for offline postmortem analysis. 251 The feature can be enabled/disabled on the kernel command line. 252 253 Say Y here to enable "download mode" by default. 254 255config TI_SCI_PROTOCOL 256 tristate "TI System Control Interface (TISCI) Message Protocol" 257 depends on TI_MESSAGE_MANAGER 258 help 259 TI System Control Interface (TISCI) Message Protocol is used to manage 260 compute systems such as ARM, DSP etc with the system controller in 261 complex System on Chip(SoC) such as those found on certain keystone 262 generation SoC from TI. 263 264 System controller provides various facilities including power 265 management function support. 266 267 This protocol library is used by client drivers to use the features 268 provided by the system controller. 269 270config TRUSTED_FOUNDATIONS 271 bool "Trusted Foundations secure monitor support" 272 depends on ARM && CPU_V7 273 help 274 Some devices (including most early Tegra-based consumer devices on 275 the market) are booted with the Trusted Foundations secure monitor 276 active, requiring some core operations to be performed by the secure 277 monitor instead of the kernel. 278 279 This option allows the kernel to invoke the secure monitor whenever 280 required on devices using Trusted Foundations. See the functions and 281 comments in linux/firmware/trusted_foundations.h or the device tree 282 bindings for "tlm,trusted-foundations" for details on how to use it. 283 284 Choose N if you don't know what this is about. 285 286config TURRIS_MOX_RWTM 287 tristate "Turris Mox rWTM secure firmware driver" 288 depends on ARCH_MVEBU || COMPILE_TEST 289 depends on HAS_DMA && OF 290 depends on MAILBOX 291 select HW_RANDOM 292 select ARMADA_37XX_RWTM_MBOX 293 help 294 This driver communicates with the firmware on the Cortex-M3 secure 295 processor of the Turris Mox router. Enable if you are building for 296 Turris Mox, and you will be able to read the device serial number and 297 other manufacturing data and also utilize the Entropy Bit Generator 298 for hardware random number generation. 299 300source "drivers/firmware/arm_ffa/Kconfig" 301source "drivers/firmware/broadcom/Kconfig" 302source "drivers/firmware/google/Kconfig" 303source "drivers/firmware/efi/Kconfig" 304source "drivers/firmware/imx/Kconfig" 305source "drivers/firmware/meson/Kconfig" 306source "drivers/firmware/psci/Kconfig" 307source "drivers/firmware/smccc/Kconfig" 308source "drivers/firmware/tegra/Kconfig" 309source "drivers/firmware/xilinx/Kconfig" 310 311endmenu 312