From: Scott Wood <oss@buserror.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] mtd: nand: fsl-ifc: fix support of multiple NAND devices
Date: Mon, 30 Oct 2017 16:58:00 -0500 [thread overview]
Message-ID: <1509400680.20386.13.camel@buserror.net> (raw)
In-Reply-To: <VI1PR04MB207868202A8E88745F39AE889A590@VI1PR04MB2078.eurprd04.prod.outlook.com>
On Mon, 2017-10-30 at 18:50 +0000, York Sun wrote:
> On 10/20/2017 03:43 AM, Kurt Kanzenbach wrote:
> > Currently the chipselect used to identify the corresponding NAND chip is
> > stored
> > at the controller and only set during fsl_ifc_chip_init(). This way, only
> > the
> > last NAND chip is working, as the previous value of cs_nand gets
> > overwritten.
> >
> > In order to solve this issue the chipselect is computed on demand by
> > evaluating
> > the bank variable. Thus, the correct chipselect for each NAND chip
> > operation is
> > used.
> >
> > Tested on hardware with two NAND chips connected to the IFC controller.
> >
> > Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
> > ---
> > Changes for v2:
> > - get rid of cs_nand and compute chipselect on demand
> > - pass priv instead of mtd to fsl_ifc_sram_init()
>
> Scott,
>
> Are you OK with this version? Somehow this patch was assigned me. I can
> bring it in if you ack it.
Acked-by: Scott Wood <oss@buserror.net>
-Scott
next prev parent reply other threads:[~2017-10-30 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 9:44 [U-Boot] [PATCH v2] mtd: nand: fsl-ifc: fix support of multiple NAND devices Kurt Kanzenbach
2017-10-30 18:50 ` York Sun
2017-10-30 21:58 ` Scott Wood [this message]
2017-11-17 17:18 ` 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=1509400680.20386.13.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