drivers/firmware/Kconfig

   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
   8 config ARM_PSCI_FW
   9         bool
  10
  11 config ARM_SCPI_PROTOCOL
  12         tristate "ARM System Control and Power Interface (SCPI) Message Protocol"
  13         depends on MAILBOX
  14         help
  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
  19           and AP.
  20
  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
  25           others.
  26
  27           This protocol library provides interface for all the client drivers
  28           making use of the features offered by the SCP.
  29
  30 config ARM_SCPI_POWER_DOMAIN
  31         tristate "SCPI power domain driver"
  32         depends on ARM_SCPI_PROTOCOL || (COMPILE_TEST && OF)
  33         default y
  34         select PM_GENERIC_DOMAINS if PM
  35         help
  36           This enables support for the SCPI power domains which can be
  37           enabled or disabled via the SCP firmware
  38
  39 config EDD
  40         tristate "BIOS Enhanced Disk Drive calls determine boot disk"
  41         depends on X86
  42         help
  43           Say Y or M here if you want to enable BIOS Enhanced Disk Drive
  44           Services real mode BIOS calls to determine which disk
  45           BIOS tries boot from.  This information is then exported via sysfs.
  46
  47           This option is experimental and is known to fail to boot on some
  48           obscure configurations. Most disk controller BIOS vendors do
  49           not yet implement this feature.
  50
  51 config EDD_OFF
  52         bool "Sets default behavior for EDD detection to off"
  53         depends on EDD
  54         default n
  55         help
  56           Say Y if you want EDD disabled by default, even though it is compiled into the
  57           kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
  58           using the kernel parameter 'edd={on|skipmbr|off}'.
  59
  60 config FIRMWARE_MEMMAP
  61     bool "Add firmware-provided memory map to sysfs" if EXPERT
  62     default X86
  63     help
  64       Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
  65       That memory map is used for example by kexec to set up parameter area
  66       for the next kernel, but can also be used for debugging purposes.
  67
  68       See also Documentation/ABI/testing/sysfs-firmware-memmap.
  69
  70 config EFI_PCDP
  71         bool "Console device selection via EFI PCDP or HCDP table"
  72         depends on ACPI && EFI && IA64
  73         default y if IA64
  74         help
  75           If your firmware supplies the PCDP table, and you want to
  76           automatically use the primary console device it describes
  77           as the Linux console, say Y here.
  78
  79           If your firmware supplies the HCDP table, and you want to
  80           use the first serial port it describes as the Linux console,
  81           say Y here.  If your EFI ConOut path contains only a UART
  82           device, it will become the console automatically.  Otherwise,
  83           you must specify the "console=hcdp" kernel boot argument.
  84
  85           Neither the PCDP nor the HCDP affects naming of serial devices,
  86           so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
  87           on how the driver discovers devices.
  88
  89           You must also enable the appropriate drivers (serial, VGA, etc.)
  90
  91           See DIG64_HCDPv20_042804.pdf available from
  92           <http://www.dig64.org/specifications/>
  93
  94 config DELL_RBU
  95         tristate "BIOS update support for DELL systems via sysfs"
  96         depends on X86
  97         select FW_LOADER
  98         select FW_LOADER_USER_HELPER
  99         help
 100          Say m if you want to have the option of updating the BIOS for your
 101          DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
 102          supporting application to communicate with the BIOS regarding the new
 103          image for the image update to take effect.
 104          See <file:Documentation/dell_rbu.txt> for more details on the driver.
 105
 106 config DCDBAS
 107         tristate "Dell Systems Management Base Driver"
 108         depends on X86
 109         help
 110           The Dell Systems Management Base Driver provides a sysfs interface
 111           for systems management software to perform System Management
 112           Interrupts (SMIs) and Host Control Actions (system power cycle or
 113           power off after OS shutdown) on certain Dell systems.
 114
 115           See <file:Documentation/dcdbas.txt> for more details on the driver
 116           and the Dell systems on which Dell systems management software makes
 117           use of this driver.
 118
 119           Say Y or M here to enable the driver for use by Dell systems
 120           management software such as Dell OpenManage.
 121
 122 config DMIID
 123     bool "Export DMI identification via sysfs to userspace"
 124     depends on DMI
 125     default y
 126         help
 127           Say Y here if you want to query SMBIOS/DMI system identification
 128           information from userspace through /sys/class/dmi/id/ or if you want
 129           DMI-based module auto-loading.
 130
 131 config DMI_SYSFS
 132         tristate "DMI table support in sysfs"
 133         depends on SYSFS && DMI
 134         default n
 135         help
 136           Say Y or M here to enable the exporting of the raw DMI table
 137           data via sysfs.  This is useful for consuming the data without
 138           requiring any access to /dev/mem at all.  Tables are found
 139           under /sys/firmware/dmi when this option is enabled and
 140           loaded.
 141
 142 config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
 143         bool
 144
 145 config ISCSI_IBFT_FIND
 146         bool "iSCSI Boot Firmware Table Attributes"
 147         depends on X86 && ACPI
 148         default n
 149         help
 150           This option enables the kernel to find the region of memory
 151           in which the ISCSI Boot Firmware Table (iBFT) resides. This
 152           is necessary for iSCSI Boot Firmware Table Attributes module to work
 153           properly.
 154
 155 config ISCSI_IBFT
 156         tristate "iSCSI Boot Firmware Table Attributes module"
 157         select ISCSI_BOOT_SYSFS
 158         depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
 159         default n
 160         help
 161           This option enables support for detection and exposing of iSCSI
 162           Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
 163           detect iSCSI boot parameters dynamically during system boot, say Y.
 164           Otherwise, say N.
 165
 166 config RASPBERRYPI_FIRMWARE
 167         tristate "Raspberry Pi Firmware Driver"
 168         depends on BCM2835_MBOX
 169         help
 170           This option enables support for communicating with the firmware on the
 171           Raspberry Pi.
 172
 173 config FW_CFG_SYSFS
 174         tristate "QEMU fw_cfg device support in sysfs"
 175         depends on SYSFS && (ARM || ARM64 || PPC_PMAC || SPARC || X86)
 176         depends on HAS_IOPORT_MAP
 177         default n
 178         help
 179           Say Y or M here to enable the exporting of the QEMU firmware
 180           configuration (fw_cfg) file entries via sysfs. Entries are
 181           found under /sys/firmware/fw_cfg when this option is enabled
 182           and loaded.
 183
 184 config FW_CFG_SYSFS_CMDLINE
 185         bool "QEMU fw_cfg device parameter parsing"
 186         depends on FW_CFG_SYSFS
 187         help
 188           Allow the qemu_fw_cfg device to be initialized via the kernel
 189           command line or using a module parameter.
 190           WARNING: Using incorrect parameters (base address in particular)
 191           may crash your system.
 192
 193 config QCOM_SCM
 194         bool
 195         depends on ARM || ARM64
 196         select RESET_CONTROLLER
 197
 198 config QCOM_SCM_32
 199         def_bool y
 200         depends on QCOM_SCM && ARM
 201
 202 config QCOM_SCM_64
 203         def_bool y
 204         depends on QCOM_SCM && ARM64
 205
 206 config HAVE_ARM_SMCCC
 207         bool
 208
 209 source "drivers/firmware/broadcom/Kconfig"
 210 source "drivers/firmware/google/Kconfig"
 211 source "drivers/firmware/efi/Kconfig"
 212
 213 endmenu