From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] board: freescale: ls1012ardb: Add command to switch QSPI bank
Date: Thu, 19 Apr 2018 20:10:28 -0500 [thread overview]
Message-ID: <1524186628.5274.33.camel@buserror.net> (raw)
In-Reply-To: <CAEhpT-Xsny4XOjTCxZ=yhyaCVNznwUS+EyG-TM08-iGO6XowNQ@mail.gmail.com>
On Thu, 2018-04-19 at 14:09 +0530, Calvin Johnson wrote:
> On Thu, Apr 19, 2018 at 12:17 PM, Scott Wood <oss@buserror.net> wrote:
> > On Mon, 2018-04-16 at 08:40 +0530, Calvin Johnson wrote:
> > > On Fri, Apr 13, 2018 at 12:18 AM, Jagdish Gediya <jagdish.gediya@nxp.com
> > > >
> > > wrote:
> > > > Add command "boot_bank X" to switch the boot bank to either
> > > > 1 or 2.
> > >
> > > Are these functions required as this can be handled by new env vars to
> > > switch banks?
> >
> > If you're going to add something new, a command is much more pleasant than
> > env
> > vars -- particularly if you stick to something like the familiar
> > interfaces
> > ("pix altbank", "qix altbank", etc), and include reporting of which bank
> > was
> > booted from if it's not there already. Of course, a fully standardized
> > interface would be even better.
>
> Yes, a fully standardized generic interface supporting all similar
> platforms with multiple banks
And other boot sources such as NAND and MMC.
> would be better. What this patch currently does can be done with
> simple env vars, like :
>
> setenv boot_bank_1 'i2c mw 0x24 0x7 0xfc; i2c mw 0x24 0x3 0xf5'
> setenv boot_bank_2 'i2c mw 0x24 0x7 0xfc; i2c mw 0x24 0x3 0xf4'
...if the user knows to env reset those variables after the update (versus
something that shows up in help), and if they don't get corrupted in a multi-
user board farm environment, etc.
-Scott
next prev parent reply other threads:[~2018-04-20 1:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 18:48 [U-Boot] [PATCH] board: freescale: ls1012ardb: Add command to switch QSPI bank Jagdish Gediya
2018-04-16 3:10 ` Calvin Johnson
2018-04-19 6:47 ` Scott Wood
2018-04-19 8:39 ` Calvin Johnson
2018-04-20 1:10 ` Scott Wood [this message]
2018-04-20 1:53 ` Calvin Johnson
2018-07-31 15:07 ` York Sun
2018-07-31 15:36 ` Calvin Johnson
2018-04-20 3:16 ` Prabhakar Kushwaha
2018-04-20 15:45 ` Scott Wood
2018-08-13 16:20 ` York Sun
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=1524186628.5274.33.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