u-boot.git/arch/arm/cpu, branch v2021.01

arm: ls102xa: select USB PHY erratum's only if USB is enabled

2020-12-10T08:26:39Z

The USB support is not by default enabled on all designs, so it does not make seance to have USB specific erratum's enabled on such a designs. On our internal Hitachi-Powergrids design not using the USB controller there is a crash when accessing those specific memory locations selected by the erratum flags. Signed-off-by: Aleksandar Gerasimovski Reviewed-by: Priyanka Jain

armv8: fsl-layerscape: Fix automatic setting of bootmcd with TF-A

2020-12-10T08:26:39Z

When booting from TF-A there is a logic that attempt to detect if the default environment is used, if this is the case it then set the `bootcmd` and `mcinitcmd` depending of the device we booted from. This detection logic is dubious as it access internals of the env implementation and it doesn't always work correctly. First of all it detect any valid environment as not being the default, so after running `env default -a && saveenv` the board doesn't boot anymore as `bootcmd` is then empty. But it also fails in some other ways, for example it always detect a default environment when redundant env is enabled on MMC, so in that case `bootcmd` is overwritten on every boot. Instead of increasing the complexity of the detection just check if `bootcmd` and `mcinitcmd` are set in the environment and set them if they are not. Signed-off-by: Alban Bedel Reviewed-by: Priyanka Jain

layerscape: fdt.c: Check for NULL return value from fdt_getprop()

2020-12-10T08:26:39Z

Check for NULL return value from fdt_getprop() in fdt_fixup_remove_jr() Signed-off-by: Priyanka Singh [Fixed checkpatch errors/warnings] Signed-off-by: Priyanka Jain

armv8: lx2162a: Add Soc changes to support LX2162A

2020-12-10T08:26:39Z

LX2162 is LX2160 based SoC, it has same die as of LX2160 with different packaging. LX2162A support 64-bit 2.9GT/s DDR4 memory, i2c, micro-click module, microSD card, eMMC support, serial console, qspi nor flash, qsgmii, sgmii, 25g, 40g, 50g network interface, one usb 3.0 and serdes interface to support three PCIe gen3 interface. Signed-off-by: Meenakshi Aggarwal [Fixed whitespace errors] Signed-off-by: Priyanka Jain

armv8: layerscape: don't remove crypto node if just partially disabled

2020-10-23T11:22:09Z

On all newer Layerscape SoCs, only the export-controlled ciphers of the crypto module are disabled on non-E parts. Thus it doesn't make sense to completely remove the node. Linux will figure out what is there and what is not. Just remove it for older SoCs, where the module is indeed completely disabled on non-E parts. Signed-off-by: Michael Walle Reviewed-by: Horia Geanta Reviewed-by: Priyanka Jain

net: lx2160a.c: Update to set ECx_PMUX precedence

2020-10-23T11:22:09Z

As per hardware documentation, ECx_PMUX has precedence over SerDes protocol. For LX2160/LX2162 if DPMACs 17 and 18 are enabled as SGMII through SerDes protocol but ECx_PMUX configured them as RGMII, then the ports will be configured as RGMII and not SGMII. Signed-off-by: Razvan Ionut Cirjan [Rebased] Signed-off-by: Priyanka Jain

pci: layerscape: add a way of specifying additional iommu mappings

2020-10-23T11:22:09Z

In the current implementation, u-boot creates iommu mappings only for PCI devices enumarated at boot time thus does not take into account more dynamic scenarios such as SR-IOV or PCI hot-plug. Add an u-boot env var and a device tree property (to be used for example in more static scenarios such as hardwired PCI endpoints that get initialized later in the system setup) that would allow two things: - for a SRIOV capable PCI EP identified by its B.D.F specify the maximum number of VFs that will ever be created for it - for hot-plug case, specify the B.D.F with which the device will show up on the PCI bus More details can be found in the included documentation: arch/arm/cpu/armv8/fsl-layerscape/doc/README.pci_iommu_extra Signed-off-by: Laurentiu Tudor Reviewed-by: Priyanka Jain

arm: fsl-layerscape: Include device_compat.h in soc.c

2020-10-16T13:44:27Z

Necessary for dev_xxx. Signed-off-by: Tom Rini

arm64: PIE: Skip fixups if distance is zero

2020-10-08T15:42:36Z

When the actual offset between link and runtime address is zero, there is no need for patching up U-Boot early when running with CONFIG_POSITION_INDEPENDENT. Skip the whole routine when the distance is 0. This helps when U-Boot is loaded into ROM, or in otherwise sensitive memory locations. Signed-off-by: Andre Przywara Reviewed-by: Stephen Warren

Merge branch 'next'

2020-10-05T18:10:59Z

Bring in the assorted changes that have been staged in the 'next' branch prior to release. Signed-off-by: Tom Rini