1 menu "Generic Driver Options"
4 bool "Enable Driver Model"
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
12 bool "Enable Driver Model for SPL"
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.
25 bool "Enable Driver Model for TPL"
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.
39 bool "Enable warnings in driver model"
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
49 bool "Enable debug messages in driver model core"
52 Say Y here if you want to compile in debug messages in DM core.
54 config DM_DEVICE_REMOVE
55 bool "Support device removal"
59 We can save some code space by dropping support for removing a
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.
66 config SPL_DM_DEVICE_REMOVE
67 bool "Support device removal in SPL"
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.
76 bool "Support stdio registration"
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.
85 bool "Support numbered aliases in device tree"
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.
93 config SPL_DM_SEQ_ALIAS
94 bool "Support numbered aliases in device tree in SPL"
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.
103 bool "Support register maps"
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.
113 bool "Support register maps in SPL"
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.
123 bool "Support register maps in TPL"
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.
133 bool "Support system controllers"
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.
142 bool "Support system controllers in SPL"
143 depends on SPL_REGMAP
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.
151 bool "Support system controllers in TPL"
152 depends on TPL_REGMAP
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.
160 bool "Managed device resources"
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
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.
173 bool "Managed device resources debugging functions"
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.
181 If you are unsure about this, Say N here.
184 bool "Support simple-bus driver"
185 depends on DM && OF_CONTROL
188 Supports the 'simple-bus' driver, which is used on some systems.
190 config SPL_SIMPLE_BUS
191 bool "Support simple-bus driver in SPL"
192 depends on SPL_DM && SPL_OF_CONTROL
195 Supports the 'simple-bus' driver, which is used on some systems
199 bool "Support simple-pm-bus driver"
200 depends on DM && OF_CONTROL && CLK && POWER_DOMAIN
202 Supports the 'simple-pm-bus' driver, which is used for busses that
203 have power domains and/or clocks which need to be enabled before use.
206 bool "Translate addresses using fdt_translate_address"
207 depends on DM && OF_CONTROL
210 If this option is enabled, the reg property will be translated
211 using the fdt_translate_address() function. This is necessary
212 on some platforms (e.g. MVEBU) using complex "ranges"
213 properties in many nodes. As this translation is not handled
214 correctly in the default simple_bus_translate() function.
216 If this option is not enabled, simple_bus_translate() will be
217 used for the address translation. This function is faster and
218 smaller in size than fdt_translate_address().
220 config SPL_OF_TRANSLATE
221 bool "Translate addresses using fdt_translate_address in SPL"
222 depends on SPL_DM && SPL_OF_CONTROL
225 If this option is enabled, the reg property will be translated
226 using the fdt_translate_address() function. This is necessary
227 on some platforms (e.g. MVEBU) using complex "ranges"
228 properties in many nodes. As this translation is not handled
229 correctly in the default simple_bus_translate() function.
231 If this option is not enabled, simple_bus_translate() will be
232 used for the address translation. This function is faster and
233 smaller in size than fdt_translate_address().
235 config TRANSLATION_OFFSET
236 bool "Platforms specific translation offset"
237 depends on DM && OF_CONTROL
239 Some platforms need a special address translation. Those
240 platforms (e.g. mvebu in SPL) can configure a translation
241 offset by enabling this option and setting the translation_offset
242 variable in the GD in their platform- / board-specific code.
246 depends on OF_TRANSLATE
248 Is this option is enabled then support for the ISA bus will
249 be included for addresses read from DT. This is something that
250 should be known to be required or not based upon the board
251 being targeted, and whether or not it makes use of an ISA bus.
253 The bus is matched based upon its node name equalling "isa". The
254 busses #address-cells should equal 2, with the first cell being
255 used to hold flags & flag 0x1 indicating that the address range
256 should be accessed using I/O port in/out accessors. The second
257 cell holds the offset into ISA bus address space. The #size-cells
258 property should equal 1, and of course holds the size of the
259 address range used by a device.
261 If this option is not enabled then support for the ISA bus is
262 not included and any such busses used in DT will be treated as
263 typical simple-bus compatible busses. This will lead to
264 mistranslation of device addresses, so ensure that this is
265 enabled if your board does include an ISA bus.
267 config DM_DEV_READ_INLINE
269 default y if !OF_LIVE
272 bool "Support ACPI table generation in driver model"
273 default y if SANDBOX || GENERATE_ACPI_TABLE
275 This option enables generation of ACPI tables using driver-model
276 devices. It adds a new operation struct to each driver, to support
277 things like generating device-specific tables and returning the ACPI