Skip to content
  • Philipp Tomsich's avatar
    defconfig: puma-rk3399: add defconfig for the RK3399-Q7 (Puma) · 0b3ce83d
    Philipp Tomsich authored and Simon Glass's avatar Simon Glass committed
    
    
    This commit adds the baseline defconfig for the RK3399-Q7 (Puma) SoM
    (under the name 'puma-rk3399_defconfig') featuring the Rockchip RK3399
    in a Qseven compatible module.
    
    This subsumes the following changes:
     * defconfig: rk3399: migrate CONFIG_SPL_LIBCOMMON_SUPPORT/CONFIG_SPL_LIBGENERIC_SUPPORT
     * defconfig: rk3399-puma: add CONFIG_MMC_DW_ROCKCHIP
     * defconfig: rk3399-puma: disable CONFIG_SPL_OF_PLATDATA
     * defconfig: rk3399-puma: don't USE_TINY_PRINTF
     * defconfig: rk3399-puma: set up CONFIG_SYS_BOARD for the RK3399-Q7
     * defconfig: rk3399-puma: enable the multi-image loading via CONFIG_SPL_FIT
     * defconfig: rk3399-puma: SPL should be able to boot from MMC/SD card
     * defconfig: rk3399-puma: enable GMAC support
     * defconfig: rk3399-puma: enable support for SPI and Winbond SPI flash
     * defconfig: rk3399-puma: enable SPI as a boot-source in SPL
     * defconfig: rk3399-puma: disallow non-FIT images from being loaded
     * defconfig: rk3399-puma: rename to puma-rk3399
     * rockchip: config: rk3399: update defconfigs and rk3399_common
    
    For the RK3399-Q7, we want a default boot-order of SPI -> MMC -> uSD.
    This both follows how the BootROM probes devices and is a sane default
    for customers in device-personalisation (e.g. it allows for quick and
    easy factory programming of unpersonalised devices using an SD card)
    and field usage (with customer devices expected to have their firmware
    either in SPI or MMC).
    
    However, when probing multiple interfaces (according to the result
    from the board_boot_order function), we need to ensure that only valid
    FIT images are considered and disable the fallback to assuming that a
    raw (binary-only) U-Boot image is loaded (to avoid hangs/crashes from
    jumping to random content loaded from devices that are probed, but
    don't contain valid image content).
    
    By disabling the SPL_RAW_IMAGE_SUPPORT and SPL_LEGACY_IMAGE_SUPPORT
    options, we ensure that raw images (indistinguishable from random
    data) are not considered for booting.
    
    Signed-off-by: Philipp Tomsich's avatarPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
    Acked-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    Drop CONFIG_DEBUG_UART_BOARD_INIT:
    Signed-off-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    0b3ce83d