blob: 6664f1108c7c2f8c54a3d1d0f32f6c1c7f622bb3 [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
Sudeep Holla8cb7cf52015-03-30 10:59:52 +010011config ARM_SCPI_PROTOCOL
12 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
13 depends on ARM_MHU
14 help
15 System Control and Power Interface (SCPI) Message Protocol is
16 defined for the purpose of communication between the Application
17 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
18 provides a mechanism for inter-processor communication between SCP
19 and AP.
20
21 SCP controls most of the power managament on the Application
22 Processors. It offers control and management of: the core/cluster
23 power states, various power domain DVFS including the core/cluster,
24 certain system clocks configuration, thermal sensors and many
25 others.
26
27 This protocol library provides interface for all the client drivers
28 making use of the features offered by the SCP.
29
Linus Torvalds1da177e2005-04-16 15:20:36 -070030config EDD
Chris Wedgwood5d186392006-06-25 05:47:46 -070031 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080032 depends on X86
Linus Torvalds1da177e2005-04-16 15:20:36 -070033 help
34 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
35 Services real mode BIOS calls to determine which disk
36 BIOS tries boot from. This information is then exported via sysfs.
37
38 This option is experimental and is known to fail to boot on some
39 obscure configurations. Most disk controller BIOS vendors do
40 not yet implement this feature.
41
Tim Gardner8c4dd602008-04-29 01:02:45 -070042config EDD_OFF
43 bool "Sets default behavior for EDD detection to off"
44 depends on EDD
45 default n
46 help
47 Say Y if you want EDD disabled by default, even though it is compiled into the
48 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
49 using the kernel parameter 'edd={on|skipmbr|off}'.
50
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020051config FIRMWARE_MEMMAP
David Rientjes6a108a12011-01-20 14:44:16 -080052 bool "Add firmware-provided memory map to sysfs" if EXPERT
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080053 default X86
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020054 help
55 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
56 That memory map is used for example by kexec to set up parameter area
57 for the next kernel, but can also be used for debugging purposes.
58
59 See also Documentation/ABI/testing/sysfs-firmware-memmap.
60
Linus Torvalds1da177e2005-04-16 15:20:36 -070061config EFI_PCDP
62 bool "Console device selection via EFI PCDP or HCDP table"
63 depends on ACPI && EFI && IA64
64 default y if IA64
65 help
66 If your firmware supplies the PCDP table, and you want to
67 automatically use the primary console device it describes
68 as the Linux console, say Y here.
69
70 If your firmware supplies the HCDP table, and you want to
71 use the first serial port it describes as the Linux console,
72 say Y here. If your EFI ConOut path contains only a UART
73 device, it will become the console automatically. Otherwise,
74 you must specify the "console=hcdp" kernel boot argument.
75
76 Neither the PCDP nor the HCDP affects naming of serial devices,
77 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
78 on how the driver discovers devices.
79
80 You must also enable the appropriate drivers (serial, VGA, etc.)
81
Justin P. Mattock631dd1a2010-10-18 11:03:14 +020082 See DIG64_HCDPv20_042804.pdf available from
83 <http://www.dig64.org/specifications/>
Linus Torvalds1da177e2005-04-16 15:20:36 -070084
Abhay Salunke6c54c282005-09-06 15:17:14 -070085config DELL_RBU
86 tristate "BIOS update support for DELL systems via sysfs"
Dave Jones6c52f132005-11-21 21:32:30 -080087 depends on X86
Abhay Salunke6c54c282005-09-06 15:17:14 -070088 select FW_LOADER
Takashi Iwaid05c39e2013-05-22 18:28:37 +020089 select FW_LOADER_USER_HELPER
Abhay Salunke6c54c282005-09-06 15:17:14 -070090 help
91 Say m if you want to have the option of updating the BIOS for your
92 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
Matt LaPlante09509602006-10-03 22:31:37 +020093 supporting application to communicate with the BIOS regarding the new
Abhay Salunke6c54c282005-09-06 15:17:14 -070094 image for the image update to take effect.
95 See <file:Documentation/dell_rbu.txt> for more details on the driver.
Doug Warzecha90563ec42005-09-06 15:17:15 -070096
97config DCDBAS
98 tristate "Dell Systems Management Base Driver"
Brian Gerst0d078f62005-10-30 14:59:20 -080099 depends on X86
Doug Warzecha90563ec42005-09-06 15:17:15 -0700100 help
101 The Dell Systems Management Base Driver provides a sysfs interface
102 for systems management software to perform System Management
103 Interrupts (SMIs) and Host Control Actions (system power cycle or
104 power off after OS shutdown) on certain Dell systems.
105
106 See <file:Documentation/dcdbas.txt> for more details on the driver
107 and the Dell systems on which Dell systems management software makes
108 use of this driver.
109
110 Say Y or M here to enable the driver for use by Dell systems
111 management software such as Dell OpenManage.
112
Lennart Poettering4f5c7912007-05-08 22:07:02 +0200113config DMIID
114 bool "Export DMI identification via sysfs to userspace"
115 depends on DMI
116 default y
117 help
118 Say Y here if you want to query SMBIOS/DMI system identification
119 information from userspace through /sys/class/dmi/id/ or if you want
120 DMI-based module auto-loading.
121
Mike Waychison948af1f2011-02-22 17:53:21 -0800122config DMI_SYSFS
123 tristate "DMI table support in sysfs"
124 depends on SYSFS && DMI
125 default n
126 help
127 Say Y or M here to enable the exporting of the raw DMI table
128 data via sysfs. This is useful for consuming the data without
129 requiring any access to /dev/mem at all. Tables are found
130 under /sys/firmware/dmi when this option is enabled and
131 loaded.
132
Ard Biesheuvelcf074402014-01-23 15:54:39 -0800133config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
134 bool
135
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700136config ISCSI_IBFT_FIND
137 bool "iSCSI Boot Firmware Table Attributes"
Lv Zheng9d246222013-12-06 16:52:19 +0800138 depends on X86 && ACPI
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700139 default n
140 help
141 This option enables the kernel to find the region of memory
142 in which the ISCSI Boot Firmware Table (iBFT) resides. This
143 is necessary for iSCSI Boot Firmware Table Attributes module to work
144 properly.
145
146config ISCSI_IBFT
147 tristate "iSCSI Boot Firmware Table Attributes module"
Mike Christieb33a84a2010-04-12 18:06:18 +0000148 select ISCSI_BOOT_SYSFS
Randy Dunlap3e0f6862010-10-13 18:07:16 -0700149 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700150 default n
151 help
152 This option enables support for detection and exposing of iSCSI
153 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
154 detect iSCSI boot parameters dynamically during system boot, say Y.
155 Otherwise, say N.
156
Eric Anholt4e3d6062015-02-26 10:08:06 +0000157config RASPBERRYPI_FIRMWARE
158 tristate "Raspberry Pi Firmware Driver"
159 depends on BCM2835_MBOX
160 help
161 This option enables support for communicating with the firmware on the
162 Raspberry Pi.
163
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500164config FW_CFG_SYSFS
165 tristate "QEMU fw_cfg device support in sysfs"
166 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
Arnd Bergmann28c09ec2016-02-11 15:23:51 +0100167 depends on HAS_IOPORT_MAP
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500168 default n
169 help
170 Say Y or M here to enable the exporting of the QEMU firmware
171 configuration (fw_cfg) file entries via sysfs. Entries are
172 found under /sys/firmware/fw_cfg when this option is enabled
173 and loaded.
174
175config FW_CFG_SYSFS_CMDLINE
176 bool "QEMU fw_cfg device parameter parsing"
177 depends on FW_CFG_SYSFS
178 help
179 Allow the qemu_fw_cfg device to be initialized via the kernel
180 command line or using a module parameter.
181 WARNING: Using incorrect parameters (base address in particular)
182 may crash your system.
183
Kumar Gala916f743d2015-02-26 15:49:09 -0600184config QCOM_SCM
185 bool
186 depends on ARM || ARM64
187
Andy Gross50b956f2015-09-11 16:01:16 -0500188config QCOM_SCM_32
189 def_bool y
190 depends on QCOM_SCM && ARM
191
192config QCOM_SCM_64
193 def_bool y
194 depends on QCOM_SCM && ARM64
195
Jens Wiklander98dd64f2016-01-04 15:37:32 +0100196config HAVE_ARM_SMCCC
197 bool
198
Rafał Miłeckif6e734a2015-06-10 23:05:08 +0200199source "drivers/firmware/broadcom/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700200source "drivers/firmware/google/Kconfig"
Matt Fleming04851772013-02-08 15:48:51 +0000201source "drivers/firmware/efi/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700202
Linus Torvalds1da177e2005-04-16 15:20:36 -0700203endmenu