]>
Commit | Line | Data |
---|---|---|
0b11dbf7 MY |
1 | menu "Generic Driver Options" |
2 | ||
da333ae7 MY |
3 | config DM |
4 | bool "Enable Driver Model" | |
da333ae7 | 5 | help |
f94a1bed SG |
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. | |
91a91ff8 SG |
10 | |
11 | config 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 | |
f1896c45 | 19 | must provide CONFIG_SPL_SYS_MALLOC_F_LEN to set the size. |
91a91ff8 SG |
20 | In most cases driver model will only allocate a few uclasses |
21 | and devices in SPL, so 1KB should be enable. See | |
f1896c45 | 22 | CONFIG_SPL_SYS_MALLOC_F_LEN for more details on how to enable it. |
91a91ff8 | 23 | |
5a6f06f6 SG |
24 | config 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 | |
f1896c45 | 32 | must provide CONFIG_SPL_SYS_MALLOC_F_LEN to set the size. |
5a6f06f6 SG |
33 | In most cases driver model will only allocate a few uclasses |
34 | and devices in SPL, so 1KB should be enough. See | |
f1896c45 | 35 | CONFIG_SPL_SYS_MALLOC_F_LEN for more details on how to enable it. |
5a6f06f6 SG |
36 | Disable this for very small implementations. |
37 | ||
91a91ff8 SG |
38 | config DM_WARN |
39 | bool "Enable warnings in driver model" | |
d648964f MY |
40 | depends on DM |
41 | default y | |
91a91ff8 SG |
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. | |
91a91ff8 SG |
47 | |
48 | config DM_DEVICE_REMOVE | |
49 | bool "Support device removal" | |
d648964f MY |
50 | depends on DM |
51 | default y | |
91a91ff8 SG |
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. | |
91a91ff8 | 56 | |
e5c4564e HG |
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 | ||
91a91ff8 SG |
61 | config DM_STDIO |
62 | bool "Support stdio registration" | |
d648964f MY |
63 | depends on DM |
64 | default y | |
91a91ff8 SG |
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. | |
36fa61dc SG |
69 | |
70 | config DM_SEQ_ALIAS | |
71 | bool "Support numbered aliases in device tree" | |
72 | depends on DM | |
73 | default y | |
4f627c5a NR |
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 | ||
79 | config SPL_DM_SEQ_ALIAS | |
80 | bool "Support numbered aliases in device tree in SPL" | |
81 | depends on DM | |
82 | default n | |
36fa61dc SG |
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. | |
12dc8e75 SG |
87 | |
88 | config 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 | ||
41c7f664 | 98 | config SPL_REGMAP |
99 | bool "Support register maps in SPL" | |
9c447370 | 100 | depends on SPL_DM |
41c7f664 | 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 | ||
c6ac6c1b PT |
108 | config TPL_REGMAP |
109 | bool "Support register maps in TPL" | |
110 | depends on TPL_DM | |
111 | help | |
112 | Hardware peripherals tend to have one or more sets of registers | |
113 | which can be accessed to control the hardware. A register map | |
114 | models this with a simple read/write interface. It can in principle | |
115 | support any bus type (I2C, SPI) but so far this only supports | |
116 | direct memory access. | |
117 | ||
12dc8e75 SG |
118 | config SYSCON |
119 | bool "Support system controllers" | |
120 | depends on REGMAP | |
121 | help | |
122 | Many SoCs have a number of system controllers which are dealt with | |
123 | as a group by a single driver. Some common functionality is provided | |
124 | by this uclass, including accessing registers via regmap and | |
125 | assigning a unique number to each. | |
608f26c5 | 126 | |
41c7f664 | 127 | config SPL_SYSCON |
128 | bool "Support system controllers in SPL" | |
9c447370 | 129 | depends on SPL_REGMAP |
41c7f664 | 130 | help |
131 | Many SoCs have a number of system controllers which are dealt with | |
132 | as a group by a single driver. Some common functionality is provided | |
133 | by this uclass, including accessing registers via regmap and | |
134 | assigning a unique number to each. | |
135 | ||
c6ac6c1b PT |
136 | config TPL_SYSCON |
137 | bool "Support system controllers in TPL" | |
138 | depends on TPL_REGMAP | |
139 | help | |
140 | Many SoCs have a number of system controllers which are dealt with | |
141 | as a group by a single driver. Some common functionality is provided | |
142 | by this uclass, including accessing registers via regmap and | |
143 | assigning a unique number to each. | |
144 | ||
e2282d70 MY |
145 | config DEVRES |
146 | bool "Managed device resources" | |
147 | depends on DM | |
148 | help | |
149 | This option enables the Managed device resources core support. | |
150 | Device resources managed by the devres framework are automatically | |
151 | released whether initialization fails half-way or the device gets | |
152 | detached. | |
153 | ||
154 | If this option is disabled, devres functions fall back to | |
155 | non-managed variants. For example, devres_alloc() to kzalloc(), | |
156 | devm_kmalloc() to kmalloc(), etc. | |
157 | ||
608f26c5 | 158 | config DEBUG_DEVRES |
40b6f2d0 | 159 | bool "Managed device resources debugging functions" |
e2282d70 | 160 | depends on DEVRES |
608f26c5 MY |
161 | help |
162 | If this option is enabled, devres debug messages are printed. | |
40b6f2d0 | 163 | Also, a function is available to dump a list of device resources. |
608f26c5 MY |
164 | Select this if you are having a problem with devres or want to |
165 | debug resource management for a managed device. | |
166 | ||
167 | If you are unsure about this, Say N here. | |
0b11dbf7 | 168 | |
628d792c MV |
169 | config SIMPLE_BUS |
170 | bool "Support simple-bus driver" | |
171 | depends on DM && OF_CONTROL | |
172 | default y | |
173 | help | |
174 | Supports the 'simple-bus' driver, which is used on some systems. | |
175 | ||
176 | config SPL_SIMPLE_BUS | |
177 | bool "Support simple-bus driver in SPL" | |
178 | depends on SPL_DM && SPL_OF_CONTROL | |
8bebf03c | 179 | default y |
628d792c MV |
180 | help |
181 | Supports the 'simple-bus' driver, which is used on some systems | |
182 | in SPL. | |
183 | ||
ef5cd330 SR |
184 | config OF_TRANSLATE |
185 | bool "Translate addresses using fdt_translate_address" | |
186 | depends on DM && OF_CONTROL | |
187 | default y | |
188 | help | |
189 | If this option is enabled, the reg property will be translated | |
190 | using the fdt_translate_address() function. This is necessary | |
191 | on some platforms (e.g. MVEBU) using complex "ranges" | |
192 | properties in many nodes. As this translation is not handled | |
193 | correctly in the default simple_bus_translate() function. | |
194 | ||
195 | If this option is not enabled, simple_bus_translate() will be | |
196 | used for the address translation. This function is faster and | |
197 | smaller in size than fdt_translate_address(). | |
198 | ||
199 | config SPL_OF_TRANSLATE | |
7b98a3b6 | 200 | bool "Translate addresses using fdt_translate_address in SPL" |
ef5cd330 SR |
201 | depends on SPL_DM && SPL_OF_CONTROL |
202 | default n | |
203 | help | |
204 | If this option is enabled, the reg property will be translated | |
205 | using the fdt_translate_address() function. This is necessary | |
206 | on some platforms (e.g. MVEBU) using complex "ranges" | |
207 | properties in many nodes. As this translation is not handled | |
208 | correctly in the default simple_bus_translate() function. | |
209 | ||
210 | If this option is not enabled, simple_bus_translate() will be | |
211 | used for the address translation. This function is faster and | |
212 | smaller in size than fdt_translate_address(). | |
213 | ||
0a222d53 PB |
214 | config OF_ISA_BUS |
215 | bool | |
216 | depends on OF_TRANSLATE | |
217 | help | |
218 | Is this option is enabled then support for the ISA bus will | |
219 | be included for addresses read from DT. This is something that | |
220 | should be known to be required or not based upon the board | |
221 | being targetted, and whether or not it makes use of an ISA bus. | |
222 | ||
223 | The bus is matched based upon its node name equalling "isa". The | |
224 | busses #address-cells should equal 2, with the first cell being | |
225 | used to hold flags & flag 0x1 indicating that the address range | |
226 | should be accessed using I/O port in/out accessors. The second | |
227 | cell holds the offset into ISA bus address space. The #size-cells | |
228 | property should equal 1, and of course holds the size of the | |
229 | address range used by a device. | |
230 | ||
231 | If this option is not enabled then support for the ISA bus is | |
232 | not included and any such busses used in DT will be treated as | |
233 | typical simple-bus compatible busses. This will lead to | |
234 | mistranslation of device addresses, so ensure that this is | |
235 | enabled if your board does include an ISA bus. | |
236 | ||
f11c7ab9 SG |
237 | config DM_DEV_READ_INLINE |
238 | bool | |
239 | default y if !OF_LIVE | |
240 | ||
0b11dbf7 | 241 | endmenu |