linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND] [PATCH v2 1/2] arm: devtree: Set system_rev from DT revision
Date: Mon, 6 Jul 2015 06:55:06 -0700	[thread overview]
Message-ID: <20150706135506.GI10705@atomide.com> (raw)
In-Reply-To: <201507061512.27124@pali>

* Pali Roh?r <pali.rohar@gmail.com> [150706 06:14]:
> On Monday 06 July 2015 14:31:27 Tony Lindgren wrote:
> > * Pali Roh?r <pali.rohar@gmail.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?
>
> 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"?

I'd prefer linux,revision and arm,atags. Chances are the ATAGs
won't be used on other architectures. I'm find with linux,atags
too if people prefer that.

Regards,

Tony
 
> 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 at gmail.com

  reply	other threads:[~2015-07-06 13:55 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  8:49 [RESEND] [PATCH v2 0/2] ARM: /proc/cpuinfo: DT: Add support for Revision Pali Rohár
2015-05-06  8:49 ` [RESEND] [PATCH v2 1/2] arm: devtree: Set system_rev from DT revision Pali Rohár
2015-05-06  9:31   ` Arnd Bergmann
2015-05-06 10:37     ` Pali Rohár
2015-05-06 11:04       ` Arnd Bergmann
2015-05-06 11:44         ` Pali Rohár
2015-06-25  5:01           ` Tony Lindgren
2015-06-25  7:18             ` Pali Rohár
2015-06-25  7:22               ` Tony Lindgren
2015-06-25  7:27                 ` Pali Rohár
2015-06-25  7:41                   ` Tony Lindgren
2015-07-06 12:23             ` Pali Rohár
2015-07-06 12:31               ` Tony Lindgren
2015-07-06 13:12                 ` Pali Rohár
2015-07-06 13:55                   ` Tony Lindgren [this message]
2015-07-06 15:22                   ` Rob Herring
2015-07-06 16:20                     ` Pali Rohár
2015-07-06 16:36                       ` Pali Rohár
2015-07-06 17:30                       ` Rob Herring
2015-07-06 15:20                 ` Rob Herring
2015-07-06 15:24                   ` Tony Lindgren
2015-06-25 10:03           ` Russell King - ARM Linux
2015-05-06  8:49 ` [RESEND] [PATCH v2 2/2] arm: boot: convert ATAG_REVISION to DT revision field Pali Rohár
2015-05-15 19:50 ` [PATCH 0/2] ARM: /proc/atags: Export also for DT Pali Rohár
2015-05-15 19:50   ` [PATCH 1/2] arm: devtree: Save atags if are in DT atags field Pali Rohár
2015-05-15 20:09     ` Arnd Bergmann
2015-06-25  5:06       ` Tony Lindgren
2015-05-15 19:50   ` [PATCH 2/2] arm: boot: store ATAG structure into " Pali Rohár
2015-05-15 20:12     ` Arnd Bergmann
2015-05-15 20:16       ` Pali Rohár
2015-05-15 20:21         ` Arnd Bergmann
2015-06-25  5:12           ` Tony Lindgren
2015-06-25 10:02   ` [PATCH 0/2] ARM: /proc/atags: Export also for DT Russell King - ARM Linux

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=20150706135506.GI10705@atomide.com \
    --to=tony@atomide.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).