[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201507061512.27124@pali>
Date: Mon, 6 Jul 2015 15:12:27 +0200
From: Pali Rohár <pali.rohar@...il.com>
To: Tony Lindgren <tony@...mide.com>
Cc: Arnd Bergmann <arnd@...db.de>,
linux-arm-kernel@...ts.infradead.org,
Rob Herring <robherring2@...il.com>,
Russell King <linux@....linux.org.uk>,
Will Deacon <will.deacon@....com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@...il.com>,
Sebastian Reichel <sre@...ian.org>,
Pavel Machek <pavel@....cz>,
Andreas Färber <afaerber@...e.de>,
linux-omap@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
devicetree@...r.kernel.org
Subject: Re: [RESEND] [PATCH v2 1/2] arm: devtree: Set system_rev from DT revision
On Monday 06 July 2015 14:31:27 Tony Lindgren wrote:
> * Pali Rohár <pali.rohar@...il.com> [150706 05:25]:
> > into which file should I put documentation about new DT properties?
>
> If it's Linux generic like linux,revision, then how about
> Documentation/devicetree/bindings/revision.txt?
>
> For the ATAGs, Documentation/devicetree/bindings/arm/atag.txt?
>
> Regards,
>
> Tony
Hm... now I'm thinking into which DT field should I put atags and
revision. In previous emails you wrote to use "linux,atags", now
"arm,atags"? And put them into root node? Or other?
In arch/arm/boot/compressed/atags_to_fdt.c code I see that most atag
properties are converted into "/chosen" node in DT...
So what do you prefer for "revision" and what for "atags"?
Some mentioned examples:
"/revision"
"/chosen/revision"
"/linux,revision"
"/chosen/linux,revision"
...
"/atags"
"/chosen/atags"
"/linux,atags"
"/chosen/linux,atags"
"/arm,atags"
"/chosen/arm,atags"
...
--
Pali Rohár
pali.rohar@...il.com
Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists