The bootefi command gets a few addresses as values passed in. In sandbox,
these values are in U-Boot address space, so we need to make sure we
explicitly call map_sysmem() on them to be able to access them.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NAlexander Graf <agraf@suse.de>

The EFI image loader tries to determine which target architecture we're
working with to only load PE binaries that match.

So far this has worked based on CONFIG defines, because the target CPU
was always indicated by a config define. With sandbox however, this is
not longer true as all sandbox targets only encompass a single CONFIG
option and so we need to use compiler defines to determine the CPU
architecture.
Signed-off-by: NAlexander Graf <agraf@suse.de>

This reverts commit c524997a.

Booting ARMv7 in non-secure mode using bootefi works now.
Signed-off-by: NMark Kettenis <kettenis@openbsd.org>
Signed-off-by: NAlexander Graf <agraf@suse.de>

ARMV7_LPAE is required in order to enable the MMU in HYP mode.
And we really want to enable the MMU in HYP mode such that we can
enable the the caches.  Otherwise U-Boot code (such as the EFI
implementation) that runs in HYP mode will run at a snils pace.
Signed-off-by: NMark Kettenis <kettenis@openbsd.org>
Signed-off-by: NAlexander Graf <agraf@suse.de>

Multiple EFI binaries may be executed in sequence.  So if we already
are in non-secure mode after running the first one we should skip
the switching code since it no longer works once we're non-secure.
Signed-off-by: NMark Kettenis <kettenis@openbsd.org>
Signed-off-by: NAlexander Graf <agraf@suse.de>

If desired (and possible) switch into HYP mode or non-secure SVC mode
before calling the entry point of an EFI application.  This allows
U-Boot to provide a usable PSCI implementation and makes it possible
to boot kernels into hypervisor mode using an EFI bootloader.

Based on diffs from Heinrich Schuchardt and Alexander Graf.
Signed-off-by: NMark Kettenis <kettenis@openbsd.org>
[agraf: Fix indentation]
Signed-off-by: NAlexander Graf <agraf@suse.de>

The current code that switches into HYP mode doesn't bother to set
up a stack for HYP mode.  This doesn't work for EFI applications
as they expect a usable stack.  Fix this by migrating the stack
pointer from SP_svc to SP_hyp while in Monitor mode.
This restores the stack pointer when we drop into HYP mode.
Signed-off-by: NMark Kettenis <kettenis@openbsd.org>
Signed-off-by: NAlexander Graf <agraf@suse.de>

The following generated files should be ignored by git:
efi_miniapp_file_image_exit.h
efi_miniapp_file_image_return.h

*.so files are normally deleted during the build but should be
ignored too.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: NAlexander Graf <agraf@suse.de>

Our nand_ecc_modes_t is already a bit abused by value NAND_ECC_SOFT_BCH.
This enum should store ECC mode only and putting algorithm details there
is a bad idea. It would result in too many values impossible to support
in a sane way.

To solve this problem let's add a new enum. We'll have to modify all
drivers to set it properly but once it's done it'll be possible to drop
NAND_ECC_SOFT_BCH. That will result in a cleaner design and more
possibilities like setting ECC algorithm for hardware ECC mode.
Signed-off-by: NRafał Miłecki <zajec5@gmail.com>
Signed-off-by: NBoris Brezillon <boris.brezillon@free-electrons.com>
[Linux commit: b0fcd8ab7b3c89b5da7fff5224d06ed73e7a33cc]
[Philippe Reynes: adapt code to u-boot]
Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>

Only the MUSB driver is currently supported on the omap3_logic
boards.  The driver is using the new-musb and not the legacy
version, so this patch removes the dead code references.
Signed-off-by: NAdam Ford <aford173@gmail.com>

This converts the following to Kconfig:
   CONFIG_DA8XX_GPIO
Signed-off-by: NAdam Ford <aford173@gmail.com>

In order to use the device tree for MMC, the card-detect pin
needs to be inverted.  This patch places this into the
am3517-evm-u-boot.dtsi file to keep the main DTS and DTSI files
clean and in-sync with Linux
Signed-off-by: NAdam Ford <aford173@gmail.com>

With the resync of the omap3.dtsi file, the reg-shift was removed
so it breaks the UART.  Adding the reg-shift into the
am3517-evm-u-boot.dtsi keeps the reg-shift for U-Boot, but keeps
the dts/dtsi files clean from Linux.
Signed-off-by: NAdam Ford <aford173@gmail.com>

The Linux kernel moved to sphinx-based documentation and got rid of the
DocBook based documentation quite a while ago. Hence, the DocBook
documentation for U-Boot should be converted as well.

To achieve this, import the necessary files from Linux v4.17, and
convert the current DocBook documentation (three files altogether) to
sphinx/reStructuredText.

For now, all old DocBook documentation was merged into a single
handbook, tentatively named "U-Boot Hacker Manual".

For some source files, the documentation style was changed to comply
with kernel-doc; no functional changes were applied.
Signed-off-by: NMario Six <mario.six@gdsys.cc>

There have been some significant changes to the DM37 SOM-LV device
tree.  This patch re-syncs it with Linux.
Signed-off-by: NAdam Ford <aford173@gmail.com>

There have been some refactoring of the DTS files for the Logic PD
DM37 Torpedo.  This patch re-sync's the DTS files with Linux
Signed-off-by: NAdam Ford <aford173@gmail.com>

There have been several minor changes to the OMAP3.dtsi, so this
patch re-syncs it with Linux.  An addition include/dt-binding was
also brought with it.
Signed-off-by: NAdam Ford <aford173@gmail.com>

Several changes have been made to the AM3517-evm and the underlying
am3517.dtsi file.  This patch re-sync's the DTS and DTSI files with
Linux.
Signed-off-by: NAdam Ford <aford173@gmail.com>

