Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
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
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 DMIID
81 bool "Export DMI identification via sysfs to userspace"
82 depends on DMI
83 default y
84 help
85 Say Y here if you want to query SMBIOS/DMI system identification
86 information from userspace through /sys/class/dmi/id/ or if you want
87 DMI-based module auto-loading.
88
89config DMI_SYSFS
90 tristate "DMI table support in sysfs"
91 depends on SYSFS && DMI
92 default n
93 help
94 Say Y or M here to enable the exporting of the raw DMI table
95 data via sysfs. This is useful for consuming the data without
96 requiring any access to /dev/mem at all. Tables are found
97 under /sys/firmware/dmi when this option is enabled and
98 loaded.
99
100config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
101 bool
102
103config ISCSI_IBFT_FIND
104 bool "iSCSI Boot Firmware Table Attributes"
105 depends on X86 && ISCSI_IBFT
106 default n
107 help
108 This option enables the kernel to find the region of memory
109 in which the ISCSI Boot Firmware Table (iBFT) resides. This
110 is necessary for iSCSI Boot Firmware Table Attributes module to work
111 properly.
112
113config ISCSI_IBFT
114 tristate "iSCSI Boot Firmware Table Attributes module"
115 select ISCSI_BOOT_SYSFS
116 select ISCSI_IBFT_FIND if X86
117 depends on ACPI && SCSI && SCSI_LOWLEVEL
118 default n
119 help
120 This option enables support for detection and exposing of iSCSI
121 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
122 detect iSCSI boot parameters dynamically during system boot, say Y.
123 Otherwise, say N.
124
125config RASPBERRYPI_FIRMWARE
126 tristate "Raspberry Pi Firmware Driver"
127 depends on BCM2835_MBOX
128 help
129 This option enables support for communicating with the firmware on the
130 Raspberry Pi.
131
132config FW_CFG_SYSFS
133 tristate "QEMU fw_cfg device support in sysfs"
134 depends on SYSFS && (ARM || ARM64 || PARISC || PPC_PMAC || RISCV || SPARC || X86)
135 depends on HAS_IOPORT_MAP
136 default n
137 help
138 Say Y or M here to enable the exporting of the QEMU firmware
139 configuration (fw_cfg) file entries via sysfs. Entries are
140 found under /sys/firmware/fw_cfg when this option is enabled
141 and loaded.
142
143config FW_CFG_SYSFS_CMDLINE
144 bool "QEMU fw_cfg device parameter parsing"
145 depends on FW_CFG_SYSFS
146 help
147 Allow the qemu_fw_cfg device to be initialized via the kernel
148 command line or using a module parameter.
149 WARNING: Using incorrect parameters (base address in particular)
150 may crash your system.
151
152config INTEL_STRATIX10_SERVICE
153 tristate "Intel Stratix10 Service Layer"
154 depends on ARCH_INTEL_SOCFPGA && ARM64 && HAVE_ARM_SMCCC
155 default n
156 help
157 Intel Stratix10 service layer runs at privileged exception level,
158 interfaces with the service providers (FPGA manager is one of them)
159 and manages secure monitor call to communicate with secure monitor
160 software at secure monitor exception level.
161
162 Say Y here if you want Stratix10 service layer support.
163
164config INTEL_STRATIX10_RSU
165 tristate "Intel Stratix10 Remote System Update"
166 depends on INTEL_STRATIX10_SERVICE
167 help
168 The Intel Remote System Update (RSU) driver exposes interfaces
169 access through the Intel Service Layer to user space via sysfs
170 device attribute nodes. The RSU interfaces report/control some of
171 the optional RSU features of the Stratix 10 SoC FPGA.
172
173 The RSU provides a way for customers to update the boot
174 configuration of a Stratix 10 SoC device with significantly reduced
175 risk of corrupting the bitstream storage and bricking the system.
176
177 Enable RSU support if you are using an Intel SoC FPGA with the RSU
178 feature enabled and you want Linux user space control.
179
180 Say Y here if you want Intel RSU support.
181
182config MTK_ADSP_IPC
183 tristate "MTK ADSP IPC Protocol driver"
184 depends on MTK_ADSP_MBOX
185 help
186 Say yes here to add support for the MediaTek ADSP IPC
187 between host AP (Linux) and the firmware running on ADSP.
188 ADSP exists on some mtk processors.
189 Client might use shared memory to exchange information with ADSP.
190
191config SYSFB
192 bool
193 select BOOT_VESA_SUPPORT
194
195config SYSFB_SIMPLEFB
196 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
197 depends on X86 || EFI
198 select SYSFB
199 help
200 Firmwares often provide initial graphics framebuffers so the BIOS,
201 bootloader or kernel can show basic video-output during boot for
202 user-guidance and debugging. Historically, x86 used the VESA BIOS
203 Extensions and EFI-framebuffers for this, which are mostly limited
204 to x86 BIOS or EFI systems.
205 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
206 framebuffers so the new generic system-framebuffer drivers can be
207 used instead. If the framebuffer is not compatible with the generic
208 modes, it is advertised as fallback platform framebuffer so legacy
209 drivers like efifb, vesafb and uvesafb can pick it up.
210 If this option is not selected, all system framebuffers are always
211 marked as fallback platform framebuffers as usual.
212
213 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
214 not be able to pick up generic system framebuffers if this option
215 is selected. You are highly encouraged to enable simplefb as
216 replacement if you select this option. simplefb can correctly deal
217 with generic system framebuffers. But you should still keep vesafb
218 and others enabled as fallback if a system framebuffer is
219 incompatible with simplefb.
220
221 If unsure, say Y.
222
223config TI_SCI_PROTOCOL
224 tristate "TI System Control Interface (TISCI) Message Protocol"
225 depends on TI_MESSAGE_MANAGER
226 help
227 TI System Control Interface (TISCI) Message Protocol is used to manage
228 compute systems such as ARM, DSP etc with the system controller in
229 complex System on Chip(SoC) such as those found on certain keystone
230 generation SoC from TI.
231
232 System controller provides various facilities including power
233 management function support.
234
235 This protocol library is used by client drivers to use the features
236 provided by the system controller.
237
238config TRUSTED_FOUNDATIONS
239 bool "Trusted Foundations secure monitor support"
240 depends on ARM && CPU_V7
241 help
242 Some devices (including most early Tegra-based consumer devices on
243 the market) are booted with the Trusted Foundations secure monitor
244 active, requiring some core operations to be performed by the secure
245 monitor instead of the kernel.
246
247 This option allows the kernel to invoke the secure monitor whenever
248 required on devices using Trusted Foundations. See the functions and
249 comments in linux/firmware/trusted_foundations.h or the device tree
250 bindings for "tlm,trusted-foundations" for details on how to use it.
251
252 Choose N if you don't know what this is about.
253
254config TURRIS_MOX_RWTM
255 tristate "Turris Mox rWTM secure firmware driver"
256 depends on ARCH_MVEBU || COMPILE_TEST
257 depends on HAS_DMA && OF
258 depends on MAILBOX
259 select HW_RANDOM
260 select ARMADA_37XX_RWTM_MBOX
261 help
262 This driver communicates with the firmware on the Cortex-M3 secure
263 processor of the Turris Mox router. Enable if you are building for
264 Turris Mox, and you will be able to read the device serial number and
265 other manufacturing data and also utilize the Entropy Bit Generator
266 for hardware random number generation.
267
268source "drivers/firmware/arm_ffa/Kconfig"
269source "drivers/firmware/broadcom/Kconfig"
270source "drivers/firmware/cirrus/Kconfig"
271source "drivers/firmware/google/Kconfig"
272source "drivers/firmware/efi/Kconfig"
273source "drivers/firmware/imx/Kconfig"
274source "drivers/firmware/meson/Kconfig"
275source "drivers/firmware/psci/Kconfig"
276source "drivers/firmware/qcom/Kconfig"
277source "drivers/firmware/smccc/Kconfig"
278source "drivers/firmware/tegra/Kconfig"
279source "drivers/firmware/xilinx/Kconfig"
280
281endmenu