6 config SPL_LIBCOMMON_SUPPORT
9 config SPL_LIBGENERIC_SUPPORT
19 bool "Tegra AES128 crypto module"
23 config TEGRA_GP_PADCTRL
27 bool "Tegra IVC protocol"
29 IVC (Inter-VM Communication) protocol is a Tegra-specific IPC
30 (Inter Processor Communication) framework. Within the context of
31 U-Boot, it is typically used for communication between the main CPU
32 and various auxiliary processors.
43 config TEGRA_PMC_SECURE
48 bool "Tegra common options"
49 select BOARD_EARLY_INIT_F
68 bool "Tegra common options for SoCs without BPMP"
70 select TEGRA_CAR_CLOCK
71 select TEGRA_CAR_RESET
73 config TEGRA_ARMV7_COMMON
74 bool "Tegra 32-bit common options"
78 select SPL_BOARD_INIT if SPL
79 select SPL_SKIP_LOWLEVEL_INIT_ONLY if SPL
85 select TEGRA_GP_PADCTRL
92 config TEGRA_ARMV8_COMMON
93 bool "Tegra 64-bit common options"
95 select INIT_SP_RELATIVE
96 select LINUX_KERNEL_IMAGE_HEADER
97 select POSITION_INDEPENDENT
100 if TEGRA_ARMV8_COMMON
101 config LNX_KRNL_IMG_TEXT_OFFSET_BASE
106 prompt "Tegra SoC select"
110 bool "Tegra20 family"
111 select ARM_ERRATA_716044
112 select ARM_ERRATA_742230
113 select ARM_ERRATA_751472
114 select TEGRA_ARMV7_COMMON
117 bool "Tegra30 family"
118 select ARM_ERRATA_743622
119 select ARM_ERRATA_751472
120 select TEGRA_ARMV7_COMMON
123 bool "Tegra114 family"
124 select TEGRA_ARMV7_COMMON
127 bool "Tegra124 family"
128 select TEGRA_ARMV7_COMMON
133 bool "Tegra210 family"
136 select TEGRA_ARMV8_COMMON
139 select TEGRA_GP_PADCTRL
144 select TEGRA_PMC_SECURE
148 bool "Tegra186 family"
152 select TEGRA186_CLOCK
154 select TEGRA186_RESET
155 select TEGRA_ARMV8_COMMON
161 config TEGRA_DISCONNECT_UDC_ON_BOOT
162 bool "Disconnect USB device mode controller on boot"
166 When loading U-Boot into RAM over USB protocols using tools such as
167 tegrarcm or L4T's exec-uboot.sh/tegraflash.py, Tegra's USB device
168 mode controller is initialized and enumerated by the host PC running
169 the tool. Unfortunately, these tools do not shut down the USB
170 controller before executing the downloaded code, and so the host PC
171 does not "de-enumerate" the USB device. This option shuts down the
172 USB controller when U-Boot boots to avoid leaving a stale USB device
175 config CI_UDC_HAS_HOSTPC
177 depends on CI_UDC && !TEGRA20
179 config SYS_MALLOC_F_LEN
182 source "arch/arm/mach-tegra/tegra20/Kconfig"
183 source "arch/arm/mach-tegra/tegra30/Kconfig"
184 source "arch/arm/mach-tegra/tegra114/Kconfig"
185 source "arch/arm/mach-tegra/tegra124/Kconfig"
186 source "arch/arm/mach-tegra/tegra210/Kconfig"
187 source "arch/arm/mach-tegra/tegra186/Kconfig"
191 depends on TEGRA20_SFLASH || TEGRA20_SLINK || TEGRA114_SPI
194 prompt "UART to use for console"
195 depends on TEGRA_PINCTRL
196 default TEGRA_ENABLE_UARTA
198 config TEGRA_ENABLE_UARTA
201 config TEGRA_ENABLE_UARTB
204 config TEGRA_ENABLE_UARTC
207 config TEGRA_ENABLE_UARTD
213 bool "Enable setting up the GPU"
214 depends on TEGRA124 || TEGRA210
217 bool "Enable 'enterrcm' command"
220 Tegra's boot ROM supports a mode whereby code may be downloaded and
221 flash-programmed over a USB connection. On dev boards, this is
222 typically entered by holding down a "force recovery" button and
223 resetting the CPU. However, not all boards have such a button (one
224 example is the Compulab Trimslice), so a method to enter RCM from
227 Even on boards other than Trimslice, controlling this over a UART
228 may be useful, e.g. to allow simple remote control without the need
229 for mechanical button actuators, or hooking up relays/... to the
233 bool "Enable 'ebtupdate' command"
234 depends on TEGRA20 || TEGRA30
237 Updating u-boot from within u-boot in rather complex or even
238 impossible on production devices. To make it easier procedure of
239 re-cryption was created. If your device was re-crypted choose Y.