u-boot.git/arch, branch v2016.11-rc1

Merge git://git.denx.de/u-boot-rockchip

2016-10-03T13:09:29Z

ti: omap-common: Allow AM33xx devices to be built securely

2016-10-02T12:10:02Z

Like OMAP54xx and AM43xx family SoCs, AM33xx based SoCs have high security enabled models. Allow AM33xx devices to be built with HS Device Type Support. Signed-off-by: Andrew F. Davis Reviewed-by: Tom Rini Acked-by: Lokesh Vutla

am33xx: config.mk: Fix option used to enable SPI SPL image type

2016-10-02T12:10:00Z

The option SPL_SPI_SUPPORT is used to enable support in SPL for loading images from SPI flash, it should not be used to determine the build type of the SPL image itself. The ability to read images from SPI flash does not imply the SPL will be booted from SPI flash. Unconditionally build SPI flash compatible SPL images. Signed-off-by: Andrew F. Davis Acked-by: Lokesh Vutla Reviewed-by: Tom Rini

am33xx: config.mk: Add support for additional secure boot image types

2016-10-02T12:09:59Z

Depending on the boot media, different images are needed for secure devices. The build generates u-boot*_HS_* files as appropriate for the different boot modes. For AM33xx devices additional image types are needed for various SPL boot modes as the ROM checks for the name of the boot mode in the file it loads. Signed-off-by: Andrew F. Davis Reviewed-by: Tom Rini Acked-by: Lokesh Vutla

Kconfig: Separate AM33XX SOC config from target board config

2016-10-02T12:09:58Z

The config option AM33XX is used in several boards and should be defined as a stand-alone option for this SOC. We break this out from target boards that use this SoC and common headers then enable AM33XX on in all the boards that used these targets to eliminate any functional change with this patch. This is similar to what has already been done in 9de852642cae ("arm: Kconfig: Add support for AM43xx SoC specific Kconfig") and is done for the same reasons. Signed-off-by: Andrew F. Davis Acked-by: Lokesh Vutla Reviewed-by: Tom Rini

ARM: omap5: add fdt secure dram reservation fixup

2016-10-02T12:09:57Z

Adds a secure dram reservation fixup for secure devices, when a region in the emif has been set aside for secure world use. The size is defined by the CONFIG_TI_SECURE_EMIF_TOTAL_REGION_SIZE config option. Signed-off-by: Daniel Allred Reviewed-by: Tom Rini

ARM: DRA7: Add secure emif setup calls

2016-10-02T12:09:56Z

After EMIF DRAM is configured, but before it is used, calls are made on secure devices to reserve any configured memory region needed by the secure world and then to lock the EMIF firewall configuration. If any other firewall configuration needs to be applied, it must happen before the lock call. Signed-off-by: Daniel Allred

arm: omap5: secure API for EMIF memory reservations

2016-10-02T12:09:55Z

Create a few public APIs which rely on secure world ROM/HAL APIs for their implementation. These are intended to be used to reserve a portion of the EMIF memory and configure hardware firewalls around that region to prevent public code from manipulating or interfering with that memory. Signed-off-by: Daniel Allred Reviewed-by: Tom Rini

ti: omap5: Add Kconfig options for secure EMIF reservations

2016-10-02T12:09:51Z

Adds start address and size config options for setting aside a portion of the EMIF memory space for usage by security software (like a secure OS/TEE). There are two sizes, a total size and a protected size. The region is divided into protected (secure) and unprotected (public) regions, that are contiguous and start at the start address given. If the start address is zero, the intention is that the region will be automatically placed at the end of the available external DRAM space. Signed-off-by: Daniel Allred

rockchip: add boot-mode support for rk3288, rk3036

2016-10-02T00:36:55Z

rockchip platform have a protocol to pass the the kernel reboot mode to bootloader by some special registers when system reboot. In bootloader we should read it and take action. We can only setup boot_mode in board_late_init becasue "setenv" need env setuped. So add CONFIG_BOARD_LATE_INIT to common header and use a entry "rk_board_late_init" to replace "board_late_init" in board file. Signed-off-by: Jacob Chen Acked-by: Simon Glass