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