u-boot.git/arch/arm/dts, branch master

arm: Add support for Kobol Helios64 board

2021-06-12T19:39:14+00:00

The hardware is described in detail on Kobol's wiki at
https://wiki.kobol.io/helios64/intro/.

This commit is based on downstream work in Armbian by Aditya Prayoga [1].
The devicetree is taken from Linux v5.12-rc1 and was originally submitted there by
Uwe Kleine-Koenig [2].

[1] https://github.com/ukleinek/armbian-build/blob/35c85295d351830aa59b624db524ba04b238faae/patch/kernel/rockchip64-current/add-board-helios64.patch
[2] https://github.com/torvalds/linux/blob/7a7fd0de4a9804299793e564a555a49c1fc924cb/arch/arm64/boot/dts/rockchip/rk3399-kobol-helios64.dts

Signed-off-by: Dennis Gilmore

arm: mvebu: dts: turris_mox: add nodes for SPI NOR partitions

2021-06-10T05:18:06+00:00

Add nodes for SPI NOR partitions to the device tree of Turris MOX, as
are in Linux' device tree.

Signed-off-by: Marek Behún 
Reviewed-by: Stefan Roese

arm: mvebu: dts: turris_mox: add button and LED nodes

2021-06-10T05:18:06+00:00

Add nodes for indicator LED and reset button so that board code can
implement board factory reset mechanism.

Signed-off-by: Marek Behún 
Reviewed-by: Pali Rohár 
Reviewed-by: Stefan Roese

arm: a37xx: pci: Increase PCIe MEM size from 16 MiB to 127 MiB

2021-06-04T09:32:41+00:00

For some configurations with more PCIe cards and PCIe bridges, 16 MiB of
PCIe MEM space may not be enough. Since TF-A already allocates a 128 MiB
CPU window for PCIe, and since IO port space is only 64 KiB in total,
use all the remaining space (64 + 32 + 16 + 8 + 4 + 2 + 1 = 127 MiB) for
PCIe MEM.

Signed-off-by: Pali Rohár 
Reviewed-by: Marek Behún 
Reviewed-by: Stefan Roese

arm: a37xx: pci: Fix DT compatible string to Linux' DT compatible

2021-06-04T09:32:41+00:00

Change DT compatible string for A3700 PCIe from 'marvell,armada-37xx-pcie'
to 'marvell,armada-3700-pcie' to make U-Boot A3700 PCIe DT node compatible
with Linux' DT node.

Signed-off-by: Pali Rohár 
Reviewed-by: Marek Behún 
Reviewed-by: Stefan Roese

sunxi: Bring back SD card as MMC device 0

2021-05-30T23:39:54+00:00

Commit 2243d19e5618 ("mmc: mmc-uclass: Use dev_seq() to read aliases
node's index") now actually enforces U-Boot's device enumeration policy,
where explicitly named devices come first, then any other non-named
devices follow, without filling gaps.

For quite a while we have had an "mmc1 = &mmc2;" alias in our
sunxi-u-boot.dtsi, which now leads to the problem that the SD card
(which was always mmc device 0) now gets to be number 2.
This breaks quite some boot scripts, including our own distro boot
commands, and some other features looking at $mmc_bootdev, also
fastboot.

Just add an explicit mmc0 alias in the very same file to fix this and
restore the old behaviour.

Signed-off-by: Andre Przywara 
Reported-by: Samuel Holland 
Tested-by: Simon Baatz

arm: dts: stm32mp157c-odyssey-som: enable the RNG1

2021-05-28T13:05:39+00:00

Enable the true random number generator. It can be used, for example, to
generate partition UUIDs when partitioning with the gpt command. The
generator is already enabled in the device trees of several other
STM32MP1‐based boards, like DKx or DHCOM.

Signed-off-by: Grzegorz Szymaszek 
Cc: Patrice Chotard 
Cc: Patrick Delaunay 
Reviewed-by: Patrick Delaunay

arm: dts: k3-am642-sk: Add sysreset controller node

2021-05-27T09:23:14+00:00

The AM64x SoC uses a central Device Management and Security Controller
(DMSC) processor that manages all the low-level device controls
including the system-wide SoC reset. The system-wide reset is managed
through the system reset driver.

Add a sysreset controller node as a child of the dmsc node to enable
the "reset" command from U-Boot prompt for the K3 AM642 SK.

Signed-off-by: Suman Anna 
Signed-off-by: Lokesh Vutla

arm: dts: k3-am642-evm: Add sysreset controller node

2021-05-27T09:23:14+00:00

The AM64x SoC uses a central Device Management and Security Controller
(DMSC) processor that manages all the low-level device controls
including the system-wide SoC reset. The system-wide reset is managed
through the system reset driver.

Add a sysreset controller node as a child of the dmsc node to enable
the "reset" command from U-Boot prompt for the K3 AM642 EVM.

Signed-off-by: Suman Anna 
Signed-off-by: Lokesh Vutla

arm: dts: k3-j721e: Fix up MAIN R5FSS cluster mode back to Split-mode

2021-05-27T09:22:16+00:00

The default U-Boot environment variables and design are all set up for
both the MAIN R5FSS clusters to be in Split-mode. This is the setting
in v2021.01 U-Boot and the dt nodes are synched with the kernel binding
property names in commit 468ec2f3ef8f ("remoteproc: k3_r5: Sync to
upstreamed kernel DT property names") merged in v2021.04-rc2.

The modes for both the clusters got switched back to LockStep mode by
mistake in commit 70e167495ab2 ("arm: dts: k3-j721e: Sync Linux v5.11-rc6
dts into U-Boot") also in v2021.04-rc2. This throws the following warning
messages when early-booting the cores using default env variables,

  k3_r5f_rproc r5f at 5d00000: Invalid op: Trying to start secondary core 7 in lockstep mode
  Load Remote Processor 3 with data at addr=0x82000000 98484 bytes: Failed!
  k3_r5f_rproc r5f at 5f00000: Invalid op: Trying to start secondary core 9 in lockstep mode
  Load Remote Processor 5 with data at addr=0x82000000 98484 bytes: Failed!

Fix this by switching back both the clusters to the expected Split-mode.
Make this mode change in the u-boot specific dtsi file to avoid such
sync overrides in the future until the kernel dts is also switched to
Split-mode by default.

Fixes: 70e167495ab2 ("arm: dts: k3-j721e: Sync Linux v5.11-rc6 dts into U-Boot")
Reported-by: Minas Hambardzumyan 
Signed-off-by: Suman Anna 
Signed-off-by: Lokesh Vutla