From: Michal Simek <michal.simek@amd.com>
To: u-boot@lists.denx.de, git@xilinx.com
Cc: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>,
"Polak, Leszek" <LPolak@arri.de>, Stefan Roese <sr@denx.de>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] xilinx: versal: Do not prioritize boot device if driver is not enabled
Date: Wed, 29 May 2024 15:15:44 +0200 [thread overview]
Message-ID: <ae4f2abc-bc47-47c1-bde9-960df45f278d@amd.com> (raw)
In-Reply-To: <8b7cca5c7b84cb4854104e0c48f8aa63c4ec5ace.1715322156.git.michal.simek@amd.com>
On 5/10/24 08:22, Michal Simek wrote:
> From: Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
>
> 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>
> ---
>
> board/xilinx/versal/board.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/board/xilinx/versal/board.c b/board/xilinx/versal/board.c
> index 4f6d56119db1..f00605da7825 100644
> --- a/board/xilinx/versal/board.c
> +++ b/board/xilinx/versal/board.c
> @@ -151,14 +151,29 @@ static int boot_targets_setup(void)
> break;
> case QSPI_MODE_24BIT:
> puts("QSPI_MODE_24\n");
> + if (uclass_get_device_by_name(UCLASS_SPI,
> + "spi@f1030000", &dev)) {
> + debug("QSPI driver for QSPI device is not present\n");
> + break;
> + }
> mode = "xspi0";
> break;
> case QSPI_MODE_32BIT:
> puts("QSPI_MODE_32\n");
> + if (uclass_get_device_by_name(UCLASS_SPI,
> + "spi@f1030000", &dev)) {
> + debug("QSPI driver for QSPI device is not present\n");
> + break;
> + }
> mode = "xspi0";
> break;
> case OSPI_MODE:
> puts("OSPI_MODE\n");
> + if (uclass_get_device_by_name(UCLASS_SPI,
> + "spi@f1010000", &dev)) {
> + debug("OSPI driver for OSPI device is not present\n");
> + break;
> + }
> mode = "xspi0";
> break;
> case EMMC_MODE:
Applied.
M
prev parent reply other threads:[~2024-05-29 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 6:22 [PATCH] xilinx: versal: Do not prioritize boot device if driver is not enabled Michal Simek
2024-05-29 13:15 ` Michal Simek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae4f2abc-bc47-47c1-bde9-960df45f278d@amd.com \
--to=michal.simek@amd.com \
--cc=LPolak@arri.de \
--cc=git@xilinx.com \
--cc=sr@denx.de \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=venkatesh.abbarapu@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox