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