1 # SPDX-License-Identifier: GPL-2.0-only
3 # For a description of the syntax of this configuration file,
4 # see Documentation/kbuild/kconfig-language.rst.
7 menu "Firmware Drivers"
9 config ARM_SCMI_PROTOCOL
10 bool "ARM System Control and Management Interface (SCMI) Message Protocol"
11 depends on ARM || ARM64 || COMPILE_TEST
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.
27 This protocol library provides interface for all the client drivers
28 making use of the features offered by the SCMI.
30 config ARM_SCMI_POWER_DOMAIN
31 tristate "SCMI power domain driver"
32 depends on ARM_SCMI_PROTOCOL || (COMPILE_TEST && OF)
34 select PM_GENERIC_DOMAINS if PM
36 This enables support for the SCMI power domains which can be
37 enabled or disabled via the SCP firmware
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.
43 config ARM_SCPI_PROTOCOL
44 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
45 depends on ARM || ARM64 || COMPILE_TEST
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
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
60 This protocol library provides interface for all the client drivers
61 making use of the features offered by the SCP.
63 config ARM_SCPI_POWER_DOMAIN
64 tristate "SCPI power domain driver"
65 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
67 select PM_GENERIC_DOMAINS if PM
69 This enables support for the SCPI power domains which can be
70 enabled or disabled via the SCP firmware
72 config ARM_SDE_INTERFACE
73 bool "ARM Software Delegated Exception Interface (SDEI)"
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.
81 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
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.
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.
93 bool "Sets default behavior for EDD detection to off"
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}'.
101 config FIRMWARE_MEMMAP
102 bool "Add firmware-provided memory map to sysfs" if EXPERT
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.
109 See also Documentation/ABI/testing/sysfs-firmware-memmap.
112 bool "Console device selection via EFI PCDP or HCDP table"
113 depends on ACPI && EFI && IA64
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.
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.
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.
130 You must also enable the appropriate drivers (serial, VGA, etc.)
132 See DIG64_HCDPv20_042804.pdf available from
133 <http://www.dig64.org/specifications/>
136 bool "Export DMI identification via sysfs to userspace"
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.
145 tristate "DMI table support in sysfs"
146 depends on SYSFS && DMI
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
155 config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
158 config ISCSI_IBFT_FIND
159 bool "iSCSI Boot Firmware Table Attributes"
160 depends on X86 && ISCSI_IBFT
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
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
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.
180 config RASPBERRYPI_FIRMWARE
181 tristate "Raspberry Pi Firmware Driver"
182 depends on BCM2835_MBOX
184 This option enables support for communicating with the firmware on the
188 tristate "QEMU fw_cfg device support in sysfs"
189 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
190 depends on HAS_IOPORT_MAP
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
198 config FW_CFG_SYSFS_CMDLINE
199 bool "QEMU fw_cfg device parameter parsing"
200 depends on FW_CFG_SYSFS
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.
207 config INTEL_STRATIX10_SERVICE
208 tristate "Intel Stratix10 Service Layer"
209 depends on ARCH_STRATIX10 && HAVE_ARM_SMCCC
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.
217 Say Y here if you want Stratix10 service layer support.
221 depends on ARM || ARM64
222 select RESET_CONTROLLER
226 depends on QCOM_SCM && ARM
230 depends on QCOM_SCM && ARM64
232 config QCOM_SCM_DOWNLOAD_MODE_DEFAULT
233 bool "Qualcomm download mode enabled by default"
236 A device with "download mode" enabled will upon an unexpected
237 warm-restart enter a special debug mode that allows the user to
238 "download" memory content over USB for offline postmortem analysis.
239 The feature can be enabled/disabled on the kernel command line.
241 Say Y here to enable "download mode" by default.
243 config TI_SCI_PROTOCOL
244 tristate "TI System Control Interface (TISCI) Message Protocol"
245 depends on TI_MESSAGE_MANAGER
247 TI System Control Interface (TISCI) Message Protocol is used to manage
248 compute systems such as ARM, DSP etc with the system controller in
249 complex System on Chip(SoC) such as those found on certain keystone
250 generation SoC from TI.
252 System controller provides various facilities including power
253 management function support.
255 This protocol library is used by client drivers to use the features
256 provided by the system controller.
258 config TRUSTED_FOUNDATIONS
259 bool "Trusted Foundations secure monitor support"
260 depends on ARM && CPU_V7
262 Some devices (including most early Tegra-based consumer devices on
263 the market) are booted with the Trusted Foundations secure monitor
264 active, requiring some core operations to be performed by the secure
265 monitor instead of the kernel.
267 This option allows the kernel to invoke the secure monitor whenever
268 required on devices using Trusted Foundations. See the functions and
269 comments in linux/firmware/trusted_foundations.h or the device tree
270 bindings for "tlm,trusted-foundations" for details on how to use it.
272 Choose N if you don't know what this is about.
274 config TURRIS_MOX_RWTM
275 tristate "Turris Mox rWTM secure firmware driver"
276 depends on ARCH_MVEBU || COMPILE_TEST
277 depends on HAS_DMA && OF
280 select ARMADA_37XX_RWTM_MBOX
282 This driver communicates with the firmware on the Cortex-M3 secure
283 processor of the Turris Mox router. Enable if you are building for
284 Turris Mox, and you will be able to read the device serial number and
285 other manufacturing data and also utilize the Entropy Bit Generator
286 for hardware random number generation.
288 config HAVE_ARM_SMCCC
291 source "drivers/firmware/psci/Kconfig"
292 source "drivers/firmware/broadcom/Kconfig"
293 source "drivers/firmware/google/Kconfig"
294 source "drivers/firmware/efi/Kconfig"
295 source "drivers/firmware/imx/Kconfig"
296 source "drivers/firmware/meson/Kconfig"
297 source "drivers/firmware/tegra/Kconfig"
298 source "drivers/firmware/xilinx/Kconfig"