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