Versions of U-Boot before 2014.01 created a symlink from include/asm to
the architecture-specific header directory.

If an ARM board is build with that old version, then sandbox is built on
a more recent version (both with in-tree builds), the include/asm symlink
confuses the build system. It picks up the ARM headers when it should be
using the sandbox ones.

Since 2014 U-Boot has only created a symlink inside the include/asm/
directory and only for out-of-tree builds. So for in-tree builds it does
not expect to see an include/asm symlink. It is not removed by
'make mrproper'. It does show up with 'git status' but is easy enough to
miss.

Add include/asm to the files to remove with 'make mkproper'. For recent
U-Boot builds this has no effect, since include/asm is a directory, not a
file. If the include/asm symlink is there, it will be removed.
Reported-by: NMarek Szyprowski <m.szyprowski@samsung.com>
Signed-off-by: NSimon Glass <sjg@chromium.org>

s/psci_features/request_psci_features/g for the case when both
ARCH_SUPPORT_PSCI=y and ARM_PSCI_FW=y, that leads to these
compilation issues:

drivers/firmware/psci.c:69:12: error: conflicting types for 'psci_features'
   69 | static int psci_features(u32 psci_func_id)
      |            ^~~~~~~~~~~~~
In file included from drivers/firmware/psci.c:23:
./arch/arm/include/asm/system.h:548:5: note: previous declaration of 'psci_features' was here
  548 | s32 psci_features(u32 function_id, u32 psci_fid);
      |     ^~~~~~~~~~~~~
Tested-by: NAlexandru Gagniuc <mr.nuke.me@gmail.com>
Reported-by: NAlexandru Gagniuc <mr.nuke.me@gmail.com>
Fixes: b7135b03 ("psci: add features/reset2 support")
Signed-off-by: NIgor Opaniuk <igor.opaniuk@foundries.io>

This patch tries to distinguish two error messages.
Signed-off-by: Npeng.wang@smartm.com <peng.wang@smartm.com>

Python3 taken from the PATH causes build issues when pylibfdt bindings are
generated with Yocto SDK.

Python3 provided as a part of SDK is not compatible with host Python3,
therefore binding build breaks with following errors:

scripts/dtc/pylibfdt/libfdt_wrap.c:154:11: fatal error: Python.h: No such file or directory
  154 | # include <Python.h>
      |           ^~~~~~~~~~

Do not enforce the python3 from the PATH and make it conditionally-assigned
so it can be overridden from outside of build system. Keep the default
assignment to point to version that is taken from the PATH.

Similar fix has been introduced in b48bfc74 ("tools: allow to override
python"), where conditional assignment is used for python executable to
address similar build errors.
Signed-off-by: NAndrey Zhizhikin <andrey.zhizhikin@leica-geosystems.com>
Cc: Simon Glass <sjg@chromium.org>
Fixes: e91610da ("kconfig: re-sync with Linux 4.17-rc4")
Reviewed-by: NSimon Glass <sjg@chromium.org>

- Add base support for Marvell OcteonTX2 CN9130 DB (mostly done
  by Kostya)
- Sync Armada 8k MMU setup with Marvell version (misc Marvell
  authors)
- spi: kirkwood: Some fixes especially for baudrate generation
  (misc Marvell authors)
- mvebu: x530: Reduce SPL image size (Stefan)
- Rename "rx_training" to "mvebu_comphy_rx_training" (Stefan)

Even if only USB gadget is defined, dwc3 generic driver enables
a definition and probe/remove functions for host driver.

This enables the definition if USB_HOST is enabled only.
Signed-off-by: NKunihiko Hayashi <hayashi.kunihiko@socionext.com>

All newer Allwinner SoCs (since about 2013) miss the CONFIGDATA register
in their MUSB implementation, so they need a quirk to hardcode this.

Currently this quirk depends on listing the SoCs affected in musb_reg.h,
which means that this list needs to grow with every new chip.

Move the quirk feature into Kconfig, next to PIO_ONLY, and change the
default to y (for Allwinner builds), while listing the early
implementations as exceptions.

This fixes USB peripheral operation on some newer SoCs, which were not
explicitly listed before.

Tested on H6, H616, R40 (which were broken before), and also on the H5
and A20, for regressions.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>

This patch adds the base support for the Marvell Octeon TX2 CN913x DB.
Only one defconfig is added with this patch. Other board variants are
available (NAND, MMC booting) and images for these boards can be
generated by following the documentation added in the included README.
Signed-off-by: NKonstantin Porotchkin <kostap@marvell.com>
Signed-off-by: NStefan Roese <sr@denx.de>

This patch adds the dtsi/dts files needed to support the Marvell
Octeon TX2 CN913x DB. This is only the base port with not all
interfaces supported fully.
Signed-off-by: NKonstantin Porotchkin <kostap@marvell.com>
Signed-off-by: NStefan Roese <sr@denx.de>

Rename the misleading cmd "rx_training" to "mvebu_comphy_rx_training" to
avoid confusion and mixup with DDR3/4 training. This makes it clear,
that this command is platform specific and handles the COMPHY RX
training.

Also depend this cmd on ARMADA_8K and not TARGET_MVEBU_ARMADA_8K to make
is available for OcteonTX2 CN913x.
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Pali Rohár <pali@kernel.org>
Cc: Marek Behun <marek.behun@nic.cz>
Cc: Kostya Porotchkin <kostap@marvell.com>
Cc: Nadav Haklai <nadavh@marvell.com>
Acked-by: NMarek Behún <marek.behun@nic.cz>
Acked-by: NPali Rohár <pali@kernel.org>

The pcie_dw_mvebu configure ATU regions for memory, configuration
and IO space types. However the latter is not obligatory
and when not specified in the device tree, causes wrong
ATU configuration. Fix that by adding a dependency on the
detected PCIE regions count.
Signed-off-by: NMarcin Wojtas <mw@semihalf.com>
Reviewed-on: https://sj1git1.cavium.com/18136Reviewed-by: NKostya Porotchkin <kostap@marvell.com>
Tested-by: NKostya Porotchkin <kostap@marvell.com>

Some of the setups including cn9130 opens mmio window starting from
0xc0000000, reflect it in the u-boot code.
Signed-off-by: NGrzegorz Jaszczyk <jaz@semihalf.com>
Signed-off-by: NKostya Porotchkin <kostap@marvell.com>
Signed-off-by: NStefan Roese <sr@denx.de>

Signed-off-by: NGrzegorz Jaszczyk <jaz@semihalf.com>
Signed-off-by: NStefan Roese <sr@denx.de>

There is region left by ATF, which needs to remain in memory to provide RT
services. To prevent overwriting it by u-boot, do not provide any mapping
for this memory region, so any attempt to access it will trigger
synchronous exception.

Update sr 2021-04-12:
Don't update armada3700/cpu.c mmu table, as this has specific changes
included in mainline.
Signed-off-by: NGrzegorz Jaszczyk <jaz@semihalf.com>
Signed-off-by: NStefan Roese <sr@denx.de>

1. RAM: base address 0x0 size 2Gbytes
2. MMIO: base address 0xf0000000 size 1Gbytes
Signed-off-by: NOfir Fedida <ofedida@marvell.com>
Signed-off-by: NStefan Roese <sr@denx.de>

After commit 1fe929ed497bcc8975be8d37383ebafd22b99dd2
("spi: kirkwood: prevent configuring speed exceeding max controller freq")
the spi frequency could be set to 0 on platform where spi-max-frequency
is not defined (e.g. on armada-388-gp). Prevent limiting speed in
mentioned cases.
Signed-off-by: NGrzegorz Jaszczyk <jaz@semihalf.com>
Tested-by: NKostya Porotchkin <kostap@marvell.com>
Reviewed-by: NMarcin Wojtas <marcin@marvell.com>
Reviewed-by: NKostya Porotchkin <kostap@marvell.com>
Signed-off-by: NStefan Roese <sr@denx.de>

This patch adds a limitation in the kirkwood_spi driver
set_speed hook, which prevents setting too high transfer
speed.
Signed-off-by: NMarcin Wojtas <mw@semihalf.com>
Reviewed-by: NKostya Porotchkin <kostap@marvell.com>
Tested-by: NKostya Porotchkin <kostap@marvell.com>
Signed-off-by: NStefan Roese <sr@denx.de>

The Armada SoC family implementation of this SPI hardware module has
extended the configuration register to allow for a wider range of SPI
clock rates. Specifically the Serial Baud Rate Pre-selection bits in the
SPI Interface Configuration Register now also use bits 6 and 7 as well.

Modify the baud rate calculation to handle these differences for the
Armada case. Potentially a baud rate can be setup using a number of
different pre-scalar and scalar combinations. This code tries all
possible pre-scalar divisors (8 in total) to try and find the most
accurate set.
Signed-off-by: NKen Ma <make@marvell.com>
Signed-off-by: NStefan Roese <sr@denx.de>

Currently, building U-Boot for x530 fails since the SPL image is too
big. This patch reduces the SPL size by changing the following Kconfig
options:

Enable CONFIG_SPL_TINY_MEMSET
Disable CONFIG_SPI_FLASH_BAR

By disabling CONFIG_SPI_FLASH_BAR, the tiny SPI NOR framework can be
used.
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: Pratyush Yadav <p.yadav@ti.com>
Cc: Tom Rini <trini@konsulko.com>
Tested-by: NChris Packham <chris.packham@alliedtelesis.co.nz>
Acked-by: NPratyush Yadav <p.yadav@ti.com>

Rsync all defconfig files using moveconfig.py
Signed-off-by: NTom Rini <trini@konsulko.com>

- dts: add missing -u-boot.dtsi to enable HDMI on Beelink GTKing/King-Pro
- usb: dwc3-meson-g12a: skip phy on -ENODATA aswell
- net: dwmac_meson8b: do not set TX delay in TXID & RXID
- net: designware: meson8b: add g12a compatible

Add support for the Meson G12A dwmac glue compatible needed after Linux 5.12 sync.
Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>

When the PHY interface is set as TXID & RXID, the delays should be taken from DT,
but first they should not be hardcoded since the PHY driver will set them.

Fixes: 798424e8 ("net: designware: add Amlogic Meson8b & later glue driver")
Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>
Reviewed-by: NRamon Fried <rfried.dev@gmail.com>

If the PHY isn't specified in the DT, -ENODATA means it should be skipped,
handle it like -ENOENT.

With that, devices without USB3 supported can have USB working (Odroid-HC4).

Fixes: adb049ab ("usb: dwc3: Add Meson G12A USB Glue")
Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>

This lacks the right u-boot specific DT include to make HDMI work.
Reported-by: NB1oHazard <ty3uk@mail.ua>
Signed-off-by: NNeil Armstrong <narmstrong@baylibre.com>

This reverts commit bc8bbb77.

This commit breaks U-Boot booting on SiFive Unleashed board, as
there is no such CSR on U54 core.
Signed-off-by: NBin Meng <bmeng.cn@gmail.com>
Reviewed-by: NLeo Yu-Chi Liang <ycliang@andestech.com>

The pwm_sifive_set_config() and pwm_sifive_set_enable() cannot work
properly due to the wrong implementations. It will cause the u-boot
PWM command to not work as expected. The bugs will be resolved in this
patch.
Signed-off-by: NVincent Chen <vincent.chen@sifive.com>
Reviewed-by: NRick Chen <rick@andestech.com>

It is no longer necessary to disallow ai ram, since it is enabled by the
sram driver.
Signed-off-by: NSean Anderson <seanga2@gmail.com>

Testing showed that disabling AI while leaving PLL1 enabled disabled the
aisram. This suggests that AI is a more appropriate clock for that ram
bank.
Signed-off-by: NSean Anderson <seanga2@gmail.com>

This is more consistent with the naming of other ram banks, and matches
what Linux is doing.
Reported-by: NDamien Le Moal <Damien.LeMoal@wdc.com>
Signed-off-by: NSean Anderson <seanga2@gmail.com>

We just need to initialize all the clocks pre-reloc. The clock driver
creates a bunch of devices, so we need to increase the pre-reloc malloc
arena.
Signed-off-by: NSean Anderson <seanga2@gmail.com>

These devices are necessary for the clock driver, which is required by the
sram driver, to run pre-relocation.
Signed-off-by: NSean Anderson <seanga2@gmail.com>

Variables which had previously been stored in .bss are moved to .data. In
addition, probed needs to be reset when the clock driver is re-bound
post-relocation.
Signed-off-by: NSean Anderson <seanga2@gmail.com>

No other (real) clocks have the cpu clock as their parent; instead they are
children of aclk. Move the clint clock under aclk to match them.
Signed-off-by: NSean Anderson <seanga2@gmail.com>

This simplifies the PLL creation process, since we don't have to pass all
the parameters individually.
Signed-off-by: NSean Anderson <seanga2@gmail.com>

This conditional always evaluated as false, regardless of the value of reg.
Fix it so that it properly tests the bits in the PLL register. Also test
PLL_EN, now that we set it.
Reported-by: NDamien Le Moal <Damien.LeMoal@wdc.com>
Signed-off-by: NSean Anderson <seanga2@gmail.com>

After starting or setting the rate of a PLL, the enable bit must be set.

This fixes a bug where the AI ram would not be accessible, because it
requires PLL1 to be running.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NDamien Le Moal <damien.lemoal@wdc.com>