From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: nand: mxs: Add support for multiple NAND chips
Date: Sat, 6 Dec 2014 17:45:30 -0600 [thread overview]
Message-ID: <1417909530.5581.1.camel@freescale.com> (raw)
In-Reply-To: <201412061407.00278.marex@denx.de>
On Sat, 2014-12-06 at 14:07 +0100, Marek Vasut wrote:
> On Tuesday, December 02, 2014 at 02:26:14 PM, Stefan Roese wrote:
> > This patch adds support for multiple NAND chips connected to the
> > i.MX6. Linux already supports this configuration. So lets port
> > the missing features to the U-Boot driver to support more than
> > one NAND chip here as well.
> >
> > The necessary changes in detail are:
> >
> > - Only use DMA channel 0 for all NAND chips:
> > Linux: a7c12d01 (mtd: gpmi: use DMA channel 0 for all the
> > nand chips)
> > d159d8b7 (mtd: gpmi: decouple the chip select from
> > the DMA channel)
> > - On i.MX6 only use ready/busy pin for CS0:
> > Linux: 7caa4fd2 (mtd: gpmi: imx6: fix the wrong method for
> > checking ready/busy)
> >
> > To enable this feature the board needs to configure
> > CONFIG_SYS_NAND_MAX_CHIPS to 2 (or more).
> >
> > With these changes I'm able to detect and acces 2 NAND chips:
> >
> > => nand device
> >
> > Device 0: 2x nand0, sector size 128 KiB
> > Page size 2048 b
> > OOB size 64 b
> > Erase size 131072 b
>
> Shouldn't you see "Device 0" and "Device 1" ?
The "2x" indicates that there are two identical chips being treated as a
single device (chip->numchips).
-Scott
next prev parent reply other threads:[~2014-12-06 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 13:26 [U-Boot] [PATCH] mtd: nand: mxs: Add support for multiple NAND chips Stefan Roese
2014-12-06 13:07 ` Marek Vasut
2014-12-06 23:45 ` Scott Wood [this message]
2014-12-07 1:32 ` Marek Vasut
2014-12-07 1:50 ` Scott Wood
2014-12-07 5:26 ` Marek Vasut
2014-12-08 22:53 ` Scott Wood
2014-12-09 7:20 ` Stefan Roese
2014-12-09 7:34 ` Marek Vasut
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=1417909530.5581.1.camel@freescale.com \
--to=scottwood@freescale.com \
--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