Merge branch 'for-next/mips'

Merge branch 'for-next/kvx'

Merge branch 'for-next/kbuild'

Merge branch 'for-next/imx'

Merge branch 'for-next/fastboot'

Merge branch 'for-next/elf'

Merge branch 'for-next/dts-phandles'

Merge branch 'for-next/dts'

Merge branch 'for-next/at91'

Release v2020.07.0 ...

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

ARM: at91: dts: sama5d27-som1: adapt to upstream partition layout ...

Linux v5.8-rc1 adds partitions to the flash@0 node, which now overlap
with the partitions we define and resulting in errors:

  ERROR: m25p0.barebox: New partition m25p0.barebox conflicts
	with m25p0.at91bootstrap
  ERROR: m25p0.barebox-environment: New partition
  	m25p0.barebox-environment conflicts with m25p0.bootloader

We don't want to reuse those partitions as their name may and probably
will change (they have leading zeroes in the unit address).
We could use the &{/path/to/partition} syntax, but that might be broken
soon as well, as the nodes aren't inside a partitions node with a
"fixed-partitions" compatible.
The busses also don't align with the yaml schema and might be renamed.

Nuke the full flash@0 node and supply ours and avoid these problems.
The offsets of the partitions have been adjusted to coincide with the
upstream offsets for second stage bootloader and environment.

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

ARM: at91: sama5d27-giantboard: add default environment/bbu ...

The board only has SD-Card as storage. Add a barebox update handler to
flash barebox to it, as well as an nv.boot.default=mmc1 to boot from it.

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

ARM: at91: sama5d27-giantboard: add additional first stage entry point ...

The BootROM constrains us to a 64K big first stage bootloader. Add a PBL
entry point for a xload barebox that sets up the minimum necessary to
load a FAT32 barebox.bin from the SD-Card.

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

ARM: at91: sama5d27-som1-ek: add barebox_update and multi environment support ...

We now have second stage support for running from sdmmc0 and sdmmc1.
Add a barebox environment and update handler for the two SD cards.

As fall back, we use the environment in the QSPI flash as before as this
is soldered to the SoM and is always available.

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

ARM: at91: sama5d2: populate $bootsource and $bootsource_instance ...

The BootROM passes us information about the boot medium in r4 and we
already use that in first stage and pass it along to second stage
PBL already. To make use of it, we need to pass it to barebox proper, do
this by writing it in the last 4 bytes of the SRAM. As second stage
always run in DRAM, this is safe to do.

We could also write to SRAM directly from first stage, but at91bootstrap
passes info in r4 as well for the sama5d3 boards, so we do it likewise
to maintain compatibility.

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

ARM: at91: sama5d2: read back memory size from DDRAM controller ...

We hard code memory size at three places:
 - In the configuration we use to initialize the DDRAM controller
 - In the minimal available size passed from PBL to barebox proper
 - In the device tree memory node override

Remove the two latter ones and replace them with code that reads the
size back from controller.

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

scripts: imx-image: throw descriptive error on encountering dcdofs ...

With dcdofs renamed to ivtofs, out-of-tree boards will start to fail.
Make the migration easier by suggesting what needs to be changed on
stderr.

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

arm: boards: add initial imx8mp-evk support ...

This adds support for the NXP i.MX8MP-EVK board.

The SDRAM timings are taken from U-Boot-2020.07-rc4, other information
how to initialize the board are form U-Boot as well.

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

ARM: i.MX8MP: Add ocotp support ...

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

ARM: i.MX: bbu: Fix IVT offset for i.MX8MP ...

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

net: phy: realtek: handle RX delay setting ...

RX delay and TX delay can be configured independently on the RTL8211F.
Decode the phy mode setting and set both bits accordingly. This is based
on Linux commit 1b3047b5208a ("net: phy: realtek: add support for
configuring the RX delay on RTL8211F")

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

mci: imx-esdhc-pbl: Add imx8mp_esdhc_load_image() for i.MX8MP ...

The image format of the i.MX8MP is different from i.MX8M, so add its own
image loading function for it.

Older i.MX SoCs had a IVT Offset (the offset from the start of the image
to the actual data) of 1KiB. This was done to leave space for the
partition table at the beginning of the device. To support GPT SoCs
starting with i.MX8M an additional gap of 32KiB was added, so that the
actual image started at offset 33KiB. Now starting with i.MX8MP the now
superfluous 1KiB offset was removed do that the actual image now starts
at 32KiB.
Unfortunately the 1KiB offset is woven into the offsets of the IVT
whereas the 32KiB are not, which means that we really have to handle
both offsets individually instead of just handling the sum of the
offsets.

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

clk: imx: Add imx8mp clk driver ...

This adds clock support for the i.MX8MP, taken from Linux-5.7.

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>

mfd: Add pca9440 register map ...

The pca9440 is a PMIC found on the i.MX8MP-EVK board. This adds the
register map for it.

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

scripts: imx-image: Add i.MX8MP support ...

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

arm: imx: add initial imx8mp support ...

This adds base support for the i.MX8MP SoC. Not much to do here as this
SoC is quite similar to the i.MX8M. This adds:

- Kconfig symbols
- bootsource detection
- register base address defines
- iomux defines

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>

mci: imx-esdhc: Add i.MX8mp compatible ...

Only add the compatible string to let the driver match.

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>

net: fec_imx: add fsl,imx8mp-fec compatible ...

Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>

pinctrl: imx-iomux-v3: Add i.MX8MP compatible ...

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

serial: i.MX: Add i.MX8MP compatible ...

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