The m5253evbe board has been marked as orphan since June of 2014 and
should have been dropped a while ago.  Do so now.
Signed-off-by: NTom Rini <trini@konsulko.com>

This patch solves quad read issue with Macronix/Micron spi nor.
Signed-off-by: NChristophe Kerello <christophe.kerello@st.com>
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>

This patch assigns the functional operation mode in _stm32_qspi_gen_ccr
function.
Signed-off-by: NChristophe Kerello <christophe.kerello@st.com>
Signed-off-by: NPatrice Chotard <patrice.chotard@st.com>

Assigning a parameter which is not used afterwards has not effect.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: NSimon Glass <sjg@chromium.org>

trini: Update colibri-imx6ull to use Kconfig for mtdparts related
options.
Signed-off-by: NTom Rini <trini@konsulko.com>

There are already definitions for ramdisk_addr_r and fdt_addr_r, so
having a duplicate copy called ramdiskaddr and fdtaddr is confusing.
This patch converts any references to ramdisk_addr_r and fdt_addr_r
and removes the duplicates.
Signed-off-by: NAdam Ford <aford173@gmail.com>

The USBOH module on imx25 chips contains two USB controllers which are
called USB OTG Controller and USB Host Controller. Each one has its EHCI
root hub. The OTG Controller's EHCI registers start at offset 0, the Host
Controller's registers start at offset 0x400.

We set CONFIG_MXC_USB_PORT=0 to select the OTG Controller and 1 for the
Host Controller. Therefore, IMX_USB_PORT_OFFSET must be 0x400. Using
this setting, the Host Controller starts working on my imx25 board.

Please note that the imx25 reference manual claims that the Host
Controller's registers start at 0x200. This is not correct. The Linux
Kernel uses the correct offset 0x400 in imx25.dtsi.
Signed-off-by: NMartin Kaiser <martin@kaiser.cx>
Reviewed-by: NFabio Estevam <fabio.estevam@nxp.com>

Signing parts of a u-boot imximage for image verification in High
Assurance Boot (HAB) in a post-build process, requires some
information from the imximage header. Currently, this information is
only provided during the image build, which makes the transfer of this
information to the post-build process harder than necessary.

The i.MX HAB information (start and length) can be calculated either
by using information from the image-configuration file, or from the
information in the flash header of the imximage.
The advantage of using information from flash header is, that they are
not only available during image creation, but also available if
existing images are processed.

Example:
$ tools/mkimage -l u-boot.imx
Image Type:   Freescale IMX Boot Image
Image Ver:    2 (i.MX53/6/7 compatible)
Mode:         DCD
Data Size:    483328 Bytes = 472.00 KiB = 0.46 MiB
Load Address: 877ff420
Entry Point:  87800000
HAB Blocks:   0x877ff400 0x00000000 0x00071c00
DCD Blocks:   0x00910000 0x0000002c 0x00000208
Signed-off-by: NHolger Dengler <dengler@linutronix.de>
Tested-by: NBryan O'Donoghue <bryan.odonoghue@linaro.org>

In preparation for delivery bottlenecks, enable support for GigaDevice, Macronix, and Winbond nor flash chips.
Signed-off-by: NLudwig Zenz <lzenz@dh-electronics.de>

Since the vast majority of i.MX6 boards are migrating to SPL,
this patch converts im6q_logic to SPL and enables the SDP for
loading SPL and u-boot.img over USB.  The Falcon mode only
supports NAND flash as of now due to limited space/RAM, but
all i.MX6D/Q SOM's from Logic PD have internal NAND from which
to boot.
Signed-off-by: NAdam Ford <aford173@gmail.com>

Support 1GIB + 2GIB DDR3 with 64bit bus width and 512MIB + 1GIB with 32bit bus width
Signed-off-by: NLudwig Zenz <lzenz@dh-electronics.de>

Preperation for conditional DDR3 initialization based on GPIO codes.
Signed-off-by: NLudwig Zenz <lzenz@dh-electronics.de>

This reverts commit a637fe6f.

The DDR DRAM calibration was enhanced by write leveling correction code.
It can be used with T-topology now.
Signed-off-by: NLudwig Zenz <lzenz@dh-electronics.de>

The new config skips the boot menu which asks which board is in
use. This is useful to allow direct booting of image without user
iteration.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

Our default config already has the secure mode supported, so the
manual step is not required anymore.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

The DFU allows a more user friendly use as the details where the
bootloader is installed are abstracted.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

This enables the "bootaux" command so a firmware can be loaded inside
the M4 MCU.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

This allow the addition of extra default configurations for each
baseboard, removing the boot menu when user boots for the first time.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

The addrmap5 value is the same for the 512MB and 1GB variants,
so there is no need to override it.
Signed-off-by: NFabio Estevam <festevam@gmail.com>
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

Currently the CAAM driver fails to be probed:

caam 30900000.caam: Entropy delay = 3200
caam 30900000.caam: failed to acquire DECO 0
caam 30900000.caam: failed to instantiate RNG

CAAM needs to be initialized in secure world, so enable
CONFIG_ARMV7_BOOT_SEC_DEFAULT to allow the driver to
probe successfully.

Tested with kernel mainline version 4.17.2.
Signed-off-by: NFabio Estevam <festevam@gmail.com>
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

Falcon mode boots the kernel directly from SPL, without loading
the full U-Boot.

As pico-imx7d does not have a GPIO for selecting Falcon versus
normal mode, enter in Falcon mode when the customer selects
the CONFIG_SPL_OS_BOOT option in menuconfig.
Signed-off-by: NFabio Estevam <festevam@gmail.com>
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>

Currently the baseboards do not offer a way to autodetect which one is
in use, so we ask the user if no value has been set.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>