blob: 6a42a098fe59c753d2e0733e1005257470d9f699 [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 Rutlandbff607922015-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"
Sudeep Holla8f1498c2016-06-05 18:23:21 +010024 depends on MAILBOX
Sudeep Holla8cb7cf52015-03-30 10:59:52 +010025 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
Sudeep Holla8bec4332016-06-02 16:34:03 +010041config ARM_SCPI_POWER_DOMAIN
42 tristate "SCPI power domain driver"
Arnd Bergmanne517dfe2016-07-06 14:49:46 +020043 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
Sudeep Holla8bec4332016-06-02 16:34:03 +010044 default y
45 select PM_GENERIC_DOMAINS if PM
Sudeep Holla8bec4332016-06-02 16:34:03 +010046 help
47 This enables support for the SCPI power domains which can be
48 enabled or disabled via the SCP firmware
49
Linus Torvalds1da177e2005-04-16 15:20:36 -070050config EDD
Chris Wedgwood5d186392006-06-25 05:47:46 -070051 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080052 depends on X86
Linus Torvalds1da177e2005-04-16 15:20:36 -070053 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
Tim Gardner8c4dd602008-04-29 01:02:45 -070062config 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
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020071config FIRMWARE_MEMMAP
David Rientjes6a108a12011-01-20 14:44:16 -080072 bool "Add firmware-provided memory map to sysfs" if EXPERT
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080073 default X86
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020074 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070081config 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
Justin P. Mattock631dd1a2010-10-18 11:03:14 +0200102 See DIG64_HCDPv20_042804.pdf available from
103 <http://www.dig64.org/specifications/>
Linus Torvalds1da177e2005-04-16 15:20:36 -0700104
Abhay Salunke6c54c282005-09-06 15:17:14 -0700105config DELL_RBU
106 tristate "BIOS update support for DELL systems via sysfs"
Dave Jones6c52f132005-11-21 21:32:30 -0800107 depends on X86
Abhay Salunke6c54c282005-09-06 15:17:14 -0700108 select FW_LOADER
Takashi Iwaid05c39e2013-05-22 18:28:37 +0200109 select FW_LOADER_USER_HELPER
Abhay Salunke6c54c282005-09-06 15:17:14 -0700110 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)
Matt LaPlante09509602006-10-03 22:31:37 +0200113 supporting application to communicate with the BIOS regarding the new
Abhay Salunke6c54c282005-09-06 15:17:14 -0700114 image for the image update to take effect.
115 See <file:Documentation/dell_rbu.txt> for more details on the driver.
Doug Warzecha90563ec2005-09-06 15:17:15 -0700116
117config DCDBAS
118 tristate "Dell Systems Management Base Driver"
Brian Gerst0d078f62005-10-30 14:59:20 -0800119 depends on X86
Doug Warzecha90563ec2005-09-06 15:17:15 -0700120 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
Lennart Poettering4f5c7912007-05-08 22:07:02 +0200133config 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
Mike Waychison948af1f2011-02-22 17:53:21 -0800142config 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
Ard Biesheuvelcf074402014-01-23 15:54:39 -0800153config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
154 bool
155
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700156config ISCSI_IBFT_FIND
157 bool "iSCSI Boot Firmware Table Attributes"
Lv Zheng9d246222013-12-06 16:52:19 +0800158 depends on X86 && ACPI
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700159 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"
Mike Christieb33a84a2010-04-12 18:06:18 +0000168 select ISCSI_BOOT_SYSFS
Randy Dunlap3e0f6862010-10-13 18:07:16 -0700169 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700170 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
Eric Anholt4e3d6062015-02-26 10:08:06 +0000177config 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
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500184config FW_CFG_SYSFS
185 tristate "QEMU fw_cfg device support in sysfs"
186 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
Arnd Bergmann28c09ec2016-02-11 15:23:51 +0100187 depends on HAS_IOPORT_MAP
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500188 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
Kumar Gala916f743d2015-02-26 15:49:09 -0600204config QCOM_SCM
205 bool
206 depends on ARM || ARM64
Bjorn Anderssondd4fe5b2016-06-17 10:40:43 -0700207 select RESET_CONTROLLER
Kumar Gala916f743d2015-02-26 15:49:09 -0600208
Andy Gross50b956f2015-09-11 16:01:16 -0500209config 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
Jens Wiklander98dd64f2016-01-04 15:37:32 +0100217config HAVE_ARM_SMCCC
218 bool
219
Rafał Miłeckif6e734a2015-06-10 23:05:08 +0200220source "drivers/firmware/broadcom/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700221source "drivers/firmware/google/Kconfig"
Matt Fleming04851772013-02-08 15:48:51 +0000222source "drivers/firmware/efi/Kconfig"
Carlo Caione2c4ddb22016-08-27 15:43:43 +0200223source "drivers/firmware/meson/Kconfig"
Thierry Redingca791d72016-08-19 19:05:04 +0200224source "drivers/firmware/tegra/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700225
Linus Torvalds1da177e2005-04-16 15:20:36 -0700226endmenu