Loading...
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 select SCREEN_INFO
186
187config SYSFB_SIMPLEFB
188 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
189 depends on X86 || EFI
190 select SYSFB
191 help
192 Firmwares often provide initial graphics framebuffers so the BIOS,
193 bootloader or kernel can show basic video-output during boot for
194 user-guidance and debugging. Historically, x86 used the VESA BIOS
195 Extensions and EFI-framebuffers for this, which are mostly limited
196 to x86 BIOS or EFI systems.
197 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
198 framebuffers so the new generic system-framebuffer drivers can be
199 used instead. If the framebuffer is not compatible with the generic
200 modes, it is advertised as fallback platform framebuffer so legacy
201 drivers like efifb, vesafb and uvesafb can pick it up.
202 If this option is not selected, all system framebuffers are always
203 marked as fallback platform framebuffers as usual.
204
205 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
206 not be able to pick up generic system framebuffers if this option
207 is selected. You are highly encouraged to enable simplefb as
208 replacement if you select this option. simplefb can correctly deal
209 with generic system framebuffers. But you should still keep vesafb
210 and others enabled as fallback if a system framebuffer is
211 incompatible with simplefb.
212
213 If unsure, say Y.
214
215config TI_SCI_PROTOCOL
216 tristate "TI System Control Interface (TISCI) Message Protocol"
217 depends on TI_MESSAGE_MANAGER
218 help
219 TI System Control Interface (TISCI) Message Protocol is used to manage
220 compute systems such as ARM, DSP etc with the system controller in
221 complex System on Chip(SoC) such as those found on certain keystone
222 generation SoC from TI.
223
224 System controller provides various facilities including power
225 management function support.
226
227 This protocol library is used by client drivers to use the features
228 provided by the system controller.
229
230config TRUSTED_FOUNDATIONS
231 bool "Trusted Foundations secure monitor support"
232 depends on ARM && CPU_V7
233 help
234 Some devices (including most early Tegra-based consumer devices on
235 the market) are booted with the Trusted Foundations secure monitor
236 active, requiring some core operations to be performed by the secure
237 monitor instead of the kernel.
238
239 This option allows the kernel to invoke the secure monitor whenever
240 required on devices using Trusted Foundations. See the functions and
241 comments in linux/firmware/trusted_foundations.h or the device tree
242 bindings for "tlm,trusted-foundations" for details on how to use it.
243
244 Choose N if you don't know what this is about.
245
246config TURRIS_MOX_RWTM
247 tristate "Turris Mox rWTM secure firmware driver"
248 depends on ARCH_MVEBU || COMPILE_TEST
249 depends on HAS_DMA && OF
250 depends on MAILBOX
251 select HW_RANDOM
252 select ARMADA_37XX_RWTM_MBOX
253 help
254 This driver communicates with the firmware on the Cortex-M3 secure
255 processor of the Turris Mox router. Enable if you are building for
256 Turris Mox, and you will be able to read the device serial number and
257 other manufacturing data and also utilize the Entropy Bit Generator
258 for hardware random number generation.
259
260source "drivers/firmware/arm_ffa/Kconfig"
261source "drivers/firmware/broadcom/Kconfig"
262source "drivers/firmware/cirrus/Kconfig"
263source "drivers/firmware/google/Kconfig"
264source "drivers/firmware/efi/Kconfig"
265source "drivers/firmware/imx/Kconfig"
266source "drivers/firmware/meson/Kconfig"
267source "drivers/firmware/microchip/Kconfig"
268source "drivers/firmware/psci/Kconfig"
269source "drivers/firmware/qcom/Kconfig"
270source "drivers/firmware/smccc/Kconfig"
271source "drivers/firmware/tegra/Kconfig"
272source "drivers/firmware/xilinx/Kconfig"
273
274endmenu
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 ARM_PSCI_FW
9 bool
10
11config ARM_PSCI_CHECKER
12 bool "ARM PSCI checker"
13 depends on ARM_PSCI_FW && HOTPLUG_CPU && !TORTURE_TEST
14 help
15 Run the PSCI checker during startup. This checks that hotplug and
16 suspend operations work correctly when using PSCI.
17
18 The torture tests may interfere with the PSCI checker by turning CPUs
19 on and off through hotplug, so for now torture tests and PSCI checker
20 are mutually exclusive.
21
22config ARM_SCPI_PROTOCOL
23 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
24 depends on MAILBOX
25 help
26 System Control and Power Interface (SCPI) Message Protocol is
27 defined for the purpose of communication between the Application
28 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
29 provides a mechanism for inter-processor communication between SCP
30 and AP.
31
32 SCP controls most of the power managament on the Application
33 Processors. It offers control and management of: the core/cluster
34 power states, various power domain DVFS including the core/cluster,
35 certain system clocks configuration, thermal sensors and many
36 others.
37
38 This protocol library provides interface for all the client drivers
39 making use of the features offered by the SCP.
40
41config ARM_SCPI_POWER_DOMAIN
42 tristate "SCPI power domain driver"
43 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
44 default y
45 select PM_GENERIC_DOMAINS if PM
46 help
47 This enables support for the SCPI power domains which can be
48 enabled or disabled via the SCP firmware
49
50config EDD
51 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
52 depends on X86
53 help
54 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
55 Services real mode BIOS calls to determine which disk
56 BIOS tries boot from. This information is then exported via sysfs.
57
58 This option is experimental and is known to fail to boot on some
59 obscure configurations. Most disk controller BIOS vendors do
60 not yet implement this feature.
61
62config EDD_OFF
63 bool "Sets default behavior for EDD detection to off"
64 depends on EDD
65 default n
66 help
67 Say Y if you want EDD disabled by default, even though it is compiled into the
68 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
69 using the kernel parameter 'edd={on|skipmbr|off}'.
70
71config FIRMWARE_MEMMAP
72 bool "Add firmware-provided memory map to sysfs" if EXPERT
73 default X86
74 help
75 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
76 That memory map is used for example by kexec to set up parameter area
77 for the next kernel, but can also be used for debugging purposes.
78
79 See also Documentation/ABI/testing/sysfs-firmware-memmap.
80
81config EFI_PCDP
82 bool "Console device selection via EFI PCDP or HCDP table"
83 depends on ACPI && EFI && IA64
84 default y if IA64
85 help
86 If your firmware supplies the PCDP table, and you want to
87 automatically use the primary console device it describes
88 as the Linux console, say Y here.
89
90 If your firmware supplies the HCDP table, and you want to
91 use the first serial port it describes as the Linux console,
92 say Y here. If your EFI ConOut path contains only a UART
93 device, it will become the console automatically. Otherwise,
94 you must specify the "console=hcdp" kernel boot argument.
95
96 Neither the PCDP nor the HCDP affects naming of serial devices,
97 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
98 on how the driver discovers devices.
99
100 You must also enable the appropriate drivers (serial, VGA, etc.)
101
102 See DIG64_HCDPv20_042804.pdf available from
103 <http://www.dig64.org/specifications/>
104
105config DELL_RBU
106 tristate "BIOS update support for DELL systems via sysfs"
107 depends on X86
108 select FW_LOADER
109 select FW_LOADER_USER_HELPER
110 help
111 Say m if you want to have the option of updating the BIOS for your
112 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
113 supporting application to communicate with the BIOS regarding the new
114 image for the image update to take effect.
115 See <file:Documentation/dell_rbu.txt> for more details on the driver.
116
117config DCDBAS
118 tristate "Dell Systems Management Base Driver"
119 depends on X86
120 help
121 The Dell Systems Management Base Driver provides a sysfs interface
122 for systems management software to perform System Management
123 Interrupts (SMIs) and Host Control Actions (system power cycle or
124 power off after OS shutdown) on certain Dell systems.
125
126 See <file:Documentation/dcdbas.txt> for more details on the driver
127 and the Dell systems on which Dell systems management software makes
128 use of this driver.
129
130 Say Y or M here to enable the driver for use by Dell systems
131 management software such as Dell OpenManage.
132
133config DMIID
134 bool "Export DMI identification via sysfs to userspace"
135 depends on DMI
136 default y
137 help
138 Say Y here if you want to query SMBIOS/DMI system identification
139 information from userspace through /sys/class/dmi/id/ or if you want
140 DMI-based module auto-loading.
141
142config DMI_SYSFS
143 tristate "DMI table support in sysfs"
144 depends on SYSFS && DMI
145 default n
146 help
147 Say Y or M here to enable the exporting of the raw DMI table
148 data via sysfs. This is useful for consuming the data without
149 requiring any access to /dev/mem at all. Tables are found
150 under /sys/firmware/dmi when this option is enabled and
151 loaded.
152
153config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
154 bool
155
156config ISCSI_IBFT_FIND
157 bool "iSCSI Boot Firmware Table Attributes"
158 depends on X86 && ACPI
159 default n
160 help
161 This option enables the kernel to find the region of memory
162 in which the ISCSI Boot Firmware Table (iBFT) resides. This
163 is necessary for iSCSI Boot Firmware Table Attributes module to work
164 properly.
165
166config ISCSI_IBFT
167 tristate "iSCSI Boot Firmware Table Attributes module"
168 select ISCSI_BOOT_SYSFS
169 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
170 default n
171 help
172 This option enables support for detection and exposing of iSCSI
173 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
174 detect iSCSI boot parameters dynamically during system boot, say Y.
175 Otherwise, say N.
176
177config RASPBERRYPI_FIRMWARE
178 tristate "Raspberry Pi Firmware Driver"
179 depends on BCM2835_MBOX
180 help
181 This option enables support for communicating with the firmware on the
182 Raspberry Pi.
183
184config FW_CFG_SYSFS
185 tristate "QEMU fw_cfg device support in sysfs"
186 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
187 depends on HAS_IOPORT_MAP
188 default n
189 help
190 Say Y or M here to enable the exporting of the QEMU firmware
191 configuration (fw_cfg) file entries via sysfs. Entries are
192 found under /sys/firmware/fw_cfg when this option is enabled
193 and loaded.
194
195config FW_CFG_SYSFS_CMDLINE
196 bool "QEMU fw_cfg device parameter parsing"
197 depends on FW_CFG_SYSFS
198 help
199 Allow the qemu_fw_cfg device to be initialized via the kernel
200 command line or using a module parameter.
201 WARNING: Using incorrect parameters (base address in particular)
202 may crash your system.
203
204config QCOM_SCM
205 bool
206 depends on ARM || ARM64
207 select RESET_CONTROLLER
208
209config QCOM_SCM_32
210 def_bool y
211 depends on QCOM_SCM && ARM
212
213config QCOM_SCM_64
214 def_bool y
215 depends on QCOM_SCM && ARM64
216
217config TI_SCI_PROTOCOL
218 tristate "TI System Control Interface (TISCI) Message Protocol"
219 depends on TI_MESSAGE_MANAGER
220 help
221 TI System Control Interface (TISCI) Message Protocol is used to manage
222 compute systems such as ARM, DSP etc with the system controller in
223 complex System on Chip(SoC) such as those found on certain keystone
224 generation SoC from TI.
225
226 System controller provides various facilities including power
227 management function support.
228
229 This protocol library is used by client drivers to use the features
230 provided by the system controller.
231
232config HAVE_ARM_SMCCC
233 bool
234
235source "drivers/firmware/broadcom/Kconfig"
236source "drivers/firmware/google/Kconfig"
237source "drivers/firmware/efi/Kconfig"
238source "drivers/firmware/meson/Kconfig"
239source "drivers/firmware/tegra/Kconfig"
240
241endmenu