0001 # SPDX-License-Identifier: GPL-2.0-only
0002 #
0003 # For a description of the syntax of this configuration file,
0004 # see Documentation/kbuild/kconfig-language.rst.
0005 #
0006
0007 menu "Firmware Drivers"
0008
0009 source "drivers/firmware/arm_scmi/Kconfig"
0010
0011 config ARM_SCPI_PROTOCOL
0012 tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
0013 depends on ARM || ARM64 || COMPILE_TEST
0014 depends on MAILBOX
0015 help
0016 System Control and Power Interface (SCPI) Message Protocol is
0017 defined for the purpose of communication between the Application
0018 Cores(AP) and the System Control Processor(SCP). The MHU peripheral
0019 provides a mechanism for inter-processor communication between SCP
0020 and AP.
0021
0022 SCP controls most of the power management on the Application
0023 Processors. It offers control and management of: the core/cluster
0024 power states, various power domain DVFS including the core/cluster,
0025 certain system clocks configuration, thermal sensors and many
0026 others.
0027
0028 This protocol library provides interface for all the client drivers
0029 making use of the features offered by the SCP.
0030
0031 config ARM_SCPI_POWER_DOMAIN
0032 tristate "SCPI power domain driver"
0033 depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
0034 default y
0035 select PM_GENERIC_DOMAINS if PM
0036 help
0037 This enables support for the SCPI power domains which can be
0038 enabled or disabled via the SCP firmware
0039
0040 config ARM_SDE_INTERFACE
0041 bool "ARM Software Delegated Exception Interface (SDEI)"
0042 depends on ARM64
0043 depends on ACPI_APEI_GHES
0044 help
0045 The Software Delegated Exception Interface (SDEI) is an ARM
0046 standard for registering callbacks from the platform firmware
0047 into the OS. This is typically used to implement RAS notifications.
0048
0049 config EDD
0050 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
0051 depends on X86
0052 help
0053 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
0054 Services real mode BIOS calls to determine which disk
0055 BIOS tries boot from. This information is then exported via sysfs.
0056
0057 This option is experimental and is known to fail to boot on some
0058 obscure configurations. Most disk controller BIOS vendors do
0059 not yet implement this feature.
0060
0061 config EDD_OFF
0062 bool "Sets default behavior for EDD detection to off"
0063 depends on EDD
0064 default n
0065 help
0066 Say Y if you want EDD disabled by default, even though it is compiled into the
0067 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
0068 using the kernel parameter 'edd={on|skipmbr|off}'.
0069
0070 config FIRMWARE_MEMMAP
0071 bool "Add firmware-provided memory map to sysfs" if EXPERT
0072 default X86
0073 help
0074 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
0075 That memory map is used for example by kexec to set up parameter area
0076 for the next kernel, but can also be used for debugging purposes.
0077
0078 See also Documentation/ABI/testing/sysfs-firmware-memmap.
0079
0080 config EFI_PCDP
0081 bool "Console device selection via EFI PCDP or HCDP table"
0082 depends on ACPI && EFI && IA64
0083 default y if IA64
0084 help
0085 If your firmware supplies the PCDP table, and you want to
0086 automatically use the primary console device it describes
0087 as the Linux console, say Y here.
0088
0089 If your firmware supplies the HCDP table, and you want to
0090 use the first serial port it describes as the Linux console,
0091 say Y here. If your EFI ConOut path contains only a UART
0092 device, it will become the console automatically. Otherwise,
0093 you must specify the "console=hcdp" kernel boot argument.
0094
0095 Neither the PCDP nor the HCDP affects naming of serial devices,
0096 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
0097 on how the driver discovers devices.
0098
0099 You must also enable the appropriate drivers (serial, VGA, etc.)
0100
0101 See DIG64_HCDPv20_042804.pdf available from
0102 <http://www.dig64.org/specifications/>
0103
0104 config DMIID
0105 bool "Export DMI identification via sysfs to userspace"
0106 depends on DMI
0107 default y
0108 help
0109 Say Y here if you want to query SMBIOS/DMI system identification
0110 information from userspace through /sys/class/dmi/id/ or if you want
0111 DMI-based module auto-loading.
0112
0113 config DMI_SYSFS
0114 tristate "DMI table support in sysfs"
0115 depends on SYSFS && DMI
0116 default n
0117 help
0118 Say Y or M here to enable the exporting of the raw DMI table
0119 data via sysfs. This is useful for consuming the data without
0120 requiring any access to /dev/mem at all. Tables are found
0121 under /sys/firmware/dmi when this option is enabled and
0122 loaded.
0123
0124 config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
0125 bool
0126
0127 config ISCSI_IBFT_FIND
0128 bool "iSCSI Boot Firmware Table Attributes"
0129 depends on X86 && ISCSI_IBFT
0130 default n
0131 help
0132 This option enables the kernel to find the region of memory
0133 in which the ISCSI Boot Firmware Table (iBFT) resides. This
0134 is necessary for iSCSI Boot Firmware Table Attributes module to work
0135 properly.
0136
0137 config ISCSI_IBFT
0138 tristate "iSCSI Boot Firmware Table Attributes module"
0139 select ISCSI_BOOT_SYSFS
0140 select ISCSI_IBFT_FIND if X86
0141 depends on ACPI && SCSI && SCSI_LOWLEVEL
0142 default n
0143 help
0144 This option enables support for detection and exposing of iSCSI
0145 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
0146 detect iSCSI boot parameters dynamically during system boot, say Y.
0147 Otherwise, say N.
0148
0149 config RASPBERRYPI_FIRMWARE
0150 tristate "Raspberry Pi Firmware Driver"
0151 depends on BCM2835_MBOX
0152 help
0153 This option enables support for communicating with the firmware on the
0154 Raspberry Pi.
0155
0156 config FW_CFG_SYSFS
0157 tristate "QEMU fw_cfg device support in sysfs"
0158 depends on SYSFS && (ARM || ARM64 || PARISC || PPC_PMAC || SPARC || X86)
0159 depends on HAS_IOPORT_MAP
0160 default n
0161 help
0162 Say Y or M here to enable the exporting of the QEMU firmware
0163 configuration (fw_cfg) file entries via sysfs. Entries are
0164 found under /sys/firmware/fw_cfg when this option is enabled
0165 and loaded.
0166
0167 config FW_CFG_SYSFS_CMDLINE
0168 bool "QEMU fw_cfg device parameter parsing"
0169 depends on FW_CFG_SYSFS
0170 help
0171 Allow the qemu_fw_cfg device to be initialized via the kernel
0172 command line or using a module parameter.
0173 WARNING: Using incorrect parameters (base address in particular)
0174 may crash your system.
0175
0176 config INTEL_STRATIX10_SERVICE
0177 tristate "Intel Stratix10 Service Layer"
0178 depends on ARCH_INTEL_SOCFPGA && ARM64 && HAVE_ARM_SMCCC
0179 default n
0180 help
0181 Intel Stratix10 service layer runs at privileged exception level,
0182 interfaces with the service providers (FPGA manager is one of them)
0183 and manages secure monitor call to communicate with secure monitor
0184 software at secure monitor exception level.
0185
0186 Say Y here if you want Stratix10 service layer support.
0187
0188 config INTEL_STRATIX10_RSU
0189 tristate "Intel Stratix10 Remote System Update"
0190 depends on INTEL_STRATIX10_SERVICE
0191 help
0192 The Intel Remote System Update (RSU) driver exposes interfaces
0193 access through the Intel Service Layer to user space via sysfs
0194 device attribute nodes. The RSU interfaces report/control some of
0195 the optional RSU features of the Stratix 10 SoC FPGA.
0196
0197 The RSU provides a way for customers to update the boot
0198 configuration of a Stratix 10 SoC device with significantly reduced
0199 risk of corrupting the bitstream storage and bricking the system.
0200
0201 Enable RSU support if you are using an Intel SoC FPGA with the RSU
0202 feature enabled and you want Linux user space control.
0203
0204 Say Y here if you want Intel RSU support.
0205
0206 config MTK_ADSP_IPC
0207 tristate "MTK ADSP IPC Protocol driver"
0208 depends on MTK_ADSP_MBOX
0209 help
0210 Say yes here to add support for the MediaTek ADSP IPC
0211 between host AP (Linux) and the firmware running on ADSP.
0212 ADSP exists on some mtk processors.
0213 Client might use shared memory to exchange information with ADSP.
0214
0215 config QCOM_SCM
0216 tristate
0217
0218 config QCOM_SCM_DOWNLOAD_MODE_DEFAULT
0219 bool "Qualcomm download mode enabled by default"
0220 depends on QCOM_SCM
0221 help
0222 A device with "download mode" enabled will upon an unexpected
0223 warm-restart enter a special debug mode that allows the user to
0224 "download" memory content over USB for offline postmortem analysis.
0225 The feature can be enabled/disabled on the kernel command line.
0226
0227 Say Y here to enable "download mode" by default.
0228
0229 config SYSFB
0230 bool
0231 select BOOT_VESA_SUPPORT
0232
0233 config SYSFB_SIMPLEFB
0234 bool "Mark VGA/VBE/EFI FB as generic system framebuffer"
0235 depends on X86 || EFI
0236 select SYSFB
0237 help
0238 Firmwares often provide initial graphics framebuffers so the BIOS,
0239 bootloader or kernel can show basic video-output during boot for
0240 user-guidance and debugging. Historically, x86 used the VESA BIOS
0241 Extensions and EFI-framebuffers for this, which are mostly limited
0242 to x86 BIOS or EFI systems.
0243 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
0244 framebuffers so the new generic system-framebuffer drivers can be
0245 used instead. If the framebuffer is not compatible with the generic
0246 modes, it is advertised as fallback platform framebuffer so legacy
0247 drivers like efifb, vesafb and uvesafb can pick it up.
0248 If this option is not selected, all system framebuffers are always
0249 marked as fallback platform framebuffers as usual.
0250
0251 Note: Legacy fbdev drivers, including vesafb, efifb, uvesafb, will
0252 not be able to pick up generic system framebuffers if this option
0253 is selected. You are highly encouraged to enable simplefb as
0254 replacement if you select this option. simplefb can correctly deal
0255 with generic system framebuffers. But you should still keep vesafb
0256 and others enabled as fallback if a system framebuffer is
0257 incompatible with simplefb.
0258
0259 If unsure, say Y.
0260
0261 config TI_SCI_PROTOCOL
0262 tristate "TI System Control Interface (TISCI) Message Protocol"
0263 depends on TI_MESSAGE_MANAGER
0264 help
0265 TI System Control Interface (TISCI) Message Protocol is used to manage
0266 compute systems such as ARM, DSP etc with the system controller in
0267 complex System on Chip(SoC) such as those found on certain keystone
0268 generation SoC from TI.
0269
0270 System controller provides various facilities including power
0271 management function support.
0272
0273 This protocol library is used by client drivers to use the features
0274 provided by the system controller.
0275
0276 config TRUSTED_FOUNDATIONS
0277 bool "Trusted Foundations secure monitor support"
0278 depends on ARM && CPU_V7
0279 help
0280 Some devices (including most early Tegra-based consumer devices on
0281 the market) are booted with the Trusted Foundations secure monitor
0282 active, requiring some core operations to be performed by the secure
0283 monitor instead of the kernel.
0284
0285 This option allows the kernel to invoke the secure monitor whenever
0286 required on devices using Trusted Foundations. See the functions and
0287 comments in linux/firmware/trusted_foundations.h or the device tree
0288 bindings for "tlm,trusted-foundations" for details on how to use it.
0289
0290 Choose N if you don't know what this is about.
0291
0292 config TURRIS_MOX_RWTM
0293 tristate "Turris Mox rWTM secure firmware driver"
0294 depends on ARCH_MVEBU || COMPILE_TEST
0295 depends on HAS_DMA && OF
0296 depends on MAILBOX
0297 select HW_RANDOM
0298 select ARMADA_37XX_RWTM_MBOX
0299 help
0300 This driver communicates with the firmware on the Cortex-M3 secure
0301 processor of the Turris Mox router. Enable if you are building for
0302 Turris Mox, and you will be able to read the device serial number and
0303 other manufacturing data and also utilize the Entropy Bit Generator
0304 for hardware random number generation.
0305
0306 source "drivers/firmware/arm_ffa/Kconfig"
0307 source "drivers/firmware/broadcom/Kconfig"
0308 source "drivers/firmware/cirrus/Kconfig"
0309 source "drivers/firmware/google/Kconfig"
0310 source "drivers/firmware/efi/Kconfig"
0311 source "drivers/firmware/imx/Kconfig"
0312 source "drivers/firmware/meson/Kconfig"
0313 source "drivers/firmware/psci/Kconfig"
0314 source "drivers/firmware/smccc/Kconfig"
0315 source "drivers/firmware/tegra/Kconfig"
0316 source "drivers/firmware/xilinx/Kconfig"
0317
0318 endmenu
