issue found when working with 12c variant and CAN-FD is disabled (bit12)
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

1. Added TI based retimer initialization on 25Gbp SERDES configuration.
Note that those retimers are available on ClearFog CX revision 1.3 and
newer
2. Restructure SERDES configuration files
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

1. Fixed u-boot build when using u-boot release LSDK-20.04-update-290520
2. Added SD1 protocol #14 (100Gbps with PCIe gen3 x4) configuration
3. Removed UEFI from this git repository; mainline edk2-platforms now
supports most of the bits for LX2 and HoneyComb. For building uefi
repository refer to SolidRun github lx2160a_uefi repo.
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

1. Poweroff the HoneyComb board by asserting SUS_S5# signal
2. Add USB3.0 DWC3 workaround by disabling parkmode
3. Keep flexspi divisor as default which is ~17MHz. This enables using
the carrier board SPI that is limited in speed due to the analogue mux
connected to it.
4. Remove uefi build and update LSDK20.04 to may-29 update. UEFI is
temporarily hosted at https://github.com/SolidRun/lx2160a_uefi until
fully upstreamed.
5. Add 4x25Gbps MC config
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

u-boot: some tweaks to distro-boot for enabling standard debian

Signed-off-by: Josua Mayer <josua@solid-run.com>

Signed-off-by: Josua Mayer <josua@solid-run.com>

1. Manually edited patch 0018-lx... to fix atheros phy related config.
2. Just before booting the kernel toggle back the fan full speed signal
to enable the kernel driver to initialize the AMC6821 device
3. Add u-boot poweroff command that set S5# (GPIO3 7) signal to low;
thus turning off the HoneyComb / ClearFog CX boards.
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

u-boot fails to fixup the PCIe nodes on the rev1 LX2160A due to the
code not testing for the correct ID.  Add the correct ID.
Signed-off-by: Russell King <rmk@armlinux.org.uk>

CONFIG_PHY_ATHEROS was incorrectly deleted by the PCIe fixup and
eMMC boot patch.  Fix that bad patch.
Signed-off-by: Russell King <rmk@armlinux.org.uk>

Previously multistrap was used to download and create an ubuntu rootfs;
but multistrap failed under docker build since it required binfmt
installed.

This technique of installing ubuntu rootfs is totally different method,
takes more time to build but works under the native runme.sh script and
under docker build.

The method idea is -
1. Build a simple rootfs with a kernel that can be booted via
qemu-system-aarch64.
2. Install an initi script called S99bootstrap-ubuntu.sh under
/etc/init.d.
3. Run a qemu-system-aarch64 virtual machine with 1GByte of system
memory and use cortex-a57 which is the closed to cortex-a72,
virtualization wise and has the buildroot rootf as initrd and the
destination ubuntu-core.ext4 partition as a drive.
4. The VM would boot the kernel, mount the rootfs and run the
S99bootstrap-ubuntu.sh script
5. The script would download an ubuntu base image and then 'apt install'
in a virtual chrooted environment the reset of the packages to make this
rootfs to be bootable.
6. Use 'reboot' in the VM which triggers the '-no-reboot' flag for qemu
that makes the vm exit; and thus installation is continued.
7. ubuntu-core.ext4 partition is now ready to be used further on for
imaging and installations.
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

not needed for LX2
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

1. moved from ubuntu disco to focal
2. updated documentation on the unified image that auto-detects boot
device
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

runme.sh: Convert to bash defaults, use switch for serdes config

docker: add python3

Signed-off-by: Olof Johansson <olof@lixom.net>

Python3 is needed to build now. Also, when doing the second install step,
I get some URL errors so do the apt-get update once more (not sure why
it's needed twice).
Signed-off-by: Olof Johansson <olof@lixom.net>

Using conditional load and jump in RCW and boot=auto as a parameter for
ATF it is possible now to build a single image that can be booted from
SPI, SD or eMMC.

Still there is a small difference BL2 stage where on SPI it is located
on address 0x0 and SD/eMMC is located with 0x1000 (8 blocks of 512
bytes) offset.

Additional feature is runtime RCW file creation; this will be further
enhanced to create the SERDES and PLL multipliers creation in runtime
too.
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

This commit incorporates the following features / fixes -
1. Add support for lx2160a-early-access-bsp0.7 which includes rev1 and
rev 2 support
2. Split linux/rcw/u-boot patches to be dependent on release based on
3. rcw added feature to use loadc/jumpc/jump PBI commands to
differentiate between rev1 and rev2

Under debug -
1. LX2 rev2 u-boot reset and linux reboot are not functional.
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

u-boot patches split into lsdk-19.06 and lsdk-19.09 and added patch
0015-.... that adds the support to lsdk-19.09.
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

This patch holds the following modifications and support -
1. Added support to LSDK 19.09. Notice that conflicting patch
directories will hold the release prefix (look at patch/linux-*).
2. We don't use lsdk.config config file any more and added the required
kernel driver via lx2k_additions.config file
3. Add 4 eeprom support (512Kb I2C bootable, two SPD and 2Kb for misc)
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

this patch adds ltc3882 to the device tree and exposes it via 'sensors'
-

as an example -
root@localhost:~# sensors
ltc3882-i2c-5-5c
Adapter: i2c-0-mux (chan_id 2)
vin:         +12.00 V  (min =  +6.30 V, crit max = +15.50 V)
                       (highest = +12.16 V)
vout1:        +0.78 V  (crit min =  +0.72 V, min =  +0.73 V)
                       (max =  +0.84 V, crit max =  +0.86 V)
                       (highest =  +0.78 V)
vout2:        +0.78 V  (crit min =  +0.72 V, min =  +0.73 V)
                       (max =  +0.84 V, crit max =  +0.86 V)
                       (highest =  +0.78 V)
temp1:        +49.6°C  (high = +85.0°C, crit low = -40.0°C)
                       (crit = +90.0°C, highest = +55.8°C)
temp2:        +48.8°C  (high = +85.0°C, crit low = -40.0°C)
                       (crit = +90.0°C, highest = +55.3°C)
temp3:        +53.0°C  (high = +85.0°C, crit low = -40.0°C)
                       (crit = +90.0°C, highest = +57.4°C)
pout1:         6.13 W
pout2:         5.87 W
iout1:        +7.79 A  (max = +50.00 A, crit max = +50.00 A)
                       (highest = +16.44 A)
iout2:        +7.57 A  (max = +50.00 A, crit max = +50.00 A)
                       (highest = +16.78 A)
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

spr2803 pcie base class id is 0x0; this patch removes the case where it
doesn't allocate resources for such a device.
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

- more tools to install prior to build
- strip kernel modules and copy them over
Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

Signed-off-by: Rabeeh Khoury <rabeeh@solid-run.com>

patches: u-boot: add nvme fixes from upstream

Fix NVMe init issue

I think the critical ones are really around cache management. With these,
I can consistently boot from NVMe (Samsung 970 Pro).
Signed-off-by: Olof Johansson <olof@lixom.net>

Signed-off-by: Damjan Marion <dmarion@me.com>

A few more docker/script fixes