When someone attempts to bring up a custom board using TI SoCs (am62x in this case), it often takes several days for someone to reduce the current configuration from the TI EVM/SK boards to a configuration that works for their board.
The goal of these changes is to allow for a minimal boot configuration to exist within UBoot that someone can access directly in order to test their boards for a sign of life before beginning development. This is all done with the hope to increase ease of use and reduce the upbringing process from several days to a few hours.
With the use of fragments, the base defconfigs reside in configs/ and the config fragments reside in board/../
There is still quite a lot of board specific code inside board_init_f() that will need attention later, however this series begins the process of splitting the am62x's configs into a separate generic defconfig everyone can use for new board wakeups with individual board/ti/*.config fragments for each board varient.
Jason Kacines (3): scripts: kconfig: Add config fragment support in board/../ configs: Add am62x wakeup defconfigs board: ti: am62x: Add am62x_evm defconfig fragments
board/ti/am62x/am62x_evm_a53.config | 38 +++++++++++++ board/ti/am62x/am62x_evm_r5.config | 51 ++++++++++++++++++ ..._evm_a53_defconfig => am62x_a53_defconfig} | 34 ++---------- ...2x_evm_r5_defconfig => am62x_r5_defconfig} | 53 ++++--------------- scripts/kconfig/Makefile | 4 +- 5 files changed, 106 insertions(+), 74 deletions(-) create mode 100644 board/ti/am62x/am62x_evm_a53.config create mode 100644 board/ti/am62x/am62x_evm_r5.config rename configs/{am62x_evm_a53_defconfig => am62x_a53_defconfig} (72%) rename configs/{am62x_evm_r5_defconfig => am62x_r5_defconfig} (66%)