Kconfig 8.5 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3 4 5 6 7
#
# For a description of the syntax of this configuration file,
# see Documentation/kbuild/kconfig-language.txt.
#

menu "Firmware Drivers"

8 9 10
config ARM_PSCI_FW
	bool

K
Kevin Brodsky 已提交
11 12 13 14 15 16 17 18 19 20 21
config ARM_PSCI_CHECKER
	bool "ARM PSCI checker"
	depends on ARM_PSCI_FW && HOTPLUG_CPU && !TORTURE_TEST
	help
	  Run the PSCI checker during startup. This checks that hotplug and
	  suspend operations work correctly when using PSCI.

	  The torture tests may interfere with the PSCI checker by turning CPUs
	  on and off through hotplug, so for now torture tests and PSCI checker
	  are mutually exclusive.

22 23
config ARM_SCPI_PROTOCOL
	tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
24
	depends on ARM || ARM64 || COMPILE_TEST
25
	depends on MAILBOX
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41
	help
	  System Control and Power Interface (SCPI) Message Protocol is
	  defined for the purpose of communication between the Application
	  Cores(AP) and the System Control Processor(SCP). The MHU peripheral
	  provides a mechanism for inter-processor communication between SCP
	  and AP.

	  SCP controls most of the power managament on the Application
	  Processors. It offers control and management of: the core/cluster
	  power states, various power domain DVFS including the core/cluster,
	  certain system clocks configuration, thermal sensors and many
	  others.

	  This protocol library provides interface for all the client drivers
	  making use of the features offered by the SCP.

42 43
config ARM_SCPI_POWER_DOMAIN
	tristate "SCPI power domain driver"
44
	depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
45 46 47 48 49 50
	default y
	select PM_GENERIC_DOMAINS if PM
	help
	  This enables support for the SCPI power domains which can be
	  enabled or disabled via the SCP firmware

L
Linus Torvalds 已提交
51
config EDD
52
	tristate "BIOS Enhanced Disk Drive calls determine boot disk"
M
Mike Frysinger 已提交
53
	depends on X86
L
Linus Torvalds 已提交
54 55 56 57 58 59 60 61 62
	help
	  Say Y or M here if you want to enable BIOS Enhanced Disk Drive
	  Services real mode BIOS calls to determine which disk
	  BIOS tries boot from.  This information is then exported via sysfs.

	  This option is experimental and is known to fail to boot on some
          obscure configurations. Most disk controller BIOS vendors do
          not yet implement this feature.

63 64 65 66 67 68 69 70 71
config EDD_OFF
	bool "Sets default behavior for EDD detection to off"
	depends on EDD
	default n
	help
	  Say Y if you want EDD disabled by default, even though it is compiled into the
	  kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
	  using the kernel parameter 'edd={on|skipmbr|off}'.

B
Bernhard Walle 已提交
72
config FIRMWARE_MEMMAP
73
    bool "Add firmware-provided memory map to sysfs" if EXPERT
M
Mike Frysinger 已提交
74
    default X86
B
Bernhard Walle 已提交
75 76 77 78 79 80 81
    help
      Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
      That memory map is used for example by kexec to set up parameter area
      for the next kernel, but can also be used for debugging purposes.

      See also Documentation/ABI/testing/sysfs-firmware-memmap.

L
Linus Torvalds 已提交
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102
config EFI_PCDP
	bool "Console device selection via EFI PCDP or HCDP table"
	depends on ACPI && EFI && IA64
	default y if IA64
	help
	  If your firmware supplies the PCDP table, and you want to
	  automatically use the primary console device it describes
	  as the Linux console, say Y here.

	  If your firmware supplies the HCDP table, and you want to
	  use the first serial port it describes as the Linux console,
	  say Y here.  If your EFI ConOut path contains only a UART
	  device, it will become the console automatically.  Otherwise,
	  you must specify the "console=hcdp" kernel boot argument.

	  Neither the PCDP nor the HCDP affects naming of serial devices,
	  so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
	  on how the driver discovers devices.

	  You must also enable the appropriate drivers (serial, VGA, etc.)

103 104
	  See DIG64_HCDPv20_042804.pdf available from
	  <http://www.dig64.org/specifications/> 
L
Linus Torvalds 已提交
105

106 107
config DELL_RBU
	tristate "BIOS update support for DELL systems via sysfs"
108
	depends on X86
109
	select FW_LOADER
110
	select FW_LOADER_USER_HELPER
111 112 113
	help
	 Say m if you want to have the option of updating the BIOS for your
	 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
M
Matt LaPlante 已提交
114
	 supporting application to communicate with the BIOS regarding the new
115 116
	 image for the image update to take effect.
	 See <file:Documentation/dell_rbu.txt> for more details on the driver.
117 118 119

config DCDBAS
	tristate "Dell Systems Management Base Driver"
B
Brian Gerst 已提交
120
	depends on X86
121 122 123 124 125 126 127 128 129 130 131 132 133
	help
	  The Dell Systems Management Base Driver provides a sysfs interface
	  for systems management software to perform System Management
	  Interrupts (SMIs) and Host Control Actions (system power cycle or
	  power off after OS shutdown) on certain Dell systems.

	  See <file:Documentation/dcdbas.txt> for more details on the driver
	  and the Dell systems on which Dell systems management software makes
	  use of this driver.

	  Say Y or M here to enable the driver for use by Dell systems
	  management software such as Dell OpenManage.

134 135 136 137 138 139 140 141 142
config DMIID
    bool "Export DMI identification via sysfs to userspace"
    depends on DMI
    default y
	help
	  Say Y here if you want to query SMBIOS/DMI system identification
	  information from userspace through /sys/class/dmi/id/ or if you want
	  DMI-based module auto-loading.

143 144 145 146 147 148 149 150 151 152 153
config DMI_SYSFS
	tristate "DMI table support in sysfs"
	depends on SYSFS && DMI
	default n
	help
	  Say Y or M here to enable the exporting of the raw DMI table
	  data via sysfs.  This is useful for consuming the data without
	  requiring any access to /dev/mem at all.  Tables are found
	  under /sys/firmware/dmi when this option is enabled and
	  loaded.

154 155 156
config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
	bool

157 158
config ISCSI_IBFT_FIND
	bool "iSCSI Boot Firmware Table Attributes"
159
	depends on X86 && ACPI
160 161 162 163 164 165 166 167 168
	default n
	help
	  This option enables the kernel to find the region of memory
	  in which the ISCSI Boot Firmware Table (iBFT) resides. This
	  is necessary for iSCSI Boot Firmware Table Attributes module to work
	  properly.

config ISCSI_IBFT
	tristate "iSCSI Boot Firmware Table Attributes module"
169
	select ISCSI_BOOT_SYSFS
R
Randy Dunlap 已提交
170
	depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
171 172 173 174 175 176 177
	default	n
	help
	  This option enables support for detection and exposing of iSCSI
	  Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
	  detect iSCSI boot parameters dynamically during system boot, say Y.
	  Otherwise, say N.

178 179 180 181 182 183 184
config RASPBERRYPI_FIRMWARE
	tristate "Raspberry Pi Firmware Driver"
	depends on BCM2835_MBOX
	help
	  This option enables support for communicating with the firmware on the
	  Raspberry Pi.

185 186 187
config FW_CFG_SYSFS
	tristate "QEMU fw_cfg device support in sysfs"
	depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
188
	depends on HAS_IOPORT_MAP
189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204
	default n
	help
	  Say Y or M here to enable the exporting of the QEMU firmware
	  configuration (fw_cfg) file entries via sysfs. Entries are
	  found under /sys/firmware/fw_cfg when this option is enabled
	  and loaded.

config FW_CFG_SYSFS_CMDLINE
	bool "QEMU fw_cfg device parameter parsing"
	depends on FW_CFG_SYSFS
	help
	  Allow the qemu_fw_cfg device to be initialized via the kernel
	  command line or using a module parameter.
	  WARNING: Using incorrect parameters (base address in particular)
	  may crash your system.

205 206 207
config QCOM_SCM
	bool
	depends on ARM || ARM64
208
	select RESET_CONTROLLER
209

210 211 212 213 214 215 216 217
config QCOM_SCM_32
	def_bool y
	depends on QCOM_SCM && ARM

config QCOM_SCM_64
	def_bool y
	depends on QCOM_SCM && ARM64

218 219 220 221 222 223 224 225 226 227 228
config QCOM_SCM_DOWNLOAD_MODE_DEFAULT
	bool "Qualcomm download mode enabled by default"
	depends on QCOM_SCM
	help
	  A device with "download mode" enabled will upon an unexpected
	  warm-restart enter a special debug mode that allows the user to
	  "download" memory content over USB for offline postmortem analysis.
	  The feature can be enabled/disabled on the kernel command line.

	  Say Y here to enable "download mode" by default.

229 230 231 232 233 234 235 236 237 238 239 240 241 242 243
config TI_SCI_PROTOCOL
	tristate "TI System Control Interface (TISCI) Message Protocol"
	depends on TI_MESSAGE_MANAGER
	help
	  TI System Control Interface (TISCI) Message Protocol is used to manage
	  compute systems such as ARM, DSP etc with the system controller in
	  complex System on Chip(SoC) such as those found on certain keystone
	  generation SoC from TI.

	  System controller provides various facilities including power
	  management function support.

	  This protocol library is used by client drivers to use the features
	  provided by the system controller.

244 245 246
config HAVE_ARM_SMCCC
	bool

247
source "drivers/firmware/broadcom/Kconfig"
M
Mike Waychison 已提交
248
source "drivers/firmware/google/Kconfig"
249
source "drivers/firmware/efi/Kconfig"
250
source "drivers/firmware/meson/Kconfig"
T
Thierry Reding 已提交
251
source "drivers/firmware/tegra/Kconfig"
M
Mike Waychison 已提交
252

L
Linus Torvalds 已提交
253
endmenu