This patch includes common config_distro_defaults.h and
config_distro_bootcmd.h for u-boot enviroments to support distro boot
which automatically scan boot.scr from storage devices(e.g.
SD/USB/SATA/SCSI disk) and execute autoboot script on LS1021ATWR board.
Signed-off-by: NShengzhou Liu <Shengzhou.Liu@nxp.com>
Signed-off-by: NAlison Wang <alison.wang@nxp.com>
Reviewed-by: NYork Sun <york.sun@nxp.com>

This adds myself as one of the x86 maintainers.
Signed-off-by: NBin Meng <bmeng.cn@gmail.com>

In the source_file_format.txt file we talk about how to construct a
valid FIT image.  While it already says to look at the source for the
full list, add kernel_noload to the explicit list of types.  This is
arguably the most important type to use as most often we are including a
kernel that will run from wherever it is loaded into memory and execute.

This for example, allows you to create a single FIT image for Linux that
can be used on both OMAP and i.MX devices as the kernel will not need to
be moved in memory.
Signed-off-by: NTom Rini <trini@konsulko.com>

STM32F7 and H7 shared the same SDRAM control block.
On STM32H7 few control bits has been added.
The current driver need some minor adaptation as FMC block
enable/disable for H7.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>

FMC driver is now able to discover the bank number by
parsing bank subnodes.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

FMC is able to manage 2 SDRAM banks, but the current driver
implementation is only able to manage the first SDRAM bank.

Even if only bank2 is used, some bank1 registers must be
configured.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Replace all fdtdec_get..() calls by ofnode_read...() or dev_read..().
This will allow drivers to support a live device tree.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Retrieve RAM base address from DT instead of using STM32_SDRAM_FMC

For STM32F7, FMC block base address is 0xA0000000, but SDRAM
registers are located at offset 0x140 inside FMC block.
Update the stm32_fmc_regs fields with all FMC registers
to map SDRAM registers at the right address.

These additionals registers will be used later.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>

Migrate all FMC defines from arch/arm/include/asm/arch-stm32f7/fmc.h
to drivers/ram/stm32_sdram.c

This will avoid to add an additionnal arch-stm32xx/fmc.h file when
a new stm32 family soc will be introduced.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Reviewed-by: NVikas Manocha <vikas.manocha@st.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

All drivers which was using clock_get() are now using
clk_get_rate() from clock framework, now it's safe to
remove clock_get().
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

Replace proprietary clock_get() by clk_get_rate()
The stm32_qspi is now "generic" and can be used
by other STM32 SoCs.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

Replace proprietary clock_get() by clk_get_rate()
The stm32x7 serial driver is now "generic" and can be used
by other STM32 SoCs.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

This allow to remove include/dm/platform_data/serial_stm32x7.h
which was included in the past by stm32x7 driver and by
stm32f746-disco.c board file.
Since patch 42bf5e7c "serial: stm32f7: add device tree support"
this file is no more needed in board file.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

clean the code by removing unused enums, structs and
defines related to clocks
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

Add clock framework .get_rate callback.
This step will allow to convert all drivers which was using
proprietary clock_get() to use clock framework .get_rate().
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

Retrieve RCC base address from DT, this will prepare
the ground for future STM32 SoCs support.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

Also remove its declaration from stm32.h which
is no more needed.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

Use the same clocks macro than the one used by kernel DT.
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>
Acked-by: NVikas MANOCHA <vikas.manocha@st.com>

The inline assembly functions in mon.c assume that the caller will
check for the return value in r0 according to regular ARM calling
conventions.

However, this assumption breaks down if the compiler inlines the
functions. The caller is then under no obligation to use r0 for the
result.

To fix this disconnect, we must explicitly move the return value
from the smc/bl call to the variable that the function returns.
Signed-off-by: NMadan Srinivas <madans@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

The load address of ramdisk, rdaddr is 0x88080000 and fit_loadaddr
is defined as 0x88000000. This leaves only 512Kbytes for the
fit image. When the FIT images are larger than this, it will
overwite the ramdisk and cause the boot to fail.

For eg, The K2 HS fit images are a few MB and end up overwriting
the ramdsk. This patch moves the fit_loadaddr to 0x87000000,
leaving a 16MB window for the fit image. This memory can be
reclaimed once the kernel starts running.
Signed-off-by: NMadan Srinivas <madans@ti.com>

