From: Scott Wood <scottwood@freescale.com>
To: Aaron Sierra <asierra@xes-inc.com>
Cc: linux-mtd@lists.infradead.org,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Prabhakar Kushwaha <prabhakar@freescale.com>
Subject: Re: [PATCH 2/2] mtd: fsl_ifc_nand: Probe partitions OF node
Date: Wed, 20 Aug 2014 18:59:56 -0500 [thread overview]
Message-ID: <1408579196.4058.80.camel@snotra.buserror.net> (raw)
In-Reply-To: <917570204.96674.1408578333042.JavaMail.zimbra@xes-inc.com>
On Wed, 2014-08-20 at 18:45 -0500, Aaron Sierra wrote:
> ----- Original Message -----
> > From: "Scott Wood" <scottwood@freescale.com>
> > Sent: Wednesday, August 20, 2014 6:26:25 PM
> >
> > On Fri, 2014-08-15 at 19:47 -0500, Aaron Sierra wrote:
> > > Previously, the OF node defining the IFC NAND controller was being
> > > passed to mtd_device_parse_register(), not the node defining the
> > > partitions. This resulted in no OF-defined partitions being created.
> >
> > This driver probes on "fsl,ifc-nand", not "fsl,ifc". So how is it
> > getting the controller node?
> >
> > What does the device tree look like in which you're seeing this happen?
> >
> > -Scott
> >
>
> This is the node that is defined in my T1042 device tree:
>
> nand0@4,0 {
> #address-cells = <0>;
> #size-cells = <0>;
> compatible = "fsl,ifc-nand";
> reg = <4 0x0 0x040000>;
>
> nand@0 {
> #address-cells = <1>;
> #size-cells = <2>;
> compatible = "micron,mt29f32g08";
>
> partition@0 {
> label = "NAND Filesystem";
> reg = <0 0x1 0x00000000>;
> };
> };
> };
This is wrong. You shouldn't have a separate nand@0 node.
Your patch will break partition detection on all of the existing IFC
device trees.
> It is based on a node used previously with the fsl_upm NAND driver on
> a P5020:
Why would you base it on a upm node rather than on an ifc node, or on
the IFC binding document
(Documentation/devicetree/bindings/memory-controllers/fsl/ifc.txt)?
-Scott
next prev parent reply other threads:[~2014-08-21 0:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 0:46 [PATCH 1/2] mtd: fsl_ifc_nand: Use devm_* throughout driver Aaron Sierra
2014-08-16 0:47 ` [PATCH 2/2] mtd: fsl_ifc_nand: Probe partitions OF node Aaron Sierra
2014-08-20 23:26 ` Scott Wood
2014-08-20 23:45 ` Aaron Sierra
2014-08-20 23:59 ` Scott Wood [this message]
2014-08-21 0:15 ` Aaron Sierra
2014-08-21 0:17 ` Scott Wood
2014-09-28 0:19 ` [PATCH 1/2] mtd: fsl_ifc_nand: Use devm_* throughout driver Brian Norris
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=1408579196.4058.80.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=asierra@xes-inc.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=prabhakar@freescale.com \
/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