From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [Patch V3 3/3] armv8/ls1043aqds: add QSPI boot support
Date: Mon, 11 Jan 2016 11:46:45 -0600 [thread overview]
Message-ID: <1452534405.19133.41.camel@buserror.net> (raw)
In-Reply-To: <1452478629-6154-4-git-send-email-Qianyu.Gong@nxp.com>
On Mon, 2016-01-11 at 10:17 +0800, Gong Qianyu wrote:
> diff --git a/board/freescale/ls1043aqds/ls1043aqds.c
> b/board/freescale/ls1043aqds/ls1043aqds.c
> index d6696ca..770b79f 100644
> --- a/board/freescale/ls1043aqds/ls1043aqds.c
> +++ b/board/freescale/ls1043aqds/ls1043aqds.c
> @@ -43,15 +43,19 @@ enum {
>
> int checkboard(void)
> {
> +#ifndef CONFIG_QSPI_BOOT
> char buf[64];
> #ifndef CONFIG_SD_BOOT
> u8 sw;
> #endif
> +#endif
>
> puts("Board: LS1043AQDS, boot from ");
>
> #ifdef CONFIG_SD_BOOT
> puts("SD\n");
> +#elif defined(CONFIG_QSPI_BOOT)
> + puts("QSPI\n");
> #else
> sw = QIXIS_READ(brdcfg[0]);
> sw = (sw & QIXIS_LBMAP_MASK) >> QIXIS_LBMAP_SHIFT;
> @@ -68,12 +72,15 @@ int checkboard(void)
> printf("invalid setting of SW%u\n", QIXIS_LBMAP_SWITCH);
> #endif
>
> +#ifndef CONFIG_QSPI_BOOT
> + /* For QSPI boot, here I2C is not ready yet. */
> printf("Sys ID: 0x%02x, Sys Ver: 0x%02x\n",
> QIXIS_READ(id), QIXIS_READ(arch));
>
> printf("FPGA: v%d (%s), build %d\n",
> (int)QIXIS_READ(scver), qixis_read_tag(buf),
> (int)qixis_read_minor());
> +#endif
Why isn't i2c ready? How is DDR inited without it?
-Scott
next prev parent reply other threads:[~2016-01-11 17:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 2:17 [U-Boot] [Patch V3 0/3] LS1043AQDS SPI related patches Gong Qianyu
2016-01-11 2:17 ` [U-Boot] [Patch V3 1/3] armv8/ls1043aqds: add DSPI support Gong Qianyu
2016-01-11 2:17 ` [U-Boot] [Patch V3 2/3] armv8/ls1043aqds: add QSPI support in SD boot Gong Qianyu
2016-01-11 2:17 ` [U-Boot] [Patch V3 3/3] armv8/ls1043aqds: add QSPI boot support Gong Qianyu
2016-01-11 17:46 ` Scott Wood [this message]
2016-01-12 3:14 ` Qianyu Gong
2016-01-14 0:20 ` Scott Wood
2016-01-14 4:26 ` Qianyu Gong
2016-01-19 6:13 ` Calvin Johnson
2016-01-19 6:58 ` Qianyu Gong
2016-01-21 22:50 ` Scott Wood
2016-01-22 4:57 ` Qianyu Gong
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=1452534405.19133.41.camel@buserror.net \
--to=oss@buserror.net \
--cc=u-boot@lists.denx.de \
/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