2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 menu "Firmware Drivers"
11 config ARM_SCPI_PROTOCOL
12 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
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
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
27 This protocol library provides interface for all the client drivers
28 making use of the features offered by the SCP.
30 config ARM_SCPI_POWER_DOMAIN
31 tristate "SCPI power domain driver"
32 depends on ARM_SCPI_PROTOCOL || COMPILE_TEST
34 select PM_GENERIC_DOMAINS if PM
35 select PM_GENERIC_DOMAINS_OF if PM
37 This enables support for the SCPI power domains which can be
38 enabled or disabled via the SCP firmware
41 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
44 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
45 Services real mode BIOS calls to determine which disk
46 BIOS tries boot from. This information is then exported via sysfs.
48 This option is experimental and is known to fail to boot on some
49 obscure configurations. Most disk controller BIOS vendors do
50 not yet implement this feature.
53 bool "Sets default behavior for EDD detection to off"
57 Say Y if you want EDD disabled by default, even though it is compiled into the
58 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
59 using the kernel parameter 'edd={on|skipmbr|off}'.
61 config FIRMWARE_MEMMAP
62 bool "Add firmware-provided memory map to sysfs" if EXPERT
65 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
66 That memory map is used for example by kexec to set up parameter area
67 for the next kernel, but can also be used for debugging purposes.
69 See also Documentation/ABI/testing/sysfs-firmware-memmap.
72 bool "Console device selection via EFI PCDP or HCDP table"
73 depends on ACPI && EFI && IA64
76 If your firmware supplies the PCDP table, and you want to
77 automatically use the primary console device it describes
78 as the Linux console, say Y here.
80 If your firmware supplies the HCDP table, and you want to
81 use the first serial port it describes as the Linux console,
82 say Y here. If your EFI ConOut path contains only a UART
83 device, it will become the console automatically. Otherwise,
84 you must specify the "console=hcdp" kernel boot argument.
86 Neither the PCDP nor the HCDP affects naming of serial devices,
87 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
88 on how the driver discovers devices.
90 You must also enable the appropriate drivers (serial, VGA, etc.)
92 See DIG64_HCDPv20_042804.pdf available from
93 <http://www.dig64.org/specifications/>
96 tristate "BIOS update support for DELL systems via sysfs"
99 select FW_LOADER_USER_HELPER
101 Say m if you want to have the option of updating the BIOS for your
102 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
103 supporting application to communicate with the BIOS regarding the new
104 image for the image update to take effect.
105 See <file:Documentation/dell_rbu.txt> for more details on the driver.
108 tristate "Dell Systems Management Base Driver"
111 The Dell Systems Management Base Driver provides a sysfs interface
112 for systems management software to perform System Management
113 Interrupts (SMIs) and Host Control Actions (system power cycle or
114 power off after OS shutdown) on certain Dell systems.
116 See <file:Documentation/dcdbas.txt> for more details on the driver
117 and the Dell systems on which Dell systems management software makes
120 Say Y or M here to enable the driver for use by Dell systems
121 management software such as Dell OpenManage.
124 bool "Export DMI identification via sysfs to userspace"
128 Say Y here if you want to query SMBIOS/DMI system identification
129 information from userspace through /sys/class/dmi/id/ or if you want
130 DMI-based module auto-loading.
133 tristate "DMI table support in sysfs"
134 depends on SYSFS && DMI
137 Say Y or M here to enable the exporting of the raw DMI table
138 data via sysfs. This is useful for consuming the data without
139 requiring any access to /dev/mem at all. Tables are found
140 under /sys/firmware/dmi when this option is enabled and
143 config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
146 config ISCSI_IBFT_FIND
147 bool "iSCSI Boot Firmware Table Attributes"
148 depends on X86 && ACPI
151 This option enables the kernel to find the region of memory
152 in which the ISCSI Boot Firmware Table (iBFT) resides. This
153 is necessary for iSCSI Boot Firmware Table Attributes module to work
157 tristate "iSCSI Boot Firmware Table Attributes module"
158 select ISCSI_BOOT_SYSFS
159 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
162 This option enables support for detection and exposing of iSCSI
163 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
164 detect iSCSI boot parameters dynamically during system boot, say Y.
167 config RASPBERRYPI_FIRMWARE
168 tristate "Raspberry Pi Firmware Driver"
169 depends on BCM2835_MBOX
171 This option enables support for communicating with the firmware on the
175 tristate "QEMU fw_cfg device support in sysfs"
176 depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
177 depends on HAS_IOPORT_MAP
180 Say Y or M here to enable the exporting of the QEMU firmware
181 configuration (fw_cfg) file entries via sysfs. Entries are
182 found under /sys/firmware/fw_cfg when this option is enabled
185 config FW_CFG_SYSFS_CMDLINE
186 bool "QEMU fw_cfg device parameter parsing"
187 depends on FW_CFG_SYSFS
189 Allow the qemu_fw_cfg device to be initialized via the kernel
190 command line or using a module parameter.
191 WARNING: Using incorrect parameters (base address in particular)
192 may crash your system.
196 depends on ARM || ARM64
197 select RESET_CONTROLLER
201 depends on QCOM_SCM && ARM
205 depends on QCOM_SCM && ARM64
207 config HAVE_ARM_SMCCC
210 source "drivers/firmware/broadcom/Kconfig"
211 source "drivers/firmware/google/Kconfig"
212 source "drivers/firmware/efi/Kconfig"