From: Aaron Sierra <asierra@xes-inc.com>
To: Scott Wood <scottwood@freescale.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:45:33 -0500 (CDT) [thread overview]
Message-ID: <917570204.96674.1408578333042.JavaMail.zimbra@xes-inc.com> (raw)
In-Reply-To: <1408577185.4058.77.camel@snotra.buserror.net>
----- 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>;
};
};
};
It is based on a node used previously with the fsl_upm NAND driver on
a P5020:
upm@4,0 {
#address-cells = <0>;
#size-cells = <0>;
compatible = "fsl,upm-nand";
reg = <4 0x0 0x080000>;
fsl,upm-addr-offset = <0x10>;
fsl,upm-cmd-offset = <0x08>;
fsl,upm-wait-flags = <0x1>;
chip-delay = <50>;
nand@0 {
#address-cells = <1>;
#size-cells = <2>;
compatible = "micron,mt29f32g08";
partition@0 {
label = "NAND Filesystem";
reg = <0 0x1 0x00000000>;
};
};
};
The patch that I submitted is based on code from the fsl_upm driver:
flash_np = of_get_next_child(upm_np, NULL);
if (!flash_np)
return -ENODEV;
[snip]
ppdata.of_node = flash_np;
ret = mtd_device_parse_register(&fun->mtd, NULL, &ppdata, NULL, 0);
err:
of_node_put(flash_np);
-Aaron
next prev parent reply other threads:[~2014-08-20 23:45 UTC|newest]
Thread overview: 9+ 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 [this message]
2014-08-20 23:59 ` Scott Wood
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
2014-09-28 0:19 ` 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=917570204.96674.1408578333042.JavaMail.zimbra@xes-inc.com \
--to=asierra@xes-inc.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=prabhakar@freescale.com \
--cc=scottwood@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.