atmel nand bindings vs. actual dts files

Alexander Dahl ada at thorsis.com
Tue Apr 30 02:24:44 PDT 2019


Hello Miquèl,

Am Montag, 29. April 2019, 11:55:40 CEST schrieb Miquel Raynal:
> Alexander Dahl <ada at 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 at 3 {
		reg = <0x3 0x0 0x800000>;

Others have this:

	nand at 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




More information about the linux-mtd mailing list