From: Alexander Dahl <ada@thorsis.com>
To: linux-mtd@lists.infradead.org
Cc: Boris Brezillon <bbrezillon@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: atmel nand bindings vs. actual dts files
Date: Tue, 30 Apr 2019 11:24:44 +0200 [thread overview]
Message-ID: <1947914.CcHDgmXbBm@ada> (raw)
In-Reply-To: <20190429115540.7d577a50@xps13>
Hello Miquèl,
Am Montag, 29. April 2019, 11:55:40 CEST schrieb Miquel Raynal:
> Alexander Dahl <ada@thorsis.com> wrote on Thu, 07 Mar 2019 17:25:17
> > Am Mittwoch, 6. März 2019, 15:07:52 CET schrieb Alexander Dahl:
> > > So instead of "always 0x800000" that node has 0x2 as third entry for the
> > > 'reg' property. Why is that?
> >
> > I didn't investigate that further yet, but I'm curious, so if anyone
> > knows?
>
> I suppose the bindings [1] explain the situation.
>
> [1]
> https://elixir.bootlin.com/linux/v5.0/source/Documentation/devicetree/bindi
> ngs/mtd/atmel-nand.txt#L32
No, that was not what I wanted to know. The bindings says for that reg
property: “3rd entry: the memory region size (always 0x800000)”
This is true for some dts files including this nand node, but not for all,
some have this:
nand@3 {
reg = <0x3 0x0 0x800000>;
Others have this:
nand@3 {
reg = <0x3 0x0 0x2>;
The second contradicts the binding doc. Most of this was changed when
switching from the old bindings in changeset v4.12-rc1-7-g1004a2977bdc by
Boris Brezillon. I wanted to know why the difference?
Greets
Alex
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-04-30 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 14:07 atmel nand bindings vs. actual dts files Alexander Dahl
2019-03-07 16:25 ` Alexander Dahl
2019-04-29 9:55 ` Miquel Raynal
2019-04-30 9:24 ` Alexander Dahl [this message]
2019-04-30 9:32 ` Miquel Raynal
2019-06-04 1:53 ` Alexandre Belloni
2019-06-04 7:43 ` Boris Brezillon
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=1947914.CcHDgmXbBm@ada \
--to=ada@thorsis.com \
--cc=bbrezillon@kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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;
as well as URLs for NNTP newsgroup(s).