u-boot/arch/arm/mach-k3/am62x/Kconfig

# SPDX-License-Identifier: GPL-2.0+
#
# Copyright (C) 2023 Texas Instruments Incorporated - https://www.ti.com/
#	Andrew Davis <afd@ti.com>

if SOC_K3_AM625

choice
	prompt "K3 AM62x based boards"
	optional

config TARGET_AM625_A53_EVM
	bool "TI K3 based AM625 EVM running on A53"
	select ARM64
	select BINMAN

config TARGET_AM625_R5_EVM
	bool "TI K3 based AM625 EVM running on R5"
	select CPU_V7R
	select SYS_THUMB_BUILD
	select K3_LOAD_SYSFW
	select RAM
	select SPL_RAM
	select K3_DDRSS
	select BINMAN
	imply SYS_K3_SPL_ATF

config TARGET_VERDIN_AM62_A53
	bool "Toradex Verdin AM62 running on A53"
	select ARM64
	select BINMAN

config TARGET_VERDIN_AM62_R5
	bool "Toradex Verdin AM62 running on R5"
	select CPU_V7R
	select SYS_THUMB_BUILD
	select K3_LOAD_SYSFW
	select RAM
	select SPL_RAM
	select K3_DDRSS
	select BINMAN
	imply SYS_K3_SPL_ATF

endchoice

source "board/beagle/beagleplay/Kconfig"
source "board/ti/am62x/Kconfig"
source "board/toradex/verdin-am62/Kconfig"

endif
arm: mach-k3: am62x: Move board selection to mach-k3 Currently each set of board targets from a vendor is selected inside the board directory for that vendor. This has the problem of multiple targets, one from each vendor, being selectable at the same time. For instance you can select both TARGET_AM654_A53_EVM and TARGET_IOT2050_A53 in the same build. To fix this we need to move the target board choice to a common location for each parent SoC selection. Do this in arch/arm/mach-k3. Signed-off-by: Andrew Davis <afd@ti.com> 2023-11-01 20:35:28 +00:00			`# SPDX-License-Identifier: GPL-2.0+`
			`#`
			`# Copyright (C) 2023 Texas Instruments Incorporated - https://www.ti.com/`
			`# Andrew Davis <afd@ti.com>`

			`if SOC_K3_AM625`

			`choice`
			`prompt "K3 AM62x based boards"`
			`optional`

			`config TARGET_AM625_A53_EVM`
			`bool "TI K3 based AM625 EVM running on A53"`
			`select ARM64`
			`select BINMAN`

			`config TARGET_AM625_R5_EVM`
			`bool "TI K3 based AM625 EVM running on R5"`
			`select CPU_V7R`
			`select SYS_THUMB_BUILD`
			`select K3_LOAD_SYSFW`
			`select RAM`
			`select SPL_RAM`
			`select K3_DDRSS`
			`select BINMAN`
			`imply SYS_K3_SPL_ATF`

			`config TARGET_VERDIN_AM62_A53`
			`bool "Toradex Verdin AM62 running on A53"`
			`select ARM64`
			`select BINMAN`

			`config TARGET_VERDIN_AM62_R5`
			`bool "Toradex Verdin AM62 running on R5"`
			`select CPU_V7R`
			`select SYS_THUMB_BUILD`
			`select K3_LOAD_SYSFW`
			`select RAM`
			`select SPL_RAM`
			`select K3_DDRSS`
			`select BINMAN`
			`imply SYS_K3_SPL_ATF`

			`endchoice`

board: Move beagleplay under beagle vendor folder Move beagleplay support away from ti/am62x to it's own beagle vendor folder. This forms the starting point for new beagle platforms added under it's own board vendor folder. As part of this create all the associated files with a bare minimum beagleplay.c file. Suggested-by: Andrew Davis <afd@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com> Reviewed-by: Bryan Brattlof <bb@ti.com> [trini: Update k3-binman.dtsi to use full path to scheme.yaml now] Signed-off-by: Tom Rini <trini@konsulko.com> 2023-11-04 08:01:35 +00:00			`source "board/beagle/beagleplay/Kconfig"`
arm: mach-k3: am62x: Move board selection to mach-k3 Currently each set of board targets from a vendor is selected inside the board directory for that vendor. This has the problem of multiple targets, one from each vendor, being selectable at the same time. For instance you can select both TARGET_AM654_A53_EVM and TARGET_IOT2050_A53 in the same build. To fix this we need to move the target board choice to a common location for each parent SoC selection. Do this in arch/arm/mach-k3. Signed-off-by: Andrew Davis <afd@ti.com> 2023-11-01 20:35:28 +00:00			`source "board/ti/am62x/Kconfig"`
			`source "board/toradex/verdin-am62/Kconfig"`

			`endif`