#
# For a description of the syntax of this configuration file,
# see Documentation/kbuild/kconfig-language.txt.
#
menu "Firmware Drivers"
config [31mCONFIG_ARM_PSCI_FW[0m
bool
config [31mCONFIG_ARM_PSCI_CHECKER[0m
bool "ARM PSCI checker"
depends on [31mCONFIG_ARM_PSCI_FW[0m && [31mCONFIG_HOTPLUG_CPU[0m && ![31mCONFIG_TORTURE_TEST[0m
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.
config [31mCONFIG_ARM_SCPI_PROTOCOL[0m
tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
depends on [31mCONFIG_MAILBOX[0m
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.
config [31mCONFIG_ARM_SCPI_POWER_DOMAIN[0m
tristate "SCPI power domain driver"
depends on [31mCONFIG_ARM_SCPI_PROTOCOL[0m || ([31mCONFIG_COMPILE_TEST[0m && [31mCONFIG_OF[0m)
default y
select [31mCONFIG_PM_GENERIC_DOMAINS[0m if [31mCONFIG_PM[0m
help
This enables support for the SCPI power domains which can be
enabled or disabled via the SCP firmware
config [31mCONFIG_EDD[0m
tristate "BIOS Enhanced Disk Drive calls determine boot disk"
depends on [31mCONFIG_X86[0m
help
Say Y or [31mCONFIG_M[0m 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.
config [31mCONFIG_EDD_OFF[0m
bool "Sets default behavior for EDD detection to off"
depends on [31mCONFIG_EDD[0m
default n
help
Say Y if you want [31mCONFIG_EDD[0m disabled by default, even though it is compiled into the
kernel. Say N if you want [31mCONFIG_EDD[0m enabled by default. [31mCONFIG_EDD[0m can be dynamically set
using the kernel parameter 'edd={on|skipmbr|off}'.
config [31mCONFIG_FIRMWARE_MEMMAP[0m
bool "Add firmware-provided memory map to sysfs" if [31mCONFIG_EXPERT[0m
default [31mCONFIG_X86[0m
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.
config [31mCONFIG_EFI_PCDP[0m
bool "Console device selection via EFI PCDP or HCDP table"
depends on [31mCONFIG_ACPI[0m && [31mCONFIG_EFI[0m && [31mCONFIG_IA64[0m
default y if [31mCONFIG_IA64[0m
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 [31mCONFIG_EFI[0m 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.)
See DIG64_HCDPv20_042804.pdf available from
<http://www.dig64.org/specifications/>
config [31mCONFIG_DELL_RBU[0m
tristate "BIOS update support for DELL systems via sysfs"
depends on [31mCONFIG_X86[0m
select [31mCONFIG_FW_LOADER[0m
select [31mCONFIG_FW_LOADER_USER_HELPER[0m
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)
supporting application to communicate with the BIOS regarding the new
image for the image update to take effect.
See <file:Documentation/dell_rbu.txt> for more details on the driver.
config [31mCONFIG_DCDBAS[0m
tristate "Dell Systems Management Base Driver"
depends on [31mCONFIG_X86[0m
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 [31mCONFIG_M[0m here to enable the driver for use by Dell systems
management software such as Dell OpenManage.
config [31mCONFIG_DMIID[0m
bool "Export DMI identification via sysfs to userspace"
depends on [31mCONFIG_DMI[0m
default y
help
Say Y here if you want to query SMBIOS/[31mCONFIG_DMI[0m system identification
information from userspace through /sys/class/dmi/id/ or if you want
[31mCONFIG_DMI[0m-based module auto-loading.
config [31mCONFIG_DMI_SYSFS[0m
tristate "DMI table support in sysfs"
depends on [31mCONFIG_SYSFS[0m && [31mCONFIG_DMI[0m
default n
help
Say Y or [31mCONFIG_M[0m here to enable the exporting of the raw [31mCONFIG_DMI[0m 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.
config [31mCONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK[0m
bool
config [31mCONFIG_ISCSI_IBFT_FIND[0m
bool "iSCSI Boot Firmware Table Attributes"
depends on [31mCONFIG_X86[0m && [31mCONFIG_ACPI[0m
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 [31mCONFIG_ISCSI_IBFT[0m
tristate "iSCSI Boot Firmware Table Attributes module"
select [31mCONFIG_ISCSI_BOOT_SYSFS[0m
depends on [31mCONFIG_ISCSI_IBFT_FIND[0m && [31mCONFIG_SCSI[0m && [31mCONFIG_SCSI_LOWLEVEL[0m
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.
config [31mCONFIG_RASPBERRYPI_FIRMWARE[0m
tristate "Raspberry Pi Firmware Driver"
depends on [31mCONFIG_BCM2835_MBOX[0m
help
This option enables support for communicating with the firmware on the
Raspberry Pi.
config [31mCONFIG_FW_CFG_SYSFS[0m
tristate "QEMU fw_cfg device support in sysfs"
depends on [31mCONFIG_SYSFS[0m && ([31mCONFIG_ARM[0m || [31mCONFIG_ARM64[0m || [31mCONFIG_PPC_PMAC[0m || [31mCONFIG_SPARC[0m || [31mCONFIG_X86[0m)
depends on [31mCONFIG_HAS_IOPORT_MAP[0m
default n
help
Say Y or [31mCONFIG_M[0m 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 [31mCONFIG_FW_CFG_SYSFS_CMDLINE[0m
bool "QEMU fw_cfg device parameter parsing"
depends on [31mCONFIG_FW_CFG_SYSFS[0m
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.
config [31mCONFIG_QCOM_SCM[0m
bool
depends on [31mCONFIG_ARM[0m || [31mCONFIG_ARM64[0m
select [31mCONFIG_RESET_CONTROLLER[0m
config [31mCONFIG_QCOM_SCM_32[0m
def_bool y
depends on [31mCONFIG_QCOM_SCM[0m && [31mCONFIG_ARM[0m
config [31mCONFIG_QCOM_SCM_64[0m
def_bool y
depends on [31mCONFIG_QCOM_SCM[0m && [31mCONFIG_ARM64[0m
config [31mCONFIG_TI_SCI_PROTOCOL[0m
tristate "TI System Control Interface (TISCI) Message Protocol"
depends on [31mCONFIG_TI_MESSAGE_MANAGER[0m
help
TI System Control Interface (TISCI) Message Protocol is used to manage
compute systems such as [31mCONFIG_ARM[0m, 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.
config [31mCONFIG_HAVE_ARM_SMCCC[0m
bool
source "drivers/firmware/broadcom/Kconfig"
source "drivers/firmware/google/Kconfig"
source "drivers/firmware/efi/Kconfig"
source "drivers/firmware/meson/Kconfig"
source "drivers/firmware/tegra/Kconfig"
endmenu