ARM: i.MX: phytec-som-imx6: Fix paths to SPI-NOR partition ...

Due to a previously change of the partition namings, the kernel- and
oftree-paths in the SPI-bootscript have to be adapted to the changes.

The previous change can be found here:
commit 72ba815

Signed-off-by: Yunus Bas <y.bas@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-next/stm32'

Merge branch 'for-next/misc'

Merge branch 'for-next/mips'

Merge branch 'for-next/imx'

Merge branch 'for-next/at91'

ARM: at91: add sama5d27-based Groboards Giant Board support ...

The Groboards Giant Board is a ATSAMA5D27C-D1G SiP-based SBC.
The board features a 500MHz ARM Cortex-A5 and 128MB DDR2 SDRAM in the
SiP as well as a MicroSD slot on the PCB.

barebox doesn't yet support the sama5d2 SDHCI-variant, so board support
is limited to toggling the LED and interfacing with the UART, but add
this now till the rest may follow. Device tree is based on the vendor's
device-tree available at https://github.com/Groboards/giantboard-tools

Acked-by: Sam Ravnborg <sam@ravnborg.org>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: at91: sama5d27-som1: branch to noinline function after stack setup ...

We need to branch out as soon as possible after setting up the stack.
Do this and thereby avoid an access violation we now run into using
OSELAS.Toolchain-2019.09.1.

Fixes: 8bfb1852cf6a ("ARM: at91: add basic sama5d2-som1-ek1 support")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: at91: sama5d27-som1: clean up lowlevel.c ...

In ARM, stack decrements before storing values, so decrementing a number
from the stack base is unnecessary. Existing instances of this were
removed in 6b3dc4abd8 ("ARM: Cleanup stack offset cargo cult"), but the
sama5d27-som1 board was added later than that. Fix the cargo cult here
as well and while at it, turn a macro that doesn't need to be one
into a static inline function.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: at91: add support for SAM9 SoC reset ...

System reset wasn't supported on the sama5 so far.
Add a driver to remedy this.

Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: phytec-som-imx6: Add imx6dl with 512mb RAM ...

This patch adds support for a phyCORE-i.MX 6Solo/DualLight variant with
512mb RAM.

Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
Signed-off-by: Stefan Riedmüller <s.riedmueller@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

kbuild: rename barebox-{common, lds} to BAREBOX_{OBJS, LDS} ...

The previous commit renamed barebox-pbl-common because you cannot
export a variable that contain hyphens.

These variables are not exported for now. I am just renaming them for
consistency.

  barebox-common -> BAREBOX_OBJS
  barebox-lds    -> BAREBOX_LDS

If barebox moves the link rules into scripts/link-barebox.sh like
Linux did, these two must be exported anyway.

Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

kbuild: rename barebox-pbl-common to BAREBOX_PBL_OBJS ...

'export barebox-pbl-common' does not work reliably because hyphens
are disallowed in shell variables.

This caused a problem in Linux in the past. See Linux commit 2bfbe7881ee0
("kbuild: Do not use hyphen in exported variable name").

The same problem occurs when you build barebox with O= and the directory
path to the source tree contains a shell special character like '~'.

The maintainer of GNU Make stated that there is no consistent way to
export variables that do not meet the shell's naming criteria.
(https://savannah.gnu.org/bugs/?55719)

Consequently, you cannot use hyphens in exported variables.

Rename barebox-pbl-common to BAREBOX_PBL_OBJS.

I named it after KBUILD_VMLINUX_OBJS in the Linux top Makefile.

Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: dts: advantech-rom-7421: Add ocotp node to provide mac address ...

This patch adds an ocotp node to provide barebox with a mac address
for Advantech ROM-7421.

Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: dts: advantech-rom-7421: fix sd-card cd pin ...

Enable possibility to auto detect sd-card insertion on Advantech
ROM-7421, this patch sets a necessary gpio to active-low.

Signed-off-by: Christoph Fritz <chf.fritz@googlemail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: dts: phycore-imx6: change mtd-partition names for compatibility with kernel ...

The NVMEM-subsystem in newer kernels does not allow identical partition
names on different subdevices. According to the recommendation, we have to
rename the partition names to be compatible with actual kernel
versions.

To minimize the problems which could possibly arise, the nand device is
not changed. For all other devices, we prepend the device name to the
partitions.

Signed-off-by: Yunus Bas <y.bas@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: dts: Add missing #size/address-cells properties ...

Some boards lack the #address-cells/#size-cells properties for the i.MX6
GPMI nand controller. Add them.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

arm: vf610-zii-scu4-aib: Remove non effective properties ...

The vf610-zii-scu4-aib dts contains a fixup for nodes which do not
exist anymore, so instead of fixing up the nodes new ones are created
which is surely not intentional.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>

arm: dts: Fix node names ...

- Remove leading zeroes from the addresses in the node names of i2c/spi
  devices
- Remove leading 0x from the addresses in the node names of i2c/spi
  devices
- Add missing reg address in node names.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM64: add support for booting a FIT image ...

Add the image type handler to the ARM64 boot code. The only difference
in the boot handling is that we need to look at the FIT loaded OS image
header to get the image load and text offsets, as the os_header is the
FIT header, not the kernel header.

Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Merge branch 'for-master/imx-external-nand'

ARM: stm32mp: add aliases for mmc1 and mmc2 ...

With the latest update, dts/src/arm/stm32mp151.dtsi now defines the two
other sdmmc nodes as well. Have barebox set aliases for them.

Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: stm32mp: dk2: delete unused includes ...

These includes are no longer needed because we don't need to hard code
memory size in board code anymore for the STM32MP. Drop them.

Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

MIPS: ath79: add support for OpenEmbed SOM9331 board ...

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

gadget: f_fastboot: New Kconfig option USB_GADGET_FASTBOOT_CMD_OEM ...

Most fastboot commands are suitable for a secure boot environment as
they only allow to download/flash/erase to files/partitions which were
explicitly specified in the usbgadget command.

The "oem" group of commands allows execution of arbitrary barebox
commands. This needs to be disabled for secure boot devices.

Signed-off-by: Christian Eggers <ceggers@arri.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

arm: baltos: use compressed DTB images ...

This reduces the size of MLO enough to fit into SRAM.

Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: i.MX: external NAND boot: Fix passing boarddata ...

We used to pass a device tree pointer to
imx*_barebox_boot_nand_external(). This no longer works since we compile
barebox with -fPIE.

The problem is that we only have the first 2KiB of the image available
when we start from NAND. The pointer to the device tree is not valid
yet. This hasn't been a problem because the pointer is only used later
when we have the full image in SDRAM. With -fPIE though the actual
pointer is derived indirectly through another pointer, and that pointer
to the pointer is also not valid which causes an invalid pointer to
the device tree later.

This is solved by splitting the NAND boot functions up into two
functions. With imx*_nand_relocate_to_sdram() the board code relocates
the image out of the NFC SRAM into SDRAM. From that point on the device
tree pointer can be accessed and the board can load the image using
imx*_nand_load_image() and can afterwards pass control to barebox
passing whatever device tee pointer it likes.

Fixes: b0348d677b ("ARM: Compile with -fPIE")
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: i.MX: external NAND boot: Leave icache disabled ...

It seems running from the NFC SRAM doesn't work with the instruction
cache enabled, it leads to corruptions on the i.MX27. We stumbled upon
this earlier and the solution at that time was to disable the
instruction cache in the NAND boot code. It is, however, more reliable
to just not enable the instruction cache in the first place.
This is not particularly nice as we have to ifdef this in generic code,
duplicate arm_cpu_lowlevel_init(), or call arm_cpu_lowlevel_init() later
when we are out of NFC SRAM. From the different bad solutions I chose
to ifdef the instruction cache away. It will be enabled later in the
common cache functions.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

ARM: i.MX: external NAND boot: remove unnecessary arguments from imx*_nand_load_image ...

The imx*_nand_load_image functions all take dest, size, nfc_base and
pagesize_2k arguments. All of these can be determined inside the functions,
so remove them.

Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

reset_source: migrate from reset_source_name to reset_source_to_string ...

Whether reset_source_name() returns the just set reset_source is
dependent on probe order and the priorities of prior reset sources
in relation to the current one. Make this more robust by using the new
reset_source_to_string.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>