On early K2 devices (eg. K2HK) the secure ROM code does not support
loading secure code to firewall protected memory, before decrypting,
authenticating and executing it.

To load the boot monitor on these devices, it is necessary to first
authenticate and run a copy loop from non-secure memory that copies
the boot monitor behind firewall protected memory, before decrypting
and executing it.

On K2G, the secure ROM does not allow secure code executing from
unprotected memory. Further, ROM first copies the signed and encrypted
image into firewall protected memory, then decrypts, authenticates
and executes it.

As a result of this, we cannot use the copy loop for K2G. The
mon_install has to be modified to pass the address the signed and
encrypted secure boot monitor image to the authentication API.

For backward compatibility with other K2 devices and K2G GP,
the mon_install API still supports a single argument. In this case
the second argument is set to 0 by u-boot and is ignored by ROM
Signed-off-by: NThanh Tran <thanh-tran@ti.com>
Signed-off-by: NMadan Srinivas <madans@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

We first split the CONFIG_BOOTCOMMAND into its components to improve
readability. We then make the following order changes:

 - Run findfdt first so the fdt name can be used in envboot like OMAP
 - Install the boot monitor before running the PMMC so we can make any
     needed secure changes before PMMC, do this on both HS and non-HS
 - Move set_name_pmmc to just before get_pmmc_${boot}
Signed-off-by: NAndrew F. Davis <afd@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

Updates the default u-boot environment variables to support secure
boot. On secure devices, a secure boot monitor (sec-bm) needs to
be installed by u-boot.
Signed-off-by: NMadan Srinivas <madans@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

Updates the default u-boot environment variables to support FIT image
loading.
Signed-off-by: NAndrew F. Davis <afd@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

BeagleBoard X15 revC board is similar to X15 revB1 except
with a SR2.0 where revB1 uses a SR1.1. Add board detection
support for revC.
Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

board_is*("rev", board_ti_get_rev()) uses strncmp() for
revison detection and assumes it is success if return value
is <= 0. This will fail in case of multiple versions, as
revb will be true for board_is_*revb() and board_is_*reva().
Fix it by looking for exact match of the string.
Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

GPIOs are now supported on Meson GXBB, enable driver and command in
the config.
Signed-off-by: NBeniamino Galvani <b.galvani@gmail.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

This commit adds GPIO support to the Amlogic Meson pin controller
driver, based on code from Linux kernel.
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NBeniamino Galvani <b.galvani@gmail.com>

Import Amlogic Meson DTS files from Linux kernel version 4.12
Signed-off-by: NBeniamino Galvani <b.galvani@gmail.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Enable file system commands such as load, ls.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

As is often the case with SoC development, slightly different
products (i.e. different part number) are developed based on the
same silicon-die.  Such fine grained information is unmaintainable.

Also, "SoC:" is a better fit that "CPU:".
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Rework the readme to reflect the latest boot mechanism on ARMv8 SoCs.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

It has been a while since ARM Trusted Firmware supported UniPhier SoC
family.  U-Boot SPL was intended as a temporary loader that runs in
secure world.  It is a maintenance headache to support two different
boot mechanisms.  Secure firmware is realm of ARM Trusted Firmware
and now U-Boot only serves as a non-secure boot loader for UniPhier
ARMv8 SoCs.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

This converts the following to Kconfig:
   CONFIG_ENV_IS_IN_ONENAND
Signed-off-by: NSimon Glass <sjg@chromium.org>

This converts the following to Kconfig:
   CONFIG_ENV_IS_IN_FAT
Signed-off-by: NSimon Glass <sjg@chromium.org>

This converts the following to Kconfig:
   CONFIG_ENV_IS_IN_REMOTE
Signed-off-by: NSimon Glass <sjg@chromium.org>

This converts the following to Kconfig:
   CONFIG_ENV_IS_IN_SPI_FLASH
Signed-off-by: NSimon Glass <sjg@chromium.org>

This converts the following to Kconfig:
   CONFIG_ENV_IS_IN_DATAFLASH
Signed-off-by: NSimon Glass <sjg@chromium.org>