blob: 89c5f3651c3bf7dfdb3c5279db01a6df5107d3b2 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# For a description of the syntax of this configuration file,
3# see Documentation/kbuild/kconfig-language.txt.
4#
5
6menu "Firmware Drivers"
7
Mark Rutlandbff60792015-07-31 15:46:16 +01008config ARM_PSCI_FW
9 bool
10
Kevin Brodskyea8b1c42016-11-08 17:55:46 +000011config 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
Sudeep Holla8cb7cf52015-03-30 10:59:52 +010022config ARM_SCPI_PROTOCOL
23 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
Jean Delvare92f3e6e2017-01-30 09:52:01 +010024 depends on ARM || ARM64 || COMPILE_TEST
Sudeep Holla8f1498c2016-06-05 18:23:21 +010025 depends on MAILBOX
Sudeep Holla8cb7cf52015-03-30 10:59:52 +010026 help
27 System Control and Power Interface (SCPI) Message Protocol is
28 defined for the purpose of communication between the Application
29 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
30 provides a mechanism for inter-processor communication between SCP
31 and AP.
32
33 SCP controls most of the power managament on the Application
34 Processors. It offers control and management of: the core/cluster
35 power states, various power domain DVFS including the core/cluster,
36 certain system clocks configuration, thermal sensors and many
37 others.
38
39 This protocol library provides interface for all the client drivers
40 making use of the features offered by the SCP.
41
Sudeep Holla8bec4332016-06-02 16:34:03 +010042config ARM_SCPI_POWER_DOMAIN
43 tristate "SCPI power domain driver"
Arnd Bergmanne517dfe2016-07-06 14:49:46 +020044 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
Sudeep Holla8bec4332016-06-02 16:34:03 +010045 default y
46 select PM_GENERIC_DOMAINS if PM
Sudeep Holla8bec4332016-06-02 16:34:03 +010047 help
48 This enables support for the SCPI power domains which can be
49 enabled or disabled via the SCP firmware
50
Linus Torvalds1da177e2005-04-16 15:20:36 -070051config EDD
Chris Wedgwood5d186392006-06-25 05:47:46 -070052 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080053 depends on X86
Linus Torvalds1da177e2005-04-16 15:20:36 -070054 help
55 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
56 Services real mode BIOS calls to determine which disk
57 BIOS tries boot from. This information is then exported via sysfs.
58
59 This option is experimental and is known to fail to boot on some
60 obscure configurations. Most disk controller BIOS vendors do
61 not yet implement this feature.
62
Tim Gardner8c4dd602008-04-29 01:02:45 -070063config EDD_OFF
64 bool "Sets default behavior for EDD detection to off"
65 depends on EDD
66 default n
67 help
68 Say Y if you want EDD disabled by default, even though it is compiled into the
69 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
70 using the kernel parameter 'edd={on|skipmbr|off}'.
71
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020072config FIRMWARE_MEMMAP
David Rientjes6a108a12011-01-20 14:44:16 -080073 bool "Add firmware-provided memory map to sysfs" if EXPERT
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080074 default X86
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020075 help
76 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
77 That memory map is used for example by kexec to set up parameter area
78 for the next kernel, but can also be used for debugging purposes.
79
80 See also Documentation/ABI/testing/sysfs-firmware-memmap.
81
Linus Torvalds1da177e2005-04-16 15:20:36 -070082config EFI_PCDP
83 bool "Console device selection via EFI PCDP or HCDP table"
84 depends on ACPI && EFI && IA64
85 default y if IA64
86 help
87 If your firmware supplies the PCDP table, and you want to
88 automatically use the primary console device it describes
89 as the Linux console, say Y here.
90
91 If your firmware supplies the HCDP table, and you want to
92 use the first serial port it describes as the Linux console,
93 say Y here. If your EFI ConOut path contains only a UART
94 device, it will become the console automatically. Otherwise,
95 you must specify the "console=hcdp" kernel boot argument.
96
97 Neither the PCDP nor the HCDP affects naming of serial devices,
98 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
99 on how the driver discovers devices.
100
101 You must also enable the appropriate drivers (serial, VGA, etc.)
102
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200103 See DIG64_HCDPv20_042804.pdf available from
104 <http://www.dig64.org/specifications/>
Linus Torvalds1da177e2005-04-16 15:20:36 -0700105
Abhay Salunke6c54c282005-09-06 15:17:14 -0700106config DELL_RBU
107 tristate "BIOS update support for DELL systems via sysfs"
Dave Jones6c52f132005-11-21 21:32:30 -0800108 depends on X86
Abhay Salunke6c54c282005-09-06 15:17:14 -0700109 select FW_LOADER
Takashi Iwaid05c39e2013-05-22 18:28:37 +0200110 select FW_LOADER_USER_HELPER
Abhay Salunke6c54c282005-09-06 15:17:14 -0700111 help
112 Say m if you want to have the option of updating the BIOS for your
113 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
Matt LaPlante09509602006-10-03 22:31:37 +0200114 supporting application to communicate with the BIOS regarding the new
Abhay Salunke6c54c282005-09-06 15:17:14 -0700115 image for the image update to take effect.
116 See <file:Documentation/dell_rbu.txt> for more details on the driver.
Doug Warzecha90563ec2005-09-06 15:17:15 -0700117
118config DCDBAS
119 tristate "Dell Systems Management Base Driver"
Brian Gerst0d078f62005-10-30 14:59:20 -0800120 depends on X86
Doug Warzecha90563ec2005-09-06 15:17:15 -0700121 help
122 The Dell Systems Management Base Driver provides a sysfs interface
123 for systems management software to perform System Management
124 Interrupts (SMIs) and Host Control Actions (system power cycle or
125 power off after OS shutdown) on certain Dell systems.
126
127 See <file:Documentation/dcdbas.txt> for more details on the driver
128 and the Dell systems on which Dell systems management software makes
129 use of this driver.
130
131 Say Y or M here to enable the driver for use by Dell systems
132 management software such as Dell OpenManage.
133
Lennart Poettering4f5c7912007-05-08 22:07:02 +0200134config DMIID
135 bool "Export DMI identification via sysfs to userspace"
136 depends on DMI
137 default y
138 help
139 Say Y here if you want to query SMBIOS/DMI system identification
140 information from userspace through /sys/class/dmi/id/ or if you want
141 DMI-based module auto-loading.
142
Mike Waychison948af1f2011-02-22 17:53:21 -0800143config DMI_SYSFS
144 tristate "DMI table support in sysfs"
145 depends on SYSFS && DMI
146 default n
147 help
148 Say Y or M here to enable the exporting of the raw DMI table
149 data via sysfs. This is useful for consuming the data without
150 requiring any access to /dev/mem at all. Tables are found
151 under /sys/firmware/dmi when this option is enabled and
152 loaded.
153
Ard Biesheuvelcf074402014-01-23 15:54:39 -0800154config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
155 bool
156
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700157config ISCSI_IBFT_FIND
158 bool "iSCSI Boot Firmware Table Attributes"
Thomas Taia3e7eb52019-07-18 18:37:34 +0000159 depends on X86 && ISCSI_IBFT
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700160 default n
161 help
162 This option enables the kernel to find the region of memory
163 in which the ISCSI Boot Firmware Table (iBFT) resides. This
164 is necessary for iSCSI Boot Firmware Table Attributes module to work
165 properly.
166
167config ISCSI_IBFT
168 tristate "iSCSI Boot Firmware Table Attributes module"
Mike Christieb33a84a2010-04-12 18:06:18 +0000169 select ISCSI_BOOT_SYSFS
Thomas Taia3e7eb52019-07-18 18:37:34 +0000170 select ISCSI_IBFT_FIND if X86
171 depends on ACPI && SCSI && SCSI_LOWLEVEL
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700172 default n
173 help
174 This option enables support for detection and exposing of iSCSI
175 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
176 detect iSCSI boot parameters dynamically during system boot, say Y.
177 Otherwise, say N.
178
Eric Anholt4e3d6062015-02-26 10:08:06 +0000179config RASPBERRYPI_FIRMWARE
180 tristate "Raspberry Pi Firmware Driver"
181 depends on BCM2835_MBOX
182 help
183 This option enables support for communicating with the firmware on the
184 Raspberry Pi.
185
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500186config FW_CFG_SYSFS
187 tristate "QEMU fw_cfg device support in sysfs"
188 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
Arnd Bergmann28c09ec2016-02-11 15:23:51 +0100189 depends on HAS_IOPORT_MAP
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500190 default n
191 help
192 Say Y or M here to enable the exporting of the QEMU firmware
193 configuration (fw_cfg) file entries via sysfs. Entries are
194 found under /sys/firmware/fw_cfg when this option is enabled
195 and loaded.
196
197config FW_CFG_SYSFS_CMDLINE
198 bool "QEMU fw_cfg device parameter parsing"
199 depends on FW_CFG_SYSFS
200 help
201 Allow the qemu_fw_cfg device to be initialized via the kernel
202 command line or using a module parameter.
203 WARNING: Using incorrect parameters (base address in particular)
204 may crash your system.
205
Kumar Gala916f7432015-02-26 15:49:09 -0600206config QCOM_SCM
207 bool
208 depends on ARM || ARM64
He Ying089e8c12021-04-06 05:42:00 -0400209 depends on HAVE_ARM_SMCCC
Bjorn Anderssondd4fe5b2016-06-17 10:40:43 -0700210 select RESET_CONTROLLER
Kumar Gala916f7432015-02-26 15:49:09 -0600211
Andy Gross50b956f2015-09-11 16:01:16 -0500212config QCOM_SCM_32
213 def_bool y
214 depends on QCOM_SCM && ARM
215
216config QCOM_SCM_64
217 def_bool y
218 depends on QCOM_SCM && ARM64
219
Nishanth Menonaa276782016-10-18 18:08:34 -0500220config TI_SCI_PROTOCOL
221 tristate "TI System Control Interface (TISCI) Message Protocol"
222 depends on TI_MESSAGE_MANAGER
223 help
224 TI System Control Interface (TISCI) Message Protocol is used to manage
225 compute systems such as ARM, DSP etc with the system controller in
226 complex System on Chip(SoC) such as those found on certain keystone
227 generation SoC from TI.
228
229 System controller provides various facilities including power
230 management function support.
231
232 This protocol library is used by client drivers to use the features
233 provided by the system controller.
234
Jens Wiklander98dd64f2016-01-04 15:37:32 +0100235config HAVE_ARM_SMCCC
236 bool
237
Rafał Miłeckif6e734a2015-06-10 23:05:08 +0200238source "drivers/firmware/broadcom/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700239source "drivers/firmware/google/Kconfig"
Matt Fleming04851772013-02-08 15:48:51 +0000240source "drivers/firmware/efi/Kconfig"
Carlo Caione2c4ddb22016-08-27 15:43:43 +0200241source "drivers/firmware/meson/Kconfig"
Thierry Redingca791d72016-08-19 19:05:04 +0200242source "drivers/firmware/tegra/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700243
Linus Torvalds1da177e2005-04-16 15:20:36 -0700244endmenu