Loading...
1#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5
6menu "Firmware Drivers"
7
8config EDD
9 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
10 depends on X86
11 help
12 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
13 Services real mode BIOS calls to determine which disk
14 BIOS tries boot from. This information is then exported via sysfs.
15
16 This option is experimental and is known to fail to boot on some
17 obscure configurations. Most disk controller BIOS vendors do
18 not yet implement this feature.
19
20config EDD_OFF
21 bool "Sets default behavior for EDD detection to off"
22 depends on EDD
23 default n
24 help
25 Say Y if you want EDD disabled by default, even though it is compiled into the
26 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
27 using the kernel parameter 'edd={on|skipmbr|off}'.
28
29config FIRMWARE_MEMMAP
30 bool "Add firmware-provided memory map to sysfs" if EXPERT
31 default X86
32 help
33 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
34 That memory map is used for example by kexec to set up parameter area
35 for the next kernel, but can also be used for debugging purposes.
36
37 See also Documentation/ABI/testing/sysfs-firmware-memmap.
38
39config EFI_VARS
40 tristate "EFI Variable Support via sysfs"
41 depends on EFI
42 default n
43 help
44 If you say Y here, you are able to get EFI (Extensible Firmware
45 Interface) variable information via sysfs. You may read,
46 write, create, and destroy EFI variables through this interface.
47
48 Note that using this driver in concert with efibootmgr requires
49 at least test release version 0.5.0-test3 or later, which is
50 available from Matt Domsch's website located at:
51 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
52
53 Subsequent efibootmgr releases may be found at:
54 <http://linux.dell.com/efibootmgr>
55
56config EFI_PCDP
57 bool "Console device selection via EFI PCDP or HCDP table"
58 depends on ACPI && EFI && IA64
59 default y if IA64
60 help
61 If your firmware supplies the PCDP table, and you want to
62 automatically use the primary console device it describes
63 as the Linux console, say Y here.
64
65 If your firmware supplies the HCDP table, and you want to
66 use the first serial port it describes as the Linux console,
67 say Y here. If your EFI ConOut path contains only a UART
68 device, it will become the console automatically. Otherwise,
69 you must specify the "console=hcdp" kernel boot argument.
70
71 Neither the PCDP nor the HCDP affects naming of serial devices,
72 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
73 on how the driver discovers devices.
74
75 You must also enable the appropriate drivers (serial, VGA, etc.)
76
77 See DIG64_HCDPv20_042804.pdf available from
78 <http://www.dig64.org/specifications/>
79
80config DELL_RBU
81 tristate "BIOS update support for DELL systems via sysfs"
82 depends on X86
83 select FW_LOADER
84 help
85 Say m if you want to have the option of updating the BIOS for your
86 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
87 supporting application to communicate with the BIOS regarding the new
88 image for the image update to take effect.
89 See <file:Documentation/dell_rbu.txt> for more details on the driver.
90
91config DCDBAS
92 tristate "Dell Systems Management Base Driver"
93 depends on X86
94 help
95 The Dell Systems Management Base Driver provides a sysfs interface
96 for systems management software to perform System Management
97 Interrupts (SMIs) and Host Control Actions (system power cycle or
98 power off after OS shutdown) on certain Dell systems.
99
100 See <file:Documentation/dcdbas.txt> for more details on the driver
101 and the Dell systems on which Dell systems management software makes
102 use of this driver.
103
104 Say Y or M here to enable the driver for use by Dell systems
105 management software such as Dell OpenManage.
106
107config DMIID
108 bool "Export DMI identification via sysfs to userspace"
109 depends on DMI
110 default y
111 help
112 Say Y here if you want to query SMBIOS/DMI system identification
113 information from userspace through /sys/class/dmi/id/ or if you want
114 DMI-based module auto-loading.
115
116config DMI_SYSFS
117 tristate "DMI table support in sysfs"
118 depends on SYSFS && DMI
119 default n
120 help
121 Say Y or M here to enable the exporting of the raw DMI table
122 data via sysfs. This is useful for consuming the data without
123 requiring any access to /dev/mem at all. Tables are found
124 under /sys/firmware/dmi when this option is enabled and
125 loaded.
126
127config ISCSI_IBFT_FIND
128 bool "iSCSI Boot Firmware Table Attributes"
129 depends on X86
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 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
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
148config SIGMA
149 tristate "SigmaStudio firmware loader"
150 depends on I2C
151 select CRC32
152 default n
153 help
154 Enable helper functions for working with Analog Devices SigmaDSP
155 parts and binary firmwares produced by Analog Devices SigmaStudio.
156
157 If unsure, say N here. Drivers that need these helpers will select
158 this option automatically.
159
160source "drivers/firmware/google/Kconfig"
161
162endmenu
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_SDE_INTERFACE
32 bool "ARM Software Delegated Exception Interface (SDEI)"
33 depends on ARM64
34 depends on ACPI_APEI_GHES
35 help
36 The Software Delegated Exception Interface (SDEI) is an ARM
37 standard for registering callbacks from the platform firmware
38 into the OS. This is typically used to implement RAS notifications.
39
40config EDD
41 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
42 depends on X86
43 help
44 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
45 Services real mode BIOS calls to determine which disk
46 BIOS tries boot from. This information is then exported via sysfs.
47
48 This option is experimental and is known to fail to boot on some
49 obscure configurations. Most disk controller BIOS vendors do
50 not yet implement this feature.
51
52config EDD_OFF
53 bool "Sets default behavior for EDD detection to off"
54 depends on EDD
55 default n
56 help
57 Say Y if you want EDD disabled by default, even though it is compiled into the
58 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
59 using the kernel parameter 'edd={on|skipmbr|off}'.
60
61config FIRMWARE_MEMMAP
62 bool "Add firmware-provided memory map to sysfs" if EXPERT
63 default X86
64 help
65 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
66 That memory map is used for example by kexec to set up parameter area
67 for the next kernel, but can also be used for debugging purposes.
68
69 See also Documentation/ABI/testing/sysfs-firmware-memmap.
70
71config DMIID
72 bool "Export DMI identification via sysfs to userspace"
73 depends on DMI
74 default y
75 help
76 Say Y here if you want to query SMBIOS/DMI system identification
77 information from userspace through /sys/class/dmi/id/ or if you want
78 DMI-based module auto-loading.
79
80config DMI_SYSFS
81 tristate "DMI table support in sysfs"
82 depends on SYSFS && DMI
83 default n
84 help
85 Say Y or M here to enable the exporting of the raw DMI table
86 data via sysfs. This is useful for consuming the data without
87 requiring any access to /dev/mem at all. Tables are found
88 under /sys/firmware/dmi when this option is enabled and
89 loaded.
90
91config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
92 bool
93
94config ISCSI_IBFT_FIND
95 bool "iSCSI Boot Firmware Table Attributes"
96 depends on X86 && ISCSI_IBFT
97 default n
98 help
99 This option enables the kernel to find the region of memory
100 in which the ISCSI Boot Firmware Table (iBFT) resides. This
101 is necessary for iSCSI Boot Firmware Table Attributes module to work
102 properly.
103
104config ISCSI_IBFT
105 tristate "iSCSI Boot Firmware Table Attributes module"
106 select ISCSI_BOOT_SYSFS
107 select ISCSI_IBFT_FIND if X86
108 depends on ACPI && SCSI && SCSI_LOWLEVEL
109 default n
110 help
111 This option enables support for detection and exposing of iSCSI
112 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
113 detect iSCSI boot parameters dynamically during system boot, say Y.
114 Otherwise, say N.
115
116config RASPBERRYPI_FIRMWARE
117 tristate "Raspberry Pi Firmware Driver"
118 depends on BCM2835_MBOX
119 help
120 This option enables support for communicating with the firmware on the
121 Raspberry Pi.
122
123config FW_CFG_SYSFS
124 tristate "QEMU fw_cfg device support in sysfs"
125 depends on SYSFS && (ARM || ARM64 || PARISC || PPC_PMAC || RISCV || SPARC || X86)
126 depends on HAS_IOPORT_MAP
127 default n
128 help
129 Say Y or M here to enable the exporting of the QEMU firmware
130 configuration (fw_cfg) file entries via sysfs. Entries are
131 found under /sys/firmware/fw_cfg when this option is enabled
132 and loaded.
133
134config FW_CFG_SYSFS_CMDLINE
135 bool "QEMU fw_cfg device parameter parsing"
136 depends on FW_CFG_SYSFS
137 help
138 Allow the qemu_fw_cfg device to be initialized via the kernel
139 command line or using a module parameter.
140 WARNING: Using incorrect parameters (base address in particular)
141 may crash your system.
142
143config INTEL_STRATIX10_SERVICE
144 tristate "Intel Stratix10 Service Layer"
145 depends on ARCH_INTEL_SOCFPGA && ARM64 && HAVE_ARM_SMCCC
146 default n
147 help
148 Intel Stratix10 service layer runs at privileged exception level,
149 interfaces with the service providers (FPGA manager is one of them)
150 and manages secure monitor call to communicate with secure monitor
151 software at secure monitor exception level.
152
153 Say Y here if you want Stratix10 service layer support.
154
155config INTEL_STRATIX10_RSU
156 tristate "Intel Stratix10 Remote System Update"
157 depends on INTEL_STRATIX10_SERVICE
158 help
159 The Intel Remote System Update (RSU) driver exposes interfaces
160 access through the Intel Service Layer to user space via sysfs
161 device attribute nodes. The RSU interfaces report/control some of
162 the optional RSU features of the Stratix 10 SoC FPGA.
163
164 The RSU provides a way for customers to update the boot
165 configuration of a Stratix 10 SoC device with significantly reduced
166 risk of corrupting the bitstream storage and bricking the system.
167
168 Enable RSU support if you are using an Intel SoC FPGA with the RSU
169 feature enabled and you want Linux user space control.
170
171 Say Y here if you want Intel RSU support.
172
173config MTK_ADSP_IPC
174 tristate "MTK ADSP IPC Protocol driver"
175 depends on MTK_ADSP_MBOX
176 help
177 Say yes here to add support for the MediaTek ADSP IPC
178 between host AP (Linux) and the firmware running on ADSP.
179 ADSP exists on some mtk processors.
180 Client might use shared memory to exchange information with ADSP.
181
182config SYSFB
183 bool
184 select BOOT_VESA_SUPPORT
185
186config SYSFB_SIMPLEFB
187 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
188 depends on X86 || EFI
189 select SYSFB
190 help
191 Firmwares often provide initial graphics framebuffers so the BIOS,
192 bootloader or kernel can show basic video-output during boot for
193 user-guidance and debugging. Historically, x86 used the VESA BIOS
194 Extensions and EFI-framebuffers for this, which are mostly limited
195 to x86 BIOS or EFI systems.
196 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
197 framebuffers so the new generic system-framebuffer drivers can be
198 used instead. If the framebuffer is not compatible with the generic
199 modes, it is advertised as fallback platform framebuffer so legacy
200 drivers like efifb, vesafb and uvesafb can pick it up.
201 If this option is not selected, all system framebuffers are always
202 marked as fallback platform framebuffers as usual.
203
204 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
205 not be able to pick up generic system framebuffers if this option
206 is selected. You are highly encouraged to enable simplefb as
207 replacement if you select this option. simplefb can correctly deal
208 with generic system framebuffers. But you should still keep vesafb
209 and others enabled as fallback if a system framebuffer is
210 incompatible with simplefb.
211
212 If unsure, say Y.
213
214config TI_SCI_PROTOCOL
215 tristate "TI System Control Interface (TISCI) Message Protocol"
216 depends on TI_MESSAGE_MANAGER
217 help
218 TI System Control Interface (TISCI) Message Protocol is used to manage
219 compute systems such as ARM, DSP etc with the system controller in
220 complex System on Chip(SoC) such as those found on certain keystone
221 generation SoC from TI.
222
223 System controller provides various facilities including power
224 management function support.
225
226 This protocol library is used by client drivers to use the features
227 provided by the system controller.
228
229config TRUSTED_FOUNDATIONS
230 bool "Trusted Foundations secure monitor support"
231 depends on ARM && CPU_V7
232 help
233 Some devices (including most early Tegra-based consumer devices on
234 the market) are booted with the Trusted Foundations secure monitor
235 active, requiring some core operations to be performed by the secure
236 monitor instead of the kernel.
237
238 This option allows the kernel to invoke the secure monitor whenever
239 required on devices using Trusted Foundations. See the functions and
240 comments in linux/firmware/trusted_foundations.h or the device tree
241 bindings for "tlm,trusted-foundations" for details on how to use it.
242
243 Choose N if you don't know what this is about.
244
245config TURRIS_MOX_RWTM
246 tristate "Turris Mox rWTM secure firmware driver"
247 depends on ARCH_MVEBU || COMPILE_TEST
248 depends on HAS_DMA && OF
249 depends on MAILBOX
250 select HW_RANDOM
251 select ARMADA_37XX_RWTM_MBOX
252 help
253 This driver communicates with the firmware on the Cortex-M3 secure
254 processor of the Turris Mox router. Enable if you are building for
255 Turris Mox, and you will be able to read the device serial number and
256 other manufacturing data and also utilize the Entropy Bit Generator
257 for hardware random number generation.
258
259source "drivers/firmware/arm_ffa/Kconfig"
260source "drivers/firmware/broadcom/Kconfig"
261source "drivers/firmware/cirrus/Kconfig"
262source "drivers/firmware/google/Kconfig"
263source "drivers/firmware/efi/Kconfig"
264source "drivers/firmware/imx/Kconfig"
265source "drivers/firmware/meson/Kconfig"
266source "drivers/firmware/microchip/Kconfig"
267source "drivers/firmware/psci/Kconfig"
268source "drivers/firmware/qcom/Kconfig"
269source "drivers/firmware/smccc/Kconfig"
270source "drivers/firmware/tegra/Kconfig"
271source "drivers/firmware/xilinx/Kconfig"
272
273endmenu