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