Kconfig 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289
  1. menu "Generic Driver Options"
  2. config DM
  3. bool "Enable Driver Model"
  4. help
  5. This config option enables Driver Model. This brings in the core
  6. support, including scanning of platform data on start-up. If
  7. CONFIG_OF_CONTROL is enabled, the device tree will be scanned also
  8. when available.
  9. config SPL_DM
  10. bool "Enable Driver Model for SPL"
  11. depends on DM && SPL
  12. help
  13. Enable driver model in SPL. You will need to provide a
  14. suitable malloc() implementation. If you are not using the
  15. full malloc() enabled by CONFIG_SYS_SPL_MALLOC_START,
  16. consider using CONFIG_SYS_MALLOC_SIMPLE. In that case you
  17. must provide CONFIG_SPL_SYS_MALLOC_F_LEN to set the size.
  18. In most cases driver model will only allocate a few uclasses
  19. and devices in SPL, so 1KB should be enable. See
  20. CONFIG_SPL_SYS_MALLOC_F_LEN for more details on how to enable it.
  21. config TPL_DM
  22. bool "Enable Driver Model for TPL"
  23. depends on DM && TPL
  24. help
  25. Enable driver model in TPL. You will need to provide a
  26. suitable malloc() implementation. If you are not using the
  27. full malloc() enabled by CONFIG_SYS_SPL_MALLOC_START,
  28. consider using CONFIG_SYS_MALLOC_SIMPLE. In that case you
  29. must provide CONFIG_SPL_SYS_MALLOC_F_LEN to set the size.
  30. In most cases driver model will only allocate a few uclasses
  31. and devices in SPL, so 1KB should be enough. See
  32. CONFIG_SPL_SYS_MALLOC_F_LEN for more details on how to enable it.
  33. Disable this for very small implementations.
  34. config DM_WARN
  35. bool "Enable warnings in driver model"
  36. depends on DM
  37. default y
  38. help
  39. The dm_warn() function can use up quite a bit of space for its
  40. strings. By default this is disabled for SPL builds to save space.
  41. This will cause dm_warn() to be compiled out - it will do nothing
  42. when called.
  43. config DM_DEBUG
  44. bool "Enable debug messages in driver model core"
  45. depends on DM
  46. help
  47. Say Y here if you want to compile in debug messages in DM core.
  48. config DM_DEVICE_REMOVE
  49. bool "Support device removal"
  50. depends on DM
  51. default y
  52. help
  53. We can save some code space by dropping support for removing a
  54. device.
  55. Note that this may have undesirable results in the USB subsystem as
  56. it causes unplugged devices to linger around in the dm-tree, and it
  57. causes USB host controllers to not be stopped when booting the OS.
  58. config SPL_DM_DEVICE_REMOVE
  59. bool "Support device removal in SPL"
  60. depends on SPL_DM
  61. default n
  62. help
  63. We can save some code space by dropping support for removing a
  64. device. This is not normally required in SPL, so by default this
  65. option is disabled for SPL.
  66. config DM_STDIO
  67. bool "Support stdio registration"
  68. depends on DM
  69. default y
  70. help
  71. Normally serial drivers register with stdio so that they can be used
  72. as normal output devices. In SPL we don't normally use stdio, so
  73. we can omit this feature.
  74. config DM_SEQ_ALIAS
  75. bool "Support numbered aliases in device tree"
  76. depends on DM
  77. default y
  78. help
  79. Most boards will have a '/aliases' node containing the path to
  80. numbered devices (e.g. serial0 = &serial0). This feature can be
  81. disabled if it is not required.
  82. config SPL_DM_SEQ_ALIAS
  83. bool "Support numbered aliases in device tree in SPL"
  84. depends on SPL_DM
  85. default n
  86. help
  87. Most boards will have a '/aliases' node containing the path to
  88. numbered devices (e.g. serial0 = &serial0). This feature can be
  89. disabled if it is not required, to save code space in SPL.
  90. config REGMAP
  91. bool "Support register maps"
  92. depends on DM
  93. help
  94. Hardware peripherals tend to have one or more sets of registers
  95. which can be accessed to control the hardware. A register map
  96. models this with a simple read/write interface. It can in principle
  97. support any bus type (I2C, SPI) but so far this only supports
  98. direct memory access.
  99. config SPL_REGMAP
  100. bool "Support register maps in SPL"
  101. depends on SPL_DM
  102. help
  103. Hardware peripherals tend to have one or more sets of registers
  104. which can be accessed to control the hardware. A register map
  105. models this with a simple read/write interface. It can in principle
  106. support any bus type (I2C, SPI) but so far this only supports
  107. direct memory access.
  108. config TPL_REGMAP
  109. bool "Support register maps in TPL"
  110. depends on TPL_DM
  111. help
  112. Hardware peripherals tend to have one or more sets of registers
  113. which can be accessed to control the hardware. A register map
  114. models this with a simple read/write interface. It can in principle
  115. support any bus type (I2C, SPI) but so far this only supports
  116. direct memory access.
  117. config SYSCON
  118. bool "Support system controllers"
  119. depends on REGMAP
  120. help
  121. Many SoCs have a number of system controllers which are dealt with
  122. as a group by a single driver. Some common functionality is provided
  123. by this uclass, including accessing registers via regmap and
  124. assigning a unique number to each.
  125. config SPL_SYSCON
  126. bool "Support system controllers in SPL"
  127. depends on SPL_REGMAP
  128. help
  129. Many SoCs have a number of system controllers which are dealt with
  130. as a group by a single driver. Some common functionality is provided
  131. by this uclass, including accessing registers via regmap and
  132. assigning a unique number to each.
  133. config TPL_SYSCON
  134. bool "Support system controllers in TPL"
  135. depends on TPL_REGMAP
  136. help
  137. Many SoCs have a number of system controllers which are dealt with
  138. as a group by a single driver. Some common functionality is provided
  139. by this uclass, including accessing registers via regmap and
  140. assigning a unique number to each.
  141. config DEVRES
  142. bool "Managed device resources"
  143. depends on DM
  144. help
  145. This option enables the Managed device resources core support.
  146. Device resources managed by the devres framework are automatically
  147. released whether initialization fails half-way or the device gets
  148. detached.
  149. If this option is disabled, devres functions fall back to
  150. non-managed variants. For example, devres_alloc() to kzalloc(),
  151. devm_kmalloc() to kmalloc(), etc.
  152. config DEBUG_DEVRES
  153. bool "Managed device resources debugging functions"
  154. depends on DEVRES
  155. help
  156. If this option is enabled, devres debug messages are printed.
  157. Also, a function is available to dump a list of device resources.
  158. Select this if you are having a problem with devres or want to
  159. debug resource management for a managed device.
  160. If you are unsure about this, Say N here.
  161. config SIMPLE_BUS
  162. bool "Support simple-bus driver"
  163. depends on DM && OF_CONTROL
  164. default y
  165. help
  166. Supports the 'simple-bus' driver, which is used on some systems.
  167. config SPL_SIMPLE_BUS
  168. bool "Support simple-bus driver in SPL"
  169. depends on SPL_DM && SPL_OF_CONTROL
  170. default y
  171. help
  172. Supports the 'simple-bus' driver, which is used on some systems
  173. in SPL.
  174. config SIMPLE_PM_BUS
  175. bool "Support simple-pm-bus driver"
  176. depends on DM && OF_CONTROL && CLK && POWER_DOMAIN
  177. help
  178. Supports the 'simple-pm-bus' driver, which is used for busses that
  179. have power domains and/or clocks which need to be enabled before use.
  180. config OF_TRANSLATE
  181. bool "Translate addresses using fdt_translate_address"
  182. depends on DM && OF_CONTROL
  183. default y
  184. help
  185. If this option is enabled, the reg property will be translated
  186. using the fdt_translate_address() function. This is necessary
  187. on some platforms (e.g. MVEBU) using complex "ranges"
  188. properties in many nodes. As this translation is not handled
  189. correctly in the default simple_bus_translate() function.
  190. If this option is not enabled, simple_bus_translate() will be
  191. used for the address translation. This function is faster and
  192. smaller in size than fdt_translate_address().
  193. config SPL_OF_TRANSLATE
  194. bool "Translate addresses using fdt_translate_address in SPL"
  195. depends on SPL_DM && SPL_OF_CONTROL
  196. default n
  197. help
  198. If this option is enabled, the reg property will be translated
  199. using the fdt_translate_address() function. This is necessary
  200. on some platforms (e.g. MVEBU) using complex "ranges"
  201. properties in many nodes. As this translation is not handled
  202. correctly in the default simple_bus_translate() function.
  203. If this option is not enabled, simple_bus_translate() will be
  204. used for the address translation. This function is faster and
  205. smaller in size than fdt_translate_address().
  206. config TRANSLATION_OFFSET
  207. bool "Platforms specific translation offset"
  208. depends on DM && OF_CONTROL
  209. help
  210. Some platforms need a special address translation. Those
  211. platforms (e.g. mvebu in SPL) can configure a translation
  212. offset by enabling this option and setting the translation_offset
  213. variable in the GD in their platform- / board-specific code.
  214. config OF_ISA_BUS
  215. bool
  216. depends on OF_TRANSLATE
  217. help
  218. Is this option is enabled then support for the ISA bus will
  219. be included for addresses read from DT. This is something that
  220. should be known to be required or not based upon the board
  221. being targeted, and whether or not it makes use of an ISA bus.
  222. The bus is matched based upon its node name equalling "isa". The
  223. busses #address-cells should equal 2, with the first cell being
  224. used to hold flags & flag 0x1 indicating that the address range
  225. should be accessed using I/O port in/out accessors. The second
  226. cell holds the offset into ISA bus address space. The #size-cells
  227. property should equal 1, and of course holds the size of the
  228. address range used by a device.
  229. If this option is not enabled then support for the ISA bus is
  230. not included and any such busses used in DT will be treated as
  231. typical simple-bus compatible busses. This will lead to
  232. mistranslation of device addresses, so ensure that this is
  233. enabled if your board does include an ISA bus.
  234. config DM_DEV_READ_INLINE
  235. bool
  236. default y if !OF_LIVE
  237. config ACPIGEN
  238. bool "Support ACPI table generation in driver model"
  239. default y if SANDBOX || (GENERATE_ACPI_TABLE && !QEMU)
  240. help
  241. This option enables generation of ACPI tables using driver-model
  242. devices. It adds a new operation struct to each driver, to support
  243. things like generating device-specific tables and returning the ACPI
  244. name of a device.
  245. config INTEL_ACPIGEN
  246. bool "Support ACPI table generation for Intel SoCs"
  247. depends on ACPIGEN
  248. help
  249. This option adds some functions used for programatic generation of
  250. ACPI tables on Intel SoCs. This provides features for writing CPU
  251. information such as P states and T stages. Also included is a way
  252. to create a GNVS table and set it up.
  253. endmenu