1# 2# For a description of the syntax of this configuration file, 3# see Documentation/kbuild/kconfig-language.txt. 4# 5 6menu "Firmware Drivers" 7 8config ARM_PSCI_FW 9 bool 10 11config EDD 12 tristate "BIOS Enhanced Disk Drive calls determine boot disk" 13 depends on X86 14 help 15 Say Y or M here if you want to enable BIOS Enhanced Disk Drive 16 Services real mode BIOS calls to determine which disk 17 BIOS tries boot from. This information is then exported via sysfs. 18 19 This option is experimental and is known to fail to boot on some 20 obscure configurations. Most disk controller BIOS vendors do 21 not yet implement this feature. 22 23config EDD_OFF 24 bool "Sets default behavior for EDD detection to off" 25 depends on EDD 26 default n 27 help 28 Say Y if you want EDD disabled by default, even though it is compiled into the 29 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set 30 using the kernel parameter 'edd={on|skipmbr|off}'. 31 32config FIRMWARE_MEMMAP 33 bool "Add firmware-provided memory map to sysfs" if EXPERT 34 default X86 35 help 36 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap. 37 That memory map is used for example by kexec to set up parameter area 38 for the next kernel, but can also be used for debugging purposes. 39 40 See also Documentation/ABI/testing/sysfs-firmware-memmap. 41 42config EFI_PCDP 43 bool "Console device selection via EFI PCDP or HCDP table" 44 depends on ACPI && EFI && IA64 45 default y if IA64 46 help 47 If your firmware supplies the PCDP table, and you want to 48 automatically use the primary console device it describes 49 as the Linux console, say Y here. 50 51 If your firmware supplies the HCDP table, and you want to 52 use the first serial port it describes as the Linux console, 53 say Y here. If your EFI ConOut path contains only a UART 54 device, it will become the console automatically. Otherwise, 55 you must specify the "console=hcdp" kernel boot argument. 56 57 Neither the PCDP nor the HCDP affects naming of serial devices, 58 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending 59 on how the driver discovers devices. 60 61 You must also enable the appropriate drivers (serial, VGA, etc.) 62 63 See DIG64_HCDPv20_042804.pdf available from 64 <http://www.dig64.org/specifications/> 65 66config DELL_RBU 67 tristate "BIOS update support for DELL systems via sysfs" 68 depends on X86 69 select FW_LOADER 70 select FW_LOADER_USER_HELPER 71 help 72 Say m if you want to have the option of updating the BIOS for your 73 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP) 74 supporting application to communicate with the BIOS regarding the new 75 image for the image update to take effect. 76 See <file:Documentation/dell_rbu.txt> for more details on the driver. 77 78config DCDBAS 79 tristate "Dell Systems Management Base Driver" 80 depends on X86 81 help 82 The Dell Systems Management Base Driver provides a sysfs interface 83 for systems management software to perform System Management 84 Interrupts (SMIs) and Host Control Actions (system power cycle or 85 power off after OS shutdown) on certain Dell systems. 86 87 See <file:Documentation/dcdbas.txt> for more details on the driver 88 and the Dell systems on which Dell systems management software makes 89 use of this driver. 90 91 Say Y or M here to enable the driver for use by Dell systems 92 management software such as Dell OpenManage. 93 94config DMIID 95 bool "Export DMI identification via sysfs to userspace" 96 depends on DMI 97 default y 98 help 99 Say Y here if you want to query SMBIOS/DMI system identification 100 information from userspace through /sys/class/dmi/id/ or if you want 101 DMI-based module auto-loading. 102 103config DMI_SYSFS 104 tristate "DMI table support in sysfs" 105 depends on SYSFS && DMI 106 default n 107 help 108 Say Y or M here to enable the exporting of the raw DMI table 109 data via sysfs. This is useful for consuming the data without 110 requiring any access to /dev/mem at all. Tables are found 111 under /sys/firmware/dmi when this option is enabled and 112 loaded. 113 114config DMI_SCAN_MACHINE_NON_EFI_FALLBACK 115 bool 116 117config ISCSI_IBFT_FIND 118 bool "iSCSI Boot Firmware Table Attributes" 119 depends on X86 && ACPI 120 default n 121 help 122 This option enables the kernel to find the region of memory 123 in which the ISCSI Boot Firmware Table (iBFT) resides. This 124 is necessary for iSCSI Boot Firmware Table Attributes module to work 125 properly. 126 127config ISCSI_IBFT 128 tristate "iSCSI Boot Firmware Table Attributes module" 129 select ISCSI_BOOT_SYSFS 130 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL 131 default n 132 help 133 This option enables support for detection and exposing of iSCSI 134 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to 135 detect iSCSI boot parameters dynamically during system boot, say Y. 136 Otherwise, say N. 137 138config QCOM_SCM 139 bool 140 depends on ARM || ARM64 141 142config QCOM_SCM_32 143 def_bool y 144 depends on QCOM_SCM && ARM 145 146config QCOM_SCM_64 147 def_bool y 148 depends on QCOM_SCM && ARM64 149 150source "drivers/firmware/broadcom/Kconfig" 151source "drivers/firmware/google/Kconfig" 152source "drivers/firmware/efi/Kconfig" 153 154endmenu 155