blob: 0e22f241403bc1ce4da1e8abd5f33f6fde2ff1d4 [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
Sudeep Holla8cb7cf52015-03-30 10:59:52 +010011config ARM_SCPI_PROTOCOL
12 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
Sudeep Holla8f1498c2016-06-05 18:23:21 +010013 depends on MAILBOX
Sudeep Holla8cb7cf52015-03-30 10:59:52 +010014 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
Sudeep Holla8bec4332016-06-02 16:34:03 +010030config ARM_SCPI_POWER_DOMAIN
31 tristate "SCPI power domain driver"
Arnd Bergmanne517dfe2016-07-06 14:49:46 +020032 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
Sudeep Holla8bec4332016-06-02 16:34:03 +010033 default y
34 select PM_GENERIC_DOMAINS if PM
Sudeep Holla8bec4332016-06-02 16:34:03 +010035 help
36 This enables support for the SCPI power domains which can be
37 enabled or disabled via the SCP firmware
38
Linus Torvalds1da177e2005-04-16 15:20:36 -070039config EDD
Chris Wedgwood5d186392006-06-25 05:47:46 -070040 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080041 depends on X86
Linus Torvalds1da177e2005-04-16 15:20:36 -070042 help
43 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
44 Services real mode BIOS calls to determine which disk
45 BIOS tries boot from. This information is then exported via sysfs.
46
47 This option is experimental and is known to fail to boot on some
48 obscure configurations. Most disk controller BIOS vendors do
49 not yet implement this feature.
50
Tim Gardner8c4dd602008-04-29 01:02:45 -070051config EDD_OFF
52 bool "Sets default behavior for EDD detection to off"
53 depends on EDD
54 default n
55 help
56 Say Y if you want EDD disabled by default, even though it is compiled into the
57 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
58 using the kernel parameter 'edd={on|skipmbr|off}'.
59
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020060config FIRMWARE_MEMMAP
David Rientjes6a108a12011-01-20 14:44:16 -080061 bool "Add firmware-provided memory map to sysfs" if EXPERT
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080062 default X86
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020063 help
64 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
65 That memory map is used for example by kexec to set up parameter area
66 for the next kernel, but can also be used for debugging purposes.
67
68 See also Documentation/ABI/testing/sysfs-firmware-memmap.
69
Linus Torvalds1da177e2005-04-16 15:20:36 -070070config EFI_PCDP
71 bool "Console device selection via EFI PCDP or HCDP table"
72 depends on ACPI && EFI && IA64
73 default y if IA64
74 help
75 If your firmware supplies the PCDP table, and you want to
76 automatically use the primary console device it describes
77 as the Linux console, say Y here.
78
79 If your firmware supplies the HCDP table, and you want to
80 use the first serial port it describes as the Linux console,
81 say Y here. If your EFI ConOut path contains only a UART
82 device, it will become the console automatically. Otherwise,
83 you must specify the "console=hcdp" kernel boot argument.
84
85 Neither the PCDP nor the HCDP affects naming of serial devices,
86 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
87 on how the driver discovers devices.
88
89 You must also enable the appropriate drivers (serial, VGA, etc.)
90
Justin P. Mattock631dd1a2010-10-18 11:03:14 +020091 See DIG64_HCDPv20_042804.pdf available from
92 <http://www.dig64.org/specifications/>
Linus Torvalds1da177e2005-04-16 15:20:36 -070093
Abhay Salunke6c54c282005-09-06 15:17:14 -070094config DELL_RBU
95 tristate "BIOS update support for DELL systems via sysfs"
Dave Jones6c52f132005-11-21 21:32:30 -080096 depends on X86
Abhay Salunke6c54c282005-09-06 15:17:14 -070097 select FW_LOADER
Takashi Iwaid05c39e2013-05-22 18:28:37 +020098 select FW_LOADER_USER_HELPER
Abhay Salunke6c54c282005-09-06 15:17:14 -070099 help
100 Say m if you want to have the option of updating the BIOS for your
101 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
Matt LaPlante09509602006-10-03 22:31:37 +0200102 supporting application to communicate with the BIOS regarding the new
Abhay Salunke6c54c282005-09-06 15:17:14 -0700103 image for the image update to take effect.
104 See <file:Documentation/dell_rbu.txt> for more details on the driver.
Doug Warzecha90563ec2005-09-06 15:17:15 -0700105
106config DCDBAS
107 tristate "Dell Systems Management Base Driver"
Brian Gerst0d078f62005-10-30 14:59:20 -0800108 depends on X86
Doug Warzecha90563ec2005-09-06 15:17:15 -0700109 help
110 The Dell Systems Management Base Driver provides a sysfs interface
111 for systems management software to perform System Management
112 Interrupts (SMIs) and Host Control Actions (system power cycle or
113 power off after OS shutdown) on certain Dell systems.
114
115 See <file:Documentation/dcdbas.txt> for more details on the driver
116 and the Dell systems on which Dell systems management software makes
117 use of this driver.
118
119 Say Y or M here to enable the driver for use by Dell systems
120 management software such as Dell OpenManage.
121
Lennart Poettering4f5c7912007-05-08 22:07:02 +0200122config DMIID
123 bool "Export DMI identification via sysfs to userspace"
124 depends on DMI
125 default y
126 help
127 Say Y here if you want to query SMBIOS/DMI system identification
128 information from userspace through /sys/class/dmi/id/ or if you want
129 DMI-based module auto-loading.
130
Mike Waychison948af1f2011-02-22 17:53:21 -0800131config DMI_SYSFS
132 tristate "DMI table support in sysfs"
133 depends on SYSFS && DMI
134 default n
135 help
136 Say Y or M here to enable the exporting of the raw DMI table
137 data via sysfs. This is useful for consuming the data without
138 requiring any access to /dev/mem at all. Tables are found
139 under /sys/firmware/dmi when this option is enabled and
140 loaded.
141
Ard Biesheuvelcf074402014-01-23 15:54:39 -0800142config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
143 bool
144
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700145config ISCSI_IBFT_FIND
146 bool "iSCSI Boot Firmware Table Attributes"
Lv Zheng9d246222013-12-06 16:52:19 +0800147 depends on X86 && ACPI
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700148 default n
149 help
150 This option enables the kernel to find the region of memory
151 in which the ISCSI Boot Firmware Table (iBFT) resides. This
152 is necessary for iSCSI Boot Firmware Table Attributes module to work
153 properly.
154
155config ISCSI_IBFT
156 tristate "iSCSI Boot Firmware Table Attributes module"
Mike Christieb33a84a2010-04-12 18:06:18 +0000157 select ISCSI_BOOT_SYSFS
Randy Dunlap3e0f6862010-10-13 18:07:16 -0700158 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700159 default n
160 help
161 This option enables support for detection and exposing of iSCSI
162 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
163 detect iSCSI boot parameters dynamically during system boot, say Y.
164 Otherwise, say N.
165
Eric Anholt4e3d6062015-02-26 10:08:06 +0000166config RASPBERRYPI_FIRMWARE
167 tristate "Raspberry Pi Firmware Driver"
168 depends on BCM2835_MBOX
169 help
170 This option enables support for communicating with the firmware on the
171 Raspberry Pi.
172
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500173config FW_CFG_SYSFS
174 tristate "QEMU fw_cfg device support in sysfs"
175 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
Arnd Bergmann28c09ec2016-02-11 15:23:51 +0100176 depends on HAS_IOPORT_MAP
Gabriel Somlo75f3e8e2016-01-28 09:23:11 -0500177 default n
178 help
179 Say Y or M here to enable the exporting of the QEMU firmware
180 configuration (fw_cfg) file entries via sysfs. Entries are
181 found under /sys/firmware/fw_cfg when this option is enabled
182 and loaded.
183
184config FW_CFG_SYSFS_CMDLINE
185 bool "QEMU fw_cfg device parameter parsing"
186 depends on FW_CFG_SYSFS
187 help
188 Allow the qemu_fw_cfg device to be initialized via the kernel
189 command line or using a module parameter.
190 WARNING: Using incorrect parameters (base address in particular)
191 may crash your system.
192
Kumar Gala916f7432015-02-26 15:49:09 -0600193config QCOM_SCM
194 bool
195 depends on ARM || ARM64
Bjorn Anderssondd4fe5b2016-06-17 10:40:43 -0700196 select RESET_CONTROLLER
Kumar Gala916f7432015-02-26 15:49:09 -0600197
Andy Gross50b956f2015-09-11 16:01:16 -0500198config QCOM_SCM_32
199 def_bool y
200 depends on QCOM_SCM && ARM
201
202config QCOM_SCM_64
203 def_bool y
204 depends on QCOM_SCM && ARM64
205
Jens Wiklander98dd64f2016-01-04 15:37:32 +0100206config HAVE_ARM_SMCCC
207 bool
208
Rafał Miłeckif6e734a2015-06-10 23:05:08 +0200209source "drivers/firmware/broadcom/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700210source "drivers/firmware/google/Kconfig"
Matt Fleming04851772013-02-08 15:48:51 +0000211source "drivers/firmware/efi/Kconfig"
Mike Waychison74c5b312011-04-29 17:39:19 -0700212
Linus Torvalds1da177e2005-04-16 15:20:36 -0700213endmenu