u-boot.git/common/spl/Kconfig, branch v2020.04

sunxi: move CONFIG_SYS_SPI_U_BOOT_OFFS out of defconfig

2020-01-24T17:36:56Z

For Allwinner SoCs the CONFIG_SYS_SPI_U_BOOT_OFFS value is not really a board choice: The boot ROM only loads the SPL from offset 0 of the SPI NOR flash, and loads at most 32KB. This is a similar situation as on MMC, so consequently we create our "joint" image (SPL + U-Boot proper) with that 32KB offset during the build. So define the value of this symbol to be 32KB by default for every Allwinner SoC. This removes the definition of this symbol from the _defconfig files, and avoids every board to define this over and over again. Signed-off-by: Andre Przywara Reviewed-by: Jagan Teki

Merge https://gitlab.denx.de/u-boot/custodians/u-boot-marvell

2020-01-16T17:52:07Z

- Clearfog: Fix SD booting (Baruch) - Misc updates to MMC handling in SPL to support booting from main data partition (vs hardware boot partition) on MVEBU (Baruch)

spl: mmc: support uboot image offset on main partition

2020-01-16T09:58:52Z

On Armada 38x platforms the ROM code loads SPL from offset 0 of eMMC hardware boot partitions. When there are no boot partitions (i.e. SD card) the ROM skips the first sector that usually contains the (logical) partition table. Since the generated .kwb image contains the main U-Boot image in a fixed location (0x140 sectors by default), we end up with the main U-Boot image in offset of 1 sector. The current workaround is to manually set CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR to 0x141 to compensate for that. This patch uses the run-time detected boot partition to determine the right offset of the main U-Boot partition. The generated .kwb image is now compatible with both eMMC boot partition, and SD card main data partition. Signed-off-by: Baruch Siach Reviewed-by: Stefan Roese Signed-off-by: Stefan Roese

Kconfig: Rename CONFIG_SPL_DMA_SUPPORT to CONFIG_SPL_DMA

2020-01-16T00:50:27Z

Rename CONFIG_SPL_DMA_SUPPORT to CONFIG_SPL_DMA. This allows to use macros such as CONFIG_IS_ENABLED() that allow conditional compilation of code for SPL and U-Boot. Signed-off-by: Vignesh Raghavendra Reviewed-by: Simon Glass

spl: Allow cache drivers to be used in SPL

2020-01-07T13:38:33Z

Add an option for building cache drivers in SPL. Signed-off-by: Ley Foon Tan Reviewed-by: Tom Rini Reviewed-by: Simon Goldschmidt

configs: Enable SPL_FSL_PBL for some LayerScape platforms

2019-12-26T10:30:20Z

In commit , SPL_FSL_PBL is removed from the configs of some LayerScape platforms. Actually, SPL_FSL_PBL is needed for SD/NAND boot on LS1021A/LS1043A/LS1046A to create boot binary having SPL binary in PBI format concatenated with u-boot binary. SPL_FRAMEWORK is used on these platforms too. Signed-off-by: Alison Wang Reviewed-by: Priyanka Jain

spl: cache: Allow cache drivers in SPL

2019-12-10T00:23:10Z

When ax25-ae350 try to enable v5l2 cache driver in SPL configuration, it need this option for cache support in SPL. Signed-off-by: Rick Chen Cc: KC Lin Cc: Alan Kao

spl: Introduce SPL_DM_GPIO Kconfig define

2019-12-05T15:28:38Z

This define indicates if DM_GPIO shall be supported in SPL. This allows proper operation of DM converted GPIO drivers in SPL, which use boards. Signed-off-by: Lukasz Majewski

cosmetic: Fix spelling and whitespace errors

2019-12-03T13:43:23Z

Signed-off-by: Thomas Hebb

spl: separate SPL_FRAMEWORK config for spl and tpl

2019-11-17T09:22:53Z

Right now enabling SPL_FRAMEWORK will also enable it for the TPL in all cases, making the TPL bigger. There may be cases where the TPL is really size constrained due to its underlying ram size. Therefore introduce a new TPL_FRAMEWORK option and make the relevant conditionals check for both. The default is set to "y if SPL_FRAMEWORK" to mimic the previous behaviour where the TPL would always get the SPL framework if it was enabled in SPL. Signed-off-by: Heiko Stuebner Reviewed-by: Kever Yang