Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # For a description of the syntax of this configuration file, |
| 3 | # see Documentation/kbuild/kconfig-language.txt. |
| 4 | # |
| 5 | |
| 6 | menu "Firmware Drivers" |
| 7 | |
Mark Rutland | bff6079 | 2015-07-31 15:46:16 +0100 | [diff] [blame] | 8 | config ARM_PSCI_FW |
| 9 | bool |
| 10 | |
Kevin Brodsky | ea8b1c4 | 2016-11-08 17:55:46 +0000 | [diff] [blame] | 11 | config 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 Holla | 8cb7cf5 | 2015-03-30 10:59:52 +0100 | [diff] [blame] | 22 | config ARM_SCPI_PROTOCOL |
| 23 | tristate "ARM System Control and Power Interface (SCPI) Message Protocol" |
Jean Delvare | 92f3e6e | 2017-01-30 09:52:01 +0100 | [diff] [blame] | 24 | depends on ARM || ARM64 || COMPILE_TEST |
Sudeep Holla | 8f1498c | 2016-06-05 18:23:21 +0100 | [diff] [blame] | 25 | depends on MAILBOX |
Sudeep Holla | 8cb7cf5 | 2015-03-30 10:59:52 +0100 | [diff] [blame] | 26 | 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 Holla | 8bec433 | 2016-06-02 16:34:03 +0100 | [diff] [blame] | 42 | config ARM_SCPI_POWER_DOMAIN |
| 43 | tristate "SCPI power domain driver" |
Arnd Bergmann | e517dfe | 2016-07-06 14:49:46 +0200 | [diff] [blame] | 44 | depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF) |
Sudeep Holla | 8bec433 | 2016-06-02 16:34:03 +0100 | [diff] [blame] | 45 | default y |
| 46 | select PM_GENERIC_DOMAINS if PM |
Sudeep Holla | 8bec433 | 2016-06-02 16:34:03 +0100 | [diff] [blame] | 47 | help |
| 48 | This enables support for the SCPI power domains which can be |
| 49 | enabled or disabled via the SCP firmware |
| 50 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 51 | config EDD |
Chris Wedgwood | 5d18639 | 2006-06-25 05:47:46 -0700 | [diff] [blame] | 52 | tristate "BIOS Enhanced Disk Drive calls determine boot disk" |
Mike Frysinger | 9b6e3e4 | 2009-12-14 18:01:16 -0800 | [diff] [blame] | 53 | depends on X86 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 54 | 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 Gardner | 8c4dd60 | 2008-04-29 01:02:45 -0700 | [diff] [blame] | 63 | config 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 Walle | 69ac9cd | 2008-06-27 13:12:54 +0200 | [diff] [blame] | 72 | config FIRMWARE_MEMMAP |
David Rientjes | 6a108a1 | 2011-01-20 14:44:16 -0800 | [diff] [blame] | 73 | bool "Add firmware-provided memory map to sysfs" if EXPERT |
Mike Frysinger | 9b6e3e4 | 2009-12-14 18:01:16 -0800 | [diff] [blame] | 74 | default X86 |
Bernhard Walle | 69ac9cd | 2008-06-27 13:12:54 +0200 | [diff] [blame] | 75 | 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 Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 82 | config 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. Mattock | 631dd1a | 2010-10-18 11:03:14 +0200 | [diff] [blame] | 103 | See DIG64_HCDPv20_042804.pdf available from |
| 104 | <http://www.dig64.org/specifications/> |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 105 | |
Abhay Salunke | 6c54c28 | 2005-09-06 15:17:14 -0700 | [diff] [blame] | 106 | config DELL_RBU |
| 107 | tristate "BIOS update support for DELL systems via sysfs" |
Dave Jones | 6c52f13 | 2005-11-21 21:32:30 -0800 | [diff] [blame] | 108 | depends on X86 |
Abhay Salunke | 6c54c28 | 2005-09-06 15:17:14 -0700 | [diff] [blame] | 109 | select FW_LOADER |
Takashi Iwai | d05c39e | 2013-05-22 18:28:37 +0200 | [diff] [blame] | 110 | select FW_LOADER_USER_HELPER |
Abhay Salunke | 6c54c28 | 2005-09-06 15:17:14 -0700 | [diff] [blame] | 111 | 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 LaPlante | 0950960 | 2006-10-03 22:31:37 +0200 | [diff] [blame] | 114 | supporting application to communicate with the BIOS regarding the new |
Abhay Salunke | 6c54c28 | 2005-09-06 15:17:14 -0700 | [diff] [blame] | 115 | image for the image update to take effect. |
| 116 | See <file:Documentation/dell_rbu.txt> for more details on the driver. |
Doug Warzecha | 90563ec | 2005-09-06 15:17:15 -0700 | [diff] [blame] | 117 | |
| 118 | config DCDBAS |
| 119 | tristate "Dell Systems Management Base Driver" |
Brian Gerst | 0d078f6 | 2005-10-30 14:59:20 -0800 | [diff] [blame] | 120 | depends on X86 |
Doug Warzecha | 90563ec | 2005-09-06 15:17:15 -0700 | [diff] [blame] | 121 | 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 Poettering | 4f5c791 | 2007-05-08 22:07:02 +0200 | [diff] [blame] | 134 | config 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 Waychison | 948af1f | 2011-02-22 17:53:21 -0800 | [diff] [blame] | 143 | config 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 Biesheuvel | cf07440 | 2014-01-23 15:54:39 -0800 | [diff] [blame] | 154 | config DMI_SCAN_MACHINE_NON_EFI_FALLBACK |
| 155 | bool |
| 156 | |
Konrad Rzeszutek | 138fe4e | 2008-04-09 19:50:41 -0700 | [diff] [blame] | 157 | config ISCSI_IBFT_FIND |
| 158 | bool "iSCSI Boot Firmware Table Attributes" |
Thomas Tai | a3e7eb5 | 2019-07-18 18:37:34 +0000 | [diff] [blame] | 159 | depends on X86 && ISCSI_IBFT |
Konrad Rzeszutek | 138fe4e | 2008-04-09 19:50:41 -0700 | [diff] [blame] | 160 | 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 | |
| 167 | config ISCSI_IBFT |
| 168 | tristate "iSCSI Boot Firmware Table Attributes module" |
Mike Christie | b33a84a | 2010-04-12 18:06:18 +0000 | [diff] [blame] | 169 | select ISCSI_BOOT_SYSFS |
Thomas Tai | a3e7eb5 | 2019-07-18 18:37:34 +0000 | [diff] [blame] | 170 | select ISCSI_IBFT_FIND if X86 |
| 171 | depends on ACPI && SCSI && SCSI_LOWLEVEL |
Konrad Rzeszutek | 138fe4e | 2008-04-09 19:50:41 -0700 | [diff] [blame] | 172 | 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 Anholt | 4e3d606 | 2015-02-26 10:08:06 +0000 | [diff] [blame] | 179 | config 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 Somlo | 75f3e8e | 2016-01-28 09:23:11 -0500 | [diff] [blame] | 186 | config FW_CFG_SYSFS |
| 187 | tristate "QEMU fw_cfg device support in sysfs" |
| 188 | depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86) |
Arnd Bergmann | 28c09ec | 2016-02-11 15:23:51 +0100 | [diff] [blame] | 189 | depends on HAS_IOPORT_MAP |
Gabriel Somlo | 75f3e8e | 2016-01-28 09:23:11 -0500 | [diff] [blame] | 190 | 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 | |
| 197 | config 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 Gala | 916f743 | 2015-02-26 15:49:09 -0600 | [diff] [blame] | 206 | config QCOM_SCM |
| 207 | bool |
| 208 | depends on ARM || ARM64 |
He Ying | 089e8c1 | 2021-04-06 05:42:00 -0400 | [diff] [blame] | 209 | depends on HAVE_ARM_SMCCC |
Bjorn Andersson | dd4fe5b | 2016-06-17 10:40:43 -0700 | [diff] [blame] | 210 | select RESET_CONTROLLER |
Kumar Gala | 916f743 | 2015-02-26 15:49:09 -0600 | [diff] [blame] | 211 | |
Andy Gross | 50b956f | 2015-09-11 16:01:16 -0500 | [diff] [blame] | 212 | config QCOM_SCM_32 |
| 213 | def_bool y |
| 214 | depends on QCOM_SCM && ARM |
| 215 | |
| 216 | config QCOM_SCM_64 |
| 217 | def_bool y |
| 218 | depends on QCOM_SCM && ARM64 |
| 219 | |
Nishanth Menon | aa27678 | 2016-10-18 18:08:34 -0500 | [diff] [blame] | 220 | config 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 Wiklander | 98dd64f | 2016-01-04 15:37:32 +0100 | [diff] [blame] | 235 | config HAVE_ARM_SMCCC |
| 236 | bool |
| 237 | |
Rafał Miłecki | f6e734a | 2015-06-10 23:05:08 +0200 | [diff] [blame] | 238 | source "drivers/firmware/broadcom/Kconfig" |
Mike Waychison | 74c5b31 | 2011-04-29 17:39:19 -0700 | [diff] [blame] | 239 | source "drivers/firmware/google/Kconfig" |
Matt Fleming | 0485177 | 2013-02-08 15:48:51 +0000 | [diff] [blame] | 240 | source "drivers/firmware/efi/Kconfig" |
Carlo Caione | 2c4ddb2 | 2016-08-27 15:43:43 +0200 | [diff] [blame] | 241 | source "drivers/firmware/meson/Kconfig" |
Thierry Reding | ca791d7 | 2016-08-19 19:05:04 +0200 | [diff] [blame] | 242 | source "drivers/firmware/tegra/Kconfig" |
Mike Waychison | 74c5b31 | 2011-04-29 17:39:19 -0700 | [diff] [blame] | 243 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 244 | endmenu |