Kconfig 6.0 KB

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