From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: Kirkwood: DT board setup for LaPlug
Date: Mon, 23 Dec 2013 13:48:27 -0300 [thread overview]
Message-ID: <20131223164826.GA6535@localhost> (raw)
In-Reply-To: <CAGduivwCtQr-6sY92jEydU6uG1QJOSQcqxAKwcxr4viV38vU-Q@mail.gmail.com>
Hi Maxime,
On Mon, Dec 23, 2013 at 04:47:34PM +0100, Maxime Hadjinlian wrote:
> I have a slight issue which I could not resolve regarding the Hynix
> NAND on this platform. Although it worked perfectly well with 3.12,
> the device is not detected anymore with the current head of master.
>
If you do a "git log v3.12..v3.13-rc4 -- drivers/mtd/nand/orion_nand.c"
you'll see that no changes have been made.
So maybe this new dts v2 is the problem. And if you look in detail you'll
find you've been bitten by the subtleties of the devicetree!
See below...
> > + mbus {
> > + ranges = <MBUS_ID(0xf0, 0x01) 0 0xf1000000 0x100000>;
> > + pcie-controller {
> > + status = "okay";
> > + pcie at 1,0 {
> > + status = "okay";
> > + };
> > + };
> > + };
^^^^
Here's the problem: there's two wrong things with the above:
1. You can't do this... a ranges properties doesn't add on the included
(dtsi) ranges properties. Instead it replaces the included one, so you have
to write the entries all over again.
Yes, we know: it sucks! And given we know it sucks, there was a nice
message warning you about this. From the kirkwood.dtsi
/* If a board file needs to change this ranges it must replace it completely */
ranges = <MBUS_ID(0xf0, 0x01) 0 0xf1000000 0x100000 /* internal-regs */
MBUS_ID(0x01, 0x2f) 0 0xf4000000 0x10000 /* nand flash */
MBUS_ID(0x03, 0x01) 0 0xf5000000 0x10000 /* crypto sram */
>;
2. Looking in yet more detail, you're re-adding the internal-regs window.
I guess it's just a typo, no?
Anyway, I *think* that's what prevented you from getting the NAND to
work. The correct mbus node should be:
mbus {
pcie-controller {
status = "okay";
pcie at 1,0 {
status = "okay";
};
};
};
> > +&nand {
> > + /* Total size : 512MB */
> > + status = "okay";
> > +
And here: don't you need to add the pinmuxing? Maybe you don't need it,
but I guess it's the right thing to do.
I hope this helps!
Merry Christmas...
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-12-23 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 15:42 [PATCH 1/2] ARM: Kirkwood: Add 6192 DTSI file Maxime Hadjinlian
2013-12-23 15:42 ` [PATCH 2/2] ARM: Kirkwood: DT board setup for LaPlug Maxime Hadjinlian
2013-12-23 15:47 ` Maxime Hadjinlian
2013-12-23 16:05 ` Andrew Lunn
2013-12-23 16:48 ` Ezequiel Garcia [this message]
2013-12-24 11:17 ` Maxime Hadjinlian
2013-12-23 16:02 ` Andrew Lunn
2013-12-23 15:56 ` [PATCH 1/2] ARM: Kirkwood: Add 6192 DTSI file Andrew Lunn
2013-12-23 16:04 ` Maxime Hadjinlian
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=20131223164826.GA6535@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).