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_SPL_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_TPL_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 Driver Model for VPL"
43 Enable driver model in VPL. You will need to provide a
44 suitable malloc() implementation. If you are not using the
45 full malloc() enabled by CONFIG_SYS_SPL_MALLOC_START,
46 consider using CONFIG_SPL_SYS_MALLOC_SIMPLE.
49 bool "Enable warnings in driver model"
53 Enable this to see warnings related to driver model.
55 Warnings may help with debugging, such as when expected devices do
56 not bind correctly. If the option is disabled, dm_warn() is compiled
57 out - it will do nothing when called.
60 bool "Enable warnings in driver model wuth SPL"
63 Enable this to see warnings related to driver model in SPL
65 The dm_warn() function can use up quite a bit of space for its
66 strings. By default this is disabled for SPL builds to save space.
68 Warnings may help with debugging, such as when expected devices do
69 not bind correctly. If the option is disabled, dm_warn() is compiled
70 out - it will do nothing when called.
73 bool "Enable debug messages in driver model core"
76 Say Y here if you want to compile in debug messages in DM core.
78 config DM_DEVICE_REMOVE
79 bool "Support device removal"
83 We can save some code space by dropping support for removing a
86 Note that this may have undesirable results in the USB subsystem as
87 it causes unplugged devices to linger around in the dm-tree, and it
88 causes USB host controllers to not be stopped when booting the OS.
91 bool "Support events with driver model"
92 depends on DM && EVENT
95 This enables support for generating events related to driver model
96 operations, such as prbing or removing a device. Subsystems can
97 register a 'spy' function that is called when the event occurs.
99 config SPL_DM_DEVICE_REMOVE
100 bool "Support device removal in SPL"
103 We can save some code space by dropping support for removing a
104 device. This is not normally required in SPL, so by default this
105 option is disabled for SPL.
108 bool "Support stdio registration"
112 Normally serial drivers register with stdio so that they can be used
113 as normal output devices. In SPL we don't normally use stdio, so
114 we can omit this feature.
117 bool "Support numbered aliases in device tree"
121 Most boards will have a '/aliases' node containing the path to
122 numbered devices (e.g. serial0 = &serial0). This feature can be
123 disabled if it is not required.
125 config SPL_DM_SEQ_ALIAS
126 bool "Support numbered aliases in device tree in SPL"
129 Most boards will have a '/aliases' node containing the path to
130 numbered devices (e.g. serial0 = &serial0). This feature can be
131 disabled if it is not required, to save code space in SPL.
133 config VPL_DM_SEQ_ALIAS
134 bool "Support numbered aliases in device tree in VPL"
138 Most boards will have a '/aliases' node containing the path to
139 numbered devices (e.g. serial0 = &serial0). This feature can be
140 disabled if it is not required, to save code space in VPL.
142 config SPL_DM_INLINE_OFNODE
143 bool "Inline some ofnode functions which are seldom used in SPL"
147 This applies to several ofnode functions (see ofnode.h) which are
148 seldom used. Inlining them can help reduce code size.
150 config TPL_DM_INLINE_OFNODE
151 bool "Inline some ofnode functions which are seldom used in TPL"
155 This applies to several ofnode functions (see ofnode.h) which are
156 seldom used. Inlining them can help reduce code size.
159 bool "Support per-device DMA constraints"
162 Enable this to extract per-device DMA constraints, only supported on
163 device-tree systems for now. This is needed in order translate
164 addresses on systems where different buses have different views of
165 the physical address space.
168 bool "Support register maps"
171 Hardware peripherals tend to have one or more sets of registers
172 which can be accessed to control the hardware. A register map
173 models this with a simple read/write interface. It can in principle
174 support any bus type (I2C, SPI) but so far this only supports
175 direct memory access.
178 bool "Support register maps in SPL"
181 Hardware peripherals tend to have one or more sets of registers
182 which can be accessed to control the hardware. A register map
183 models this with a simple read/write interface. It can in principle
184 support any bus type (I2C, SPI) but so far this only supports
185 direct memory access.
188 bool "Support register maps in TPL"
191 Hardware peripherals tend to have one or more sets of registers
192 which can be accessed to control the hardware. A register map
193 models this with a simple read/write interface. It can in principle
194 support any bus type (I2C, SPI) but so far this only supports
195 direct memory access.
198 bool "Support register maps in VPL"
201 Hardware peripherals tend to have one or more sets of registers
202 which can be accessed to control the hardware. A register map
203 models this with a simple read/write interface. It can in principle
204 support any bus type (I2C, SPI) but so far this only supports
205 direct memory access.
208 bool "Support system controllers"
211 Many SoCs have a number of system controllers which are dealt with
212 as a group by a single driver. Some common functionality is provided
213 by this uclass, including accessing registers via regmap and
214 assigning a unique number to each.
217 bool "Support system controllers in SPL"
218 depends on SPL_REGMAP
220 Many SoCs have a number of system controllers which are dealt with
221 as a group by a single driver. Some common functionality is provided
222 by this uclass, including accessing registers via regmap and
223 assigning a unique number to each.
226 bool "Support system controllers in TPL"
227 depends on SPL_REGMAP
229 Many SoCs have a number of system controllers which are dealt with
230 as a group by a single driver. Some common functionality is provided
231 by this uclass, including accessing registers via regmap and
232 assigning a unique number to each.
235 bool "Support system controllers in VPL"
236 depends on VPL_REGMAP
238 Many SoCs have a number of system controllers which are dealt with
239 as a group by a single driver. Some common functionality is provided
240 by this uclass, including accessing registers via regmap and
241 assigning a unique number to each.
244 bool "Managed device resources"
247 This option enables the Managed device resources core support.
248 Device resources managed by the devres framework are automatically
249 released whether initialization fails half-way or the device gets
252 If this option is disabled, devres functions fall back to
253 non-managed variants. For example, devres_alloc() to kzalloc(),
254 devm_kmalloc() to kmalloc(), etc.
257 bool "Managed device resources debugging functions"
260 If this option is enabled, devres debug messages are printed.
261 Also, a function is available to dump a list of device resources.
262 Select this if you are having a problem with devres or want to
263 debug resource management for a managed device.
265 If you are unsure about this, Say N here.
268 bool "Support simple-bus driver"
269 depends on DM && OF_CONTROL
272 Supports the 'simple-bus' driver, which is used on some systems.
274 config SPL_SIMPLE_BUS
275 bool "Support simple-bus driver in SPL"
276 depends on SPL_DM && SPL_OF_CONTROL
279 Supports the 'simple-bus' driver, which is used on some systems
282 config SIMPLE_BUS_CORRECT_RANGE
283 bool "Decode the 'simple-bus' <range> by honoring the #address-cells and #size-cells"
284 depends on SIMPLE_BUS
287 Decoding the 'simple-bus' <range> by honoring the #address-cells
288 and #size-cells of parent/child bus. If unset, #address-cells of
289 parent bus is assumed to be 1, #address-cells and #size-cells of
290 child bus is also assumed to be 1, to save some spaces of using
291 an advanced API to decode the <range>, which benefits SPL image
292 builds that have size limits.
294 If you are unsure about this, Say N here.
297 bool "Support simple-pm-bus driver"
298 depends on DM && OF_CONTROL && CLK && POWER_DOMAIN
300 Supports the 'simple-pm-bus' driver, which is used for busses that
301 have power domains and/or clocks which need to be enabled before use.
304 bool "Translate addresses using fdt_translate_address"
305 depends on DM && OF_CONTROL
308 If this option is enabled, the reg property will be translated
309 using the fdt_translate_address() function. This is necessary
310 on some platforms (e.g. MVEBU) using complex "ranges"
311 properties in many nodes. As this translation is not handled
312 correctly in the default simple_bus_translate() function.
314 If this option is not enabled, simple_bus_translate() will be
315 used for the address translation. This function is faster and
316 smaller in size than fdt_translate_address().
318 config SPL_OF_TRANSLATE
319 bool "Translate addresses using fdt_translate_address in SPL"
320 depends on SPL_DM && SPL_OF_CONTROL
322 If this option is enabled, the reg property will be translated
323 using the fdt_translate_address() function. This is necessary
324 on some platforms (e.g. MVEBU) using complex "ranges"
325 properties in many nodes. As this translation is not handled
326 correctly in the default simple_bus_translate() function.
328 If this option is not enabled, simple_bus_translate() will be
329 used for the address translation. This function is faster and
330 smaller in size than fdt_translate_address().
332 config VPL_OF_TRANSLATE
333 bool "Translate addresses using fdt_translate_address in SPL"
334 depends on SPL_DM && VPL_OF_CONTROL
336 If this option is enabled, the reg property will be translated
337 using the fdt_translate_address() function. This is necessary
338 on some platforms (e.g. MVEBU) using complex "ranges"
339 properties in many nodes. As this translation is not handled
340 correctly in the default simple_bus_translate() function.
342 If this option is not enabled, simple_bus_translate() will be
343 used for the address translation. This function is faster and
344 smaller in size than fdt_translate_address().
346 config TRANSLATION_OFFSET
347 bool "Platforms specific translation offset"
348 depends on DM && OF_CONTROL
350 Some platforms need a special address translation. Those
351 platforms (e.g. mvebu in SPL) can configure a translation
352 offset by enabling this option and setting the translation_offset
353 variable in the GD in their platform- / board-specific code.
357 depends on OF_TRANSLATE
359 Is this option is enabled then support for the ISA bus will
360 be included for addresses read from DT. This is something that
361 should be known to be required or not based upon the board
362 being targeted, and whether or not it makes use of an ISA bus.
364 The bus is matched based upon its node name equalling "isa". The
365 busses #address-cells should equal 2, with the first cell being
366 used to hold flags & flag 0x1 indicating that the address range
367 should be accessed using I/O port in/out accessors. The second
368 cell holds the offset into ISA bus address space. The #size-cells
369 property should equal 1, and of course holds the size of the
370 address range used by a device.
372 If this option is not enabled then support for the ISA bus is
373 not included and any such busses used in DT will be treated as
374 typical simple-bus compatible busses. This will lead to
375 mistranslation of device addresses, so ensure that this is
376 enabled if your board does include an ISA bus.
378 config DM_DEV_READ_INLINE
380 default y if !OF_LIVE
383 bool "Support ACPI table generation in driver model"
384 default y if SANDBOX || (GENERATE_ACPI_TABLE && !QEMU)
387 This option enables generation of ACPI tables using driver-model
388 devices. It adds a new operation struct to each driver, to support
389 things like generating device-specific tables and returning the ACPI
393 bool "Include bounce buffer API"
395 Some peripherals support DMA from a subset of physically
396 addressable memory only. To support such peripherals, the
397 bounce buffer API uses a temporary buffer: it copies data
398 to/from DMA regions while managing cache operations.
400 A second possible use of bounce buffers is their ability to
401 provide aligned buffers for DMA operations.