Kconfig 7.2 KB

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