Kconfig 8.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247
  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. This is not normally required in SPL, so by default this
  55. option is disabled for SPL.
  56. Note that this may have undesirable results in the USB subsystem as
  57. it causes unplugged devices to linger around in the dm-tree, and it
  58. causes USB host controllers to not be stopped when booting the OS.
  59. config DM_STDIO
  60. bool "Support stdio registration"
  61. depends on DM
  62. default y
  63. help
  64. Normally serial drivers register with stdio so that they can be used
  65. as normal output devices. In SPL we don't normally use stdio, so
  66. we can omit this feature.
  67. config DM_SEQ_ALIAS
  68. bool "Support numbered aliases in device tree"
  69. depends on DM
  70. default y
  71. help
  72. Most boards will have a '/aliases' node containing the path to
  73. numbered devices (e.g. serial0 = &serial0). This feature can be
  74. disabled if it is not required.
  75. config SPL_DM_SEQ_ALIAS
  76. bool "Support numbered aliases in device tree in SPL"
  77. depends on DM
  78. default n
  79. help
  80. Most boards will have a '/aliases' node containing the path to
  81. numbered devices (e.g. serial0 = &serial0). This feature can be
  82. disabled if it is not required, to save code space in SPL.
  83. config REGMAP
  84. bool "Support register maps"
  85. depends on DM
  86. help
  87. Hardware peripherals tend to have one or more sets of registers
  88. which can be accessed to control the hardware. A register map
  89. models this with a simple read/write interface. It can in principle
  90. support any bus type (I2C, SPI) but so far this only supports
  91. direct memory access.
  92. config SPL_REGMAP
  93. bool "Support register maps in SPL"
  94. depends on SPL_DM
  95. help
  96. Hardware peripherals tend to have one or more sets of registers
  97. which can be accessed to control the hardware. A register map
  98. models this with a simple read/write interface. It can in principle
  99. support any bus type (I2C, SPI) but so far this only supports
  100. direct memory access.
  101. config TPL_REGMAP
  102. bool "Support register maps in TPL"
  103. depends on TPL_DM
  104. help
  105. Hardware peripherals tend to have one or more sets of registers
  106. which can be accessed to control the hardware. A register map
  107. models this with a simple read/write interface. It can in principle
  108. support any bus type (I2C, SPI) but so far this only supports
  109. direct memory access.
  110. config SYSCON
  111. bool "Support system controllers"
  112. depends on REGMAP
  113. help
  114. Many SoCs have a number of system controllers which are dealt with
  115. as a group by a single driver. Some common functionality is provided
  116. by this uclass, including accessing registers via regmap and
  117. assigning a unique number to each.
  118. config SPL_SYSCON
  119. bool "Support system controllers in SPL"
  120. depends on SPL_REGMAP
  121. help
  122. Many SoCs have a number of system controllers which are dealt with
  123. as a group by a single driver. Some common functionality is provided
  124. by this uclass, including accessing registers via regmap and
  125. assigning a unique number to each.
  126. config TPL_SYSCON
  127. bool "Support system controllers in TPL"
  128. depends on TPL_REGMAP
  129. help
  130. Many SoCs have a number of system controllers which are dealt with
  131. as a group by a single driver. Some common functionality is provided
  132. by this uclass, including accessing registers via regmap and
  133. assigning a unique number to each.
  134. config DEVRES
  135. bool "Managed device resources"
  136. depends on DM
  137. help
  138. This option enables the Managed device resources core support.
  139. Device resources managed by the devres framework are automatically
  140. released whether initialization fails half-way or the device gets
  141. detached.
  142. If this option is disabled, devres functions fall back to
  143. non-managed variants. For example, devres_alloc() to kzalloc(),
  144. devm_kmalloc() to kmalloc(), etc.
  145. config DEBUG_DEVRES
  146. bool "Managed device resources debugging functions"
  147. depends on DEVRES
  148. help
  149. If this option is enabled, devres debug messages are printed.
  150. Also, a function is available to dump a list of device resources.
  151. Select this if you are having a problem with devres or want to
  152. debug resource management for a managed device.
  153. If you are unsure about this, Say N here.
  154. config SIMPLE_BUS
  155. bool "Support simple-bus driver"
  156. depends on DM && OF_CONTROL
  157. default y
  158. help
  159. Supports the 'simple-bus' driver, which is used on some systems.
  160. config SPL_SIMPLE_BUS
  161. bool "Support simple-bus driver in SPL"
  162. depends on SPL_DM && SPL_OF_CONTROL
  163. default y
  164. help
  165. Supports the 'simple-bus' driver, which is used on some systems
  166. in SPL.
  167. config OF_TRANSLATE
  168. bool "Translate addresses using fdt_translate_address"
  169. depends on DM && OF_CONTROL
  170. default y
  171. help
  172. If this option is enabled, the reg property will be translated
  173. using the fdt_translate_address() function. This is necessary
  174. on some platforms (e.g. MVEBU) using complex "ranges"
  175. properties in many nodes. As this translation is not handled
  176. correctly in the default simple_bus_translate() function.
  177. If this option is not enabled, simple_bus_translate() will be
  178. used for the address translation. This function is faster and
  179. smaller in size than fdt_translate_address().
  180. config SPL_OF_TRANSLATE
  181. bool "Translate addresses using fdt_translate_address in SPL"
  182. depends on SPL_DM && SPL_OF_CONTROL
  183. default n
  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 OF_ISA_BUS
  194. bool
  195. depends on OF_TRANSLATE
  196. help
  197. Is this option is enabled then support for the ISA bus will
  198. be included for addresses read from DT. This is something that
  199. should be known to be required or not based upon the board
  200. being targetted, and whether or not it makes use of an ISA bus.
  201. The bus is matched based upon its node name equalling "isa". The
  202. busses #address-cells should equal 2, with the first cell being
  203. used to hold flags & flag 0x1 indicating that the address range
  204. should be accessed using I/O port in/out accessors. The second
  205. cell holds the offset into ISA bus address space. The #size-cells
  206. property should equal 1, and of course holds the size of the
  207. address range used by a device.
  208. If this option is not enabled then support for the ISA bus is
  209. not included and any such busses used in DT will be treated as
  210. typical simple-bus compatible busses. This will lead to
  211. mistranslation of device addresses, so ensure that this is
  212. enabled if your board does include an ISA bus.
  213. config DM_DEV_READ_INLINE
  214. bool
  215. default y if !OF_LIVE
  216. endmenu