u-boot/board/xilinx/versal
Venkatesh Yadav Abbarapu 454f948ff4 xilinx: versal: Do not prioritize boot device if driver is not enabled
SOC can boot out of the device which is not accessible from APU and running
this is detected as a warning, as the device is not accessible.For example
getting below warning when the boot mode is OSPI and OSPI is not enabled in
device tree.
Invalid bus 0 (err=-19)
Failed to initialize SPI flash at 0:0 (error -19)

Ignoring the prioritization of the boot device which driver is not enabled
and continue with the default boot_targets. Recommendation is to use custom
boot_targets via environment file as is done for example for Kria via
zynqmp_kria.env file.

Signed-off-by: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
Signed-off-by: Michal Simek <michal.simek@amd.com>
Link: https://lore.kernel.org/r/8b7cca5c7b84cb4854104e0c48f8aa63c4ec5ace.1715322156.git.michal.simek@amd.com
2024-06-17 16:02:29 +02:00
..
board.c xilinx: versal: Do not prioritize boot device if driver is not enabled 2024-06-17 16:02:29 +02:00
cmds.c Restore patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet" 2024-05-20 13:35:03 -06:00
Kconfig xilinx: versal: Add new versal loadpdi command 2020-08-20 09:49:20 +02:00
MAINTAINERS .mailmap: Start to use new amd.com email address 2022-04-19 14:51:11 -04:00
Makefile arm64: zynqmp: Switch to amd.com emails 2023-07-21 09:00:38 +02:00