Kconfig 11 KB

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