From: "Pali Rohár" <pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
Cc: "Arnd Bergmann" <arnd-r2nGTMty4D4@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
"Rob Herring"
<robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Russell King" <linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
"Will Deacon" <will.deacon-5wv7dgnIgG8@public.gmane.org>,
"Ivaylo Dimitrov"
<ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"Sebastian Reichel" <sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>,
"Pavel Machek" <pavel-+ZI9xUNit7I@public.gmane.org>,
"Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RESEND] [PATCH v2 1/2] arm: devtree: Set system_rev from DT revision
Date: Mon, 6 Jul 2015 15:12:27 +0200 [thread overview]
Message-ID: <201507061512.27124@pali> (raw)
In-Reply-To: <20150706123126.GG10705-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: Text/Plain, Size: 1100 bytes --]
On Monday 06 July 2015 14:31:27 Tony Lindgren wrote:
> * Pali Rohár <pali.rohar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> [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-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: pali.rohar@gmail.com (Pali Rohár)
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 15:12:27 +0200 [thread overview]
Message-ID: <201507061512.27124@pali> (raw)
In-Reply-To: <20150706123126.GG10705@atomide.com>
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?
>
> 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 at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150706/a874ec87/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: "Pali Rohár" <pali.rohar@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
"Rob Herring" <robherring2@gmail.com>,
"Russell King" <linux@arm.linux.org.uk>,
"Will Deacon" <will.deacon@arm.com>,
"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
"Sebastian Reichel" <sre@debian.org>,
"Pavel Machek" <pavel@ucw.cz>,
"Andreas Färber" <afaerber@suse.de>,
linux-omap@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [RESEND] [PATCH v2 1/2] arm: devtree: Set system_rev from DT revision
Date: Mon, 6 Jul 2015 15:12:27 +0200 [thread overview]
Message-ID: <201507061512.27124@pali> (raw)
In-Reply-To: <20150706123126.GG10705@atomide.com>
[-- Attachment #1: Type: Text/Plain, Size: 1040 bytes --]
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?
>
> 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@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-07-06 13:12 UTC|newest]
Thread overview: 81+ 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 ` Pali Rohár
2015-05-06 8:49 ` 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 8:49 ` Pali Rohár
2015-05-06 8:49 ` Pali Rohár
2015-05-06 9:31 ` Arnd Bergmann
2015-05-06 9:31 ` Arnd Bergmann
2015-05-06 10:37 ` Pali Rohár
2015-05-06 10:37 ` Pali Rohár
2015-05-06 10:37 ` Pali Rohár
2015-05-06 11:04 ` Arnd Bergmann
2015-05-06 11:04 ` Arnd Bergmann
2015-05-06 11:44 ` Pali Rohár
2015-05-06 11:44 ` Pali Rohár
2015-05-06 11:44 ` Pali Rohár
2015-06-25 5:01 ` Tony Lindgren
2015-06-25 5:01 ` Tony Lindgren
2015-06-25 7:18 ` Pali Rohár
2015-06-25 7:18 ` Pali Rohár
2015-06-25 7:22 ` Tony Lindgren
2015-06-25 7:22 ` Tony Lindgren
2015-06-25 7:22 ` Tony Lindgren
2015-06-25 7:27 ` Pali Rohár
2015-06-25 7:27 ` Pali Rohár
2015-06-25 7:41 ` Tony Lindgren
2015-06-25 7:41 ` Tony Lindgren
2015-06-25 7:41 ` Tony Lindgren
[not found] ` <20150625050138.GL4156-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-07-06 12:23 ` Pali Rohár
2015-07-06 12:23 ` Pali Rohár
2015-07-06 12:23 ` Pali Rohár
2015-07-06 12:31 ` Tony Lindgren
2015-07-06 12:31 ` Tony Lindgren
[not found] ` <20150706123126.GG10705-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2015-07-06 13:12 ` Pali Rohár [this message]
2015-07-06 13:12 ` Pali Rohár
2015-07-06 13:12 ` Pali Rohár
2015-07-06 13:55 ` Tony Lindgren
2015-07-06 13:55 ` Tony Lindgren
2015-07-06 13:55 ` Tony Lindgren
2015-07-06 15:22 ` Rob Herring
2015-07-06 15:22 ` Rob Herring
[not found] ` <CAL_Jsq+ysDqxTgfW1JvG5czHa4UkZQDv1BN63iK4jvV9kDXM8w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-06 16:20 ` Pali Rohár
2015-07-06 16:20 ` Pali Rohár
2015-07-06 16:20 ` Pali Rohár
2015-07-06 16:36 ` Pali Rohár
2015-07-06 16:36 ` Pali Rohár
2015-07-06 17:30 ` Rob Herring
2015-07-06 17:30 ` Rob Herring
2015-07-06 15:20 ` Rob Herring
2015-07-06 15:20 ` Rob Herring
2015-07-06 15:24 ` Tony Lindgren
2015-07-06 15:24 ` Tony Lindgren
2015-06-25 10:03 ` Russell King - ARM Linux
2015-06-25 10:03 ` Russell King - ARM Linux
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-06 8:49 ` Pali Rohár
2015-05-06 8:49 ` 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 ` Pali Rohár
2015-05-15 19:50 ` 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 19:50 ` Pali Rohár
2015-05-15 20:09 ` Arnd Bergmann
2015-05-15 20:09 ` Arnd Bergmann
2015-06-25 5:06 ` Tony Lindgren
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 19:50 ` Pali Rohár
2015-05-15 20:12 ` Arnd Bergmann
2015-05-15 20:12 ` Arnd Bergmann
2015-05-15 20:12 ` Arnd Bergmann
2015-05-15 20:16 ` Pali Rohár
2015-05-15 20:16 ` Pali Rohár
2015-05-15 20:21 ` Arnd Bergmann
2015-05-15 20:21 ` Arnd Bergmann
2015-05-15 20:21 ` Arnd Bergmann
2015-06-25 5:12 ` Tony Lindgren
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
2015-06-25 10:02 ` 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=201507061512.27124@pali \
--to=pali.rohar-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=afaerber-l3A5Bk7waGM@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ivo.g.dimitrov.75-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pavel-+ZI9xUNit7I@public.gmane.org \
--cc=robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=sre-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.