From: Sascha Hauer <s.hauer@pengutronix.de>
To: robert.jarzmik@free.fr
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: add pxa3xx-nand driver
Date: Mon, 5 Jan 2015 13:03:22 +0100 [thread overview]
Message-ID: <20150105120322.GB4544@pengutronix.de> (raw)
In-Reply-To: <1511697250.362148406.1420454678099.JavaMail.root@zimbra1-e1.priv.proxad.net>
Hi Robert,
On Mon, Jan 05, 2015 at 11:44:38AM +0100, robert.jarzmik@free.fr wrote:
> ----- Mail original -----
> De: "Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>
> À: "Robert Jarzmik" <robert.jarzmik@free.fr>, barebox@lists.infradead.org
> Envoyé: Dimanche 4 Janvier 2015 19:50:55
> Objet: Re: [PATCH] mtd: nand: add pxa3xx-nand driver
>
> Hi Robert,
>
> > If my memory doesn't fail me, the NAND controller is called NFC v1 on
> > pxa3xx, and NFC v2 on mvebu SoCs.
> > I'm wondering if we can pick a better name for this driver in barebox.
> > Maybe something like 'mv_nfc_nand' ?
> As all drivers are called "nand_XXX", I'd rather have it nand_mrvl_nfc then.
> Does that sound good to you ?
>
> > Also, I think you can get rid of the 'builtin_flash_types' struct and
> > all the device detection routines, which are really duplicating the
> > MTD's lower level job.
> Well, not really. If I get rid of them, how will I get the following
> information :
> - page size
> - nand timings (tHP, ...)
> - controller width to use
> - ...
Things like mtd->writesize, mtd->erasesize, and mtd->size should be
initialized after calling nand_scan_ident(). These are currently
overwritten by the pxa nand driver, but normally you should be able to
remove this. IIRC barebox can also detect the chip widths automatically.
I don't know how to get the timings though.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-01-05 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 21:58 Robert Jarzmik
2015-01-04 18:50 ` Ezequiel Garcia
2015-01-05 10:44 ` robert.jarzmik
2015-01-05 12:03 ` Sascha Hauer [this message]
2015-01-05 20:32 ` Robert Jarzmik
2015-01-05 20:33 ` Ezequiel Garcia
2015-01-05 22:42 ` Robert Jarzmik
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=20150105120322.GB4544@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
/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