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