Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
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 && CPU_IDLE && !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_SCMI_PROTOCOL
23 bool "ARM System Control and Management Interface (SCMI) Message Protocol"
24 depends on ARM || ARM64 || COMPILE_TEST
25 depends on MAILBOX
26 help
27 ARM System Control and Management Interface (SCMI) protocol is a
28 set of operating system-independent software interfaces that are
29 used in system management. SCMI is extensible and currently provides
30 interfaces for: Discovery and self-description of the interfaces
31 it supports, Power domain management which is the ability to place
32 a given device or domain into the various power-saving states that
33 it supports, Performance management which is the ability to control
34 the performance of a domain that is composed of compute engines
35 such as application processors and other accelerators, Clock
36 management which is the ability to set and inquire rates on platform
37 managed clocks and Sensor management which is the ability to read
38 sensor data, and be notified of sensor value.
39
40 This protocol library provides interface for all the client drivers
41 making use of the features offered by the SCMI.
42
43config ARM_SCMI_POWER_DOMAIN
44 tristate "SCMI power domain driver"
45 depends on ARM_SCMI_PROTOCOL || (COMPILE_TEST && OF)
46 default y
47 select PM_GENERIC_DOMAINS if PM
48 help
49 This enables support for the SCMI power domains which can be
50 enabled or disabled via the SCP firmware
51
52 This driver can also be built as a module. If so, the module
53 will be called scmi_pm_domain. Note this may needed early in boot
54 before rootfs may be available.
55
56config ARM_SCPI_PROTOCOL
57 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
58 depends on ARM || ARM64 || COMPILE_TEST
59 depends on MAILBOX
60 help
61 System Control and Power Interface (SCPI) Message Protocol is
62 defined for the purpose of communication between the Application
63 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
64 provides a mechanism for inter-processor communication between SCP
65 and AP.
66
67 SCP controls most of the power managament on the Application
68 Processors. It offers control and management of: the core/cluster
69 power states, various power domain DVFS including the core/cluster,
70 certain system clocks configuration, thermal sensors and many
71 others.
72
73 This protocol library provides interface for all the client drivers
74 making use of the features offered by the SCP.
75
76config ARM_SCPI_POWER_DOMAIN
77 tristate "SCPI power domain driver"
78 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
79 default y
80 select PM_GENERIC_DOMAINS if PM
81 help
82 This enables support for the SCPI power domains which can be
83 enabled or disabled via the SCP firmware
84
85config ARM_SDE_INTERFACE
86 bool "ARM Software Delegated Exception Interface (SDEI)"
87 depends on ARM64
88 help
89 The Software Delegated Exception Interface (SDEI) is an ARM
90 standard for registering callbacks from the platform firmware
91 into the OS. This is typically used to implement RAS notifications.
92
93config EDD
94 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
95 depends on X86
96 help
97 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
98 Services real mode BIOS calls to determine which disk
99 BIOS tries boot from. This information is then exported via sysfs.
100
101 This option is experimental and is known to fail to boot on some
102 obscure configurations. Most disk controller BIOS vendors do
103 not yet implement this feature.
104
105config EDD_OFF
106 bool "Sets default behavior for EDD detection to off"
107 depends on EDD
108 default n
109 help
110 Say Y if you want EDD disabled by default, even though it is compiled into the
111 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
112 using the kernel parameter 'edd={on|skipmbr|off}'.
113
114config FIRMWARE_MEMMAP
115 bool "Add firmware-provided memory map to sysfs" if EXPERT
116 default X86
117 help
118 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
119 That memory map is used for example by kexec to set up parameter area
120 for the next kernel, but can also be used for debugging purposes.
121
122 See also Documentation/ABI/testing/sysfs-firmware-memmap.
123
124config EFI_PCDP
125 bool "Console device selection via EFI PCDP or HCDP table"
126 depends on ACPI && EFI && IA64
127 default y if IA64
128 help
129 If your firmware supplies the PCDP table, and you want to
130 automatically use the primary console device it describes
131 as the Linux console, say Y here.
132
133 If your firmware supplies the HCDP table, and you want to
134 use the first serial port it describes as the Linux console,
135 say Y here. If your EFI ConOut path contains only a UART
136 device, it will become the console automatically. Otherwise,
137 you must specify the "console=hcdp" kernel boot argument.
138
139 Neither the PCDP nor the HCDP affects naming of serial devices,
140 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
141 on how the driver discovers devices.
142
143 You must also enable the appropriate drivers (serial, VGA, etc.)
144
145 See DIG64_HCDPv20_042804.pdf available from
146 <http://www.dig64.org/specifications/>
147
148config DMIID
149 bool "Export DMI identification via sysfs to userspace"
150 depends on DMI
151 default y
152 help
153 Say Y here if you want to query SMBIOS/DMI system identification
154 information from userspace through /sys/class/dmi/id/ or if you want
155 DMI-based module auto-loading.
156
157config DMI_SYSFS
158 tristate "DMI table support in sysfs"
159 depends on SYSFS && DMI
160 default n
161 help
162 Say Y or M here to enable the exporting of the raw DMI table
163 data via sysfs. This is useful for consuming the data without
164 requiring any access to /dev/mem at all. Tables are found
165 under /sys/firmware/dmi when this option is enabled and
166 loaded.
167
168config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
169 bool
170
171config ISCSI_IBFT_FIND
172 bool "iSCSI Boot Firmware Table Attributes"
173 depends on X86 && ACPI
174 default n
175 help
176 This option enables the kernel to find the region of memory
177 in which the ISCSI Boot Firmware Table (iBFT) resides. This
178 is necessary for iSCSI Boot Firmware Table Attributes module to work
179 properly.
180
181config ISCSI_IBFT
182 tristate "iSCSI Boot Firmware Table Attributes module"
183 select ISCSI_BOOT_SYSFS
184 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
185 default n
186 help
187 This option enables support for detection and exposing of iSCSI
188 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
189 detect iSCSI boot parameters dynamically during system boot, say Y.
190 Otherwise, say N.
191
192config RASPBERRYPI_FIRMWARE
193 tristate "Raspberry Pi Firmware Driver"
194 depends on BCM2835_MBOX
195 help
196 This option enables support for communicating with the firmware on the
197 Raspberry Pi.
198
199config FW_CFG_SYSFS
200 tristate "QEMU fw_cfg device support in sysfs"
201 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
202 depends on HAS_IOPORT_MAP
203 default n
204 help
205 Say Y or M here to enable the exporting of the QEMU firmware
206 configuration (fw_cfg) file entries via sysfs. Entries are
207 found under /sys/firmware/fw_cfg when this option is enabled
208 and loaded.
209
210config FW_CFG_SYSFS_CMDLINE
211 bool "QEMU fw_cfg device parameter parsing"
212 depends on FW_CFG_SYSFS
213 help
214 Allow the qemu_fw_cfg device to be initialized via the kernel
215 command line or using a module parameter.
216 WARNING: Using incorrect parameters (base address in particular)
217 may crash your system.
218
219config INTEL_STRATIX10_SERVICE
220 tristate "Intel Stratix10 Service Layer"
221 depends on HAVE_ARM_SMCCC
222 default n
223 help
224 Intel Stratix10 service layer runs at privileged exception level,
225 interfaces with the service providers (FPGA manager is one of them)
226 and manages secure monitor call to communicate with secure monitor
227 software at secure monitor exception level.
228
229 Say Y here if you want Stratix10 service layer support.
230
231config QCOM_SCM
232 bool
233 depends on ARM || ARM64
234 select RESET_CONTROLLER
235
236config QCOM_SCM_32
237 def_bool y
238 depends on QCOM_SCM && ARM
239
240config QCOM_SCM_64
241 def_bool y
242 depends on QCOM_SCM && ARM64
243
244config QCOM_SCM_DOWNLOAD_MODE_DEFAULT
245 bool "Qualcomm download mode enabled by default"
246 depends on QCOM_SCM
247 help
248 A device with "download mode" enabled will upon an unexpected
249 warm-restart enter a special debug mode that allows the user to
250 "download" memory content over USB for offline postmortem analysis.
251 The feature can be enabled/disabled on the kernel command line.
252
253 Say Y here to enable "download mode" by default.
254
255config TI_SCI_PROTOCOL
256 tristate "TI System Control Interface (TISCI) Message Protocol"
257 depends on TI_MESSAGE_MANAGER
258 help
259 TI System Control Interface (TISCI) Message Protocol is used to manage
260 compute systems such as ARM, DSP etc with the system controller in
261 complex System on Chip(SoC) such as those found on certain keystone
262 generation SoC from TI.
263
264 System controller provides various facilities including power
265 management function support.
266
267 This protocol library is used by client drivers to use the features
268 provided by the system controller.
269
270config HAVE_ARM_SMCCC
271 bool
272
273source "drivers/firmware/broadcom/Kconfig"
274source "drivers/firmware/google/Kconfig"
275source "drivers/firmware/efi/Kconfig"
276source "drivers/firmware/imx/Kconfig"
277source "drivers/firmware/meson/Kconfig"
278source "drivers/firmware/tegra/Kconfig"
279source "drivers/firmware/xilinx/Kconfig"
280
281endmenu