blob: 25f51b60194b53d14c404dfdf20a0514407249b2 [file] [log] [blame]
Thomas Gleixnerec8f24b2019-05-19 13:07:45 +01001# SPDX-License-Identifier: GPL-2.0-only
Linus Torvalds1da177e2005-04-16 15:20:36 -07002#
3# For a description of the syntax of this configuration file,
Mauro Carvalho Chehabcd238ef2019-06-12 14:52:48 -03004# see Documentation/kbuild/kconfig-language.rst.
Linus Torvalds1da177e2005-04-16 15:20:36 -07005#
6
7menu "Firmware Drivers"
8
Sudeep Hollaaa4f8862017-03-28 11:36:07 +01009config ARM_SCMI_PROTOCOL
10 bool "ARM System Control and Management Interface (SCMI) Message Protocol"
11 depends on ARM || ARM64 || COMPILE_TEST
12 depends on MAILBOX
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
Sudeep Holla898216c2017-06-14 13:48:26 +010030config 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
Sudeep Holla8cb7cf52015-03-30 10:59:52 +010043config ARM_SCPI_PROTOCOL
44 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
Jean Delvare92f3e6e2017-01-30 09:52:01 +010045 depends on ARM || ARM64 || COMPILE_TEST
Sudeep Holla8f1498c2016-06-05 18:23:21 +010046 depends on MAILBOX
Sudeep Holla8cb7cf52015-03-30 10:59:52 +010047 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
Sudeep Holla8bec4332016-06-02 16:34:03 +010063config ARM_SCPI_POWER_DOMAIN
64 tristate "SCPI power domain driver"
Arnd Bergmanne517dfe2016-07-06 14:49:46 +020065 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
Sudeep Holla8bec4332016-06-02 16:34:03 +010066 default y
67 select PM_GENERIC_DOMAINS if PM
Sudeep Holla8bec4332016-06-02 16:34:03 +010068 help
69 This enables support for the SCPI power domains which can be
70 enabled or disabled via the SCP firmware
71
James Morsead6eb312018-01-08 15:38:09 +000072config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070080config EDD
Chris Wedgwood5d186392006-06-25 05:47:46 -070081 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080082 depends on X86
Linus Torvalds1da177e2005-04-16 15:20:36 -070083 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
Tim Gardner8c4dd602008-04-29 01:02:45 -070092config 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
Bernhard Walle69ac9cd2008-06-27 13:12:54 +0200101config FIRMWARE_MEMMAP
David Rientjes6a108a12011-01-20 14:44:16 -0800102 bool "Add firmware-provided memory map to sysfs" if EXPERT
Mike Frysinger9b6e3e42009-12-14 18:01:16 -0800103 default X86
Bernhard Walle69ac9cd2008-06-27 13:12:54 +0200104 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
Linus Torvalds1da177e2005-04-16 15:20:36 -0700111config 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
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200132 See DIG64_HCDPv20_042804.pdf available from
133 <http://www.dig64.org/specifications/>
Linus Torvalds1da177e2005-04-16 15:20:36 -0700134
Lennart Poettering4f5c7912007-05-08 22:07:02 +0200135config 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
Mike Waychison948af1f2011-02-22 17:53:21 -0800144config 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
Ard Biesheuvelcf074402014-01-23 15:54:39 -0800155config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
156 bool
157
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700158config ISCSI_IBFT_FIND
159 bool "iSCSI Boot Firmware Table Attributes"
Thomas Tai94bccc32019-07-18 18:37:34 +0000160 depends on X86 && ISCSI_IBFT
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700161 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"
Mike Christieb33a84a2010-04-12 18:06:18 +0000170 select ISCSI_BOOT_SYSFS
Thomas Tai94bccc32019-07-18 18:37:34 +0000171 select ISCSI_IBFT_FIND if X86
172 depends on ACPI && SCSI && SCSI_LOWLEVEL
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700173 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
Eric Anholt4e3d6062015-02-26 10:08:06 +0000180config RASPBERRYPI_FIRMWARE
Nicolas Saenz Juliennec65822f2020-05-05 18:13:17 +0200181 bool "Raspberry Pi Firmware Driver"
Eric Anholt4e3d6062015-02-26 10:08:06 +0000182 depends on BCM2835_MBOX
Nicolas Saenz Juliennec65822f2020-05-05 18:13:17 +0200183 default USB_PCI
Eric Anholt4e3d6062015-02-26 10:08:06 +0000184 help
185 This option enables support for communicating with the firmware on the
186 Raspberry Pi.
187
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500188config FW_CFG_SYSFS
189 tristate "QEMU fw_cfg device support in sysfs"
Helge Deller6b698712020-08-29 10:00:40 +0200190 depends on SYSFS && (ARM || ARM64 || PARISC || PPC_PMAC || SPARC || X86)
Arnd Bergmann28c09ec2016-02-11 15:23:51 +0100191 depends on HAS_IOPORT_MAP
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500192 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
Richard Gong7ca5ce82018-11-13 12:14:01 -0600208config INTEL_STRATIX10_SERVICE
209 tristate "Intel Stratix10 Service Layer"
Richard Gong231d9012020-03-05 11:12:26 -0600210 depends on (ARCH_STRATIX10 || ARCH_AGILEX) && HAVE_ARM_SMCCC
Richard Gong7ca5ce82018-11-13 12:14:01 -0600211 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
Richard Gong4526ebb2019-09-03 08:18:19 -0500220config 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
Kumar Gala916f743d2015-02-26 15:49:09 -0600238config QCOM_SCM
239 bool
240 depends on ARM || ARM64
Bjorn Anderssondd4fe5b2016-06-17 10:40:43 -0700241 select RESET_CONTROLLER
Kumar Gala916f743d2015-02-26 15:49:09 -0600242
Bjorn Andersson8c1b7dc2017-08-14 15:46:18 -0700243config 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
Nishanth Menonaa276782016-10-18 18:08:34 -0500254config 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
Thierry Reding4cb5d9e2019-04-10 10:47:28 +0200269config TRUSTED_FOUNDATIONS
270 bool "Trusted Foundations secure monitor support"
Arnd Bergmanncad47b32019-06-17 14:33:23 +0200271 depends on ARM && CPU_V7
Thierry Reding4cb5d9e2019-04-10 10:47:28 +0200272 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
Marek Behún389711b2019-08-22 03:43:17 +0200285config 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
Rafał Miłeckif6e734a2015-06-10 23:05:08 +0200299source "drivers/firmware/broadcom/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700300source "drivers/firmware/google/Kconfig"
Matt Fleming04851772013-02-08 15:48:51 +0000301source "drivers/firmware/efi/Kconfig"
Dong Aishengedbee092018-10-07 21:04:42 +0800302source "drivers/firmware/imx/Kconfig"
Carlo Caione2c4ddb22016-08-27 15:43:43 +0200303source "drivers/firmware/meson/Kconfig"
Sudeep Hollae5bfb212020-05-18 10:12:16 +0100304source "drivers/firmware/psci/Kconfig"
305source "drivers/firmware/smccc/Kconfig"
Thierry Redingca791d72016-08-19 19:05:04 +0200306source "drivers/firmware/tegra/Kconfig"
Rajan Vaja76582672018-09-12 12:38:36 -0700307source "drivers/firmware/xilinx/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700308
Linus Torvalds1da177e2005-04-16 15:20:36 -0700309endmenu