From: "Andreas Färber" <afaerber@suse.de>
To: Rob Herring <robh@kernel.org>
Cc: linux-amlogic@lists.infradead.org,
Carlo Caione <carlo@caione.org>,
Kevin Hilman <khilman@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 01/18] Documentation: devicetree: amlogic: Reorder boards
Date: Mon, 23 Jan 2017 19:36:08 +0100 [thread overview]
Message-ID: <31ca7ebb-6101-891f-e8c4-298635d1979e@suse.de> (raw)
In-Reply-To: <20170123164831.ux2kkofq7xf2whnp@rob-hp-laptop>
Am 23.01.2017 um 17:48 schrieb Rob Herring:
> On Fri, Jan 20, 2017 at 11:21:01PM +0100, Andreas Färber wrote:
>> Enforce groupment by SoCs and order alphabetically within the group
>> (with some exceptions). This should facilitate adding new boards.
>>
>> Signed-off-by: Andreas Färber <afaerber@suse.de>
>> ---
>> Documentation/devicetree/bindings/arm/amlogic.txt | 19 +++++++++++++------
>> 1 file changed, 13 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt b/Documentation/devicetree/bindings/arm/amlogic.txt
>> index c246cd2730d9..b03d23c9ea78 100644
>> --- a/Documentation/devicetree/bindings/arm/amlogic.txt
>> +++ b/Documentation/devicetree/bindings/arm/amlogic.txt
>> @@ -29,23 +29,30 @@ Boards with the Amlogic Meson GXM S912 SoC shall have the following properties:
>> Required root node property:
>> compatible: "amlogic,s912", "amlogic,meson-gxm";
>>
>> -Board compatible values:
>> +Board compatible values (grouped by SoC):
>
> ...and alphabetical order within each SoC.
...except for pro, meta, telos, which are in increasing feature set
order - should we reorder them, or ignore but still write alphabetical?
Regards,
Andreas
>
>> +
>> - "geniatech,atv1200" (Meson6)
>> +
>> - "minix,neo-x8" (Meson8)
>> - - "tronfy,mxq" (Meson8b)
>> +
>> - "hardkernel,odroid-c1" (Meson8b)
>> + - "tronfy,mxq" (Meson8b)
>> +
>> + - "amlogic,p200" (Meson gxbb)
>> + - "amlogic,p201" (Meson gxbb)
>> + - "hardkernel,odroid-c2" (Meson gxbb)
>> + - "nexbox,a95x" (Meson gxbb or Meson gxl s905x)
>> - "tronsmart,vega-s95-pro", "tronsmart,vega-s95" (Meson gxbb)
>> - "tronsmart,vega-s95-meta", "tronsmart,vega-s95" (Meson gxbb)
>> - "tronsmart,vega-s95-telos", "tronsmart,vega-s95" (Meson gxbb)
>> - - "hardkernel,odroid-c2" (Meson gxbb)
>> - - "amlogic,p200" (Meson gxbb)
>> - - "amlogic,p201" (Meson gxbb)
>> - "wetek,hub" (Meson gxbb)
>> - "wetek,play2" (Meson gxbb)
>> +
>> - "amlogic,p212" (Meson gxl s905x)
>> +
>> - "amlogic,p230" (Meson gxl s905d)
>> - "amlogic,p231" (Meson gxl s905d)
>> +
>> - "amlogic,q200" (Meson gxm s912)
>> - "amlogic,q201" (Meson gxm s912)
>> - - "nexbox,a95x" (Meson gxbb or Meson gxl s905x)
>> - "nexbox,a1" (Meson gxm s912)
>> --
>> 2.10.2
>>
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-01-23 18:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 22:21 [PATCH 00/18] ARM64: meson: DT cleanups Andreas Färber
2017-01-20 22:21 ` [PATCH 01/18] Documentation: devicetree: amlogic: Reorder boards Andreas Färber
2017-01-23 16:48 ` Rob Herring
2017-01-23 18:36 ` Andreas Färber [this message]
2017-01-20 22:21 ` [PATCH 02/18] ARM64: dts: amlogic: Sort Makefile Andreas Färber
2017-01-20 22:21 ` [PATCH 03/18] ARM64: dts: meson-gxbb-vega-s95: Fix Wifi node name Andreas Färber
2017-01-20 22:21 ` [PATCH 04/18] ARM64: dts: meson-gxbb-p20x: " Andreas Färber
2017-01-23 8:55 ` Neil Armstrong
2017-01-23 16:50 ` Rob Herring
2017-01-23 16:57 ` Andreas Färber
2017-01-20 22:21 ` [PATCH 05/18] ARM64: dts: meson-gx-p23x-q20x: " Andreas Färber
2017-01-23 8:55 ` Neil Armstrong
2017-01-20 22:21 ` [PATCH 06/18] ARM64: dts: meson-gxm-nexbox-a1: Drop UART comment Andreas Färber
2017-01-23 8:55 ` Neil Armstrong
2017-01-20 22:21 ` [PATCH 07/18] ARM64: dts: meson-gxl-s905x: Comment typo fix Andreas Färber
2017-01-23 8:56 ` Neil Armstrong
2017-01-20 22:21 ` [PATCH 08/18] ARM64: dts: meson-gxm: Drop trailing white line Andreas Färber
2017-01-20 22:21 ` [PATCH 09/18] ARM64: dts: meson-gxbb-wetek-hub: Reference CVBS node by label Andreas Färber
2017-01-20 22:21 ` [PATCH 10/18] ARM64: dts: meson-gxbb: Reorder nodes Andreas Färber
2017-01-23 16:52 ` Rob Herring
2017-01-23 16:56 ` Andreas Färber
2017-01-30 14:59 ` Russell King - ARM Linux
2017-01-20 22:21 ` [PATCH 11/18] ARM64: dts: meson-gxbb-odroidc2: " Andreas Färber
2017-01-20 22:21 ` [PATCH 12/18] ARM64: dts: meson-gxbb-vega-s95: " Andreas Färber
2017-01-20 22:21 ` [PATCH 13/18] ARM64: dts: meson-gxbb-nexbox-a95x: " Andreas Färber
2017-01-23 8:57 ` Neil Armstrong
2017-01-20 22:21 ` [PATCH 14/18] ARM64: dts: meson-gxbb-p20x: " Andreas Färber
2017-01-20 22:21 ` [PATCH 15/18] ARM64: dts: meson-gxl: " Andreas Färber
2017-01-23 8:57 ` Neil Armstrong
2017-01-20 22:21 ` [PATCH 16/18] ARM64: dts: meson-gxl-s905x-nexbox-a95x: " Andreas Färber
2017-01-23 8:58 ` Neil Armstrong
2017-01-20 22:21 ` [PATCH 17/18] ARM64: dts: meson-gxm-nexbox-a1: " Andreas Färber
2017-01-23 8:58 ` Neil Armstrong
2017-01-20 22:21 ` [PATCH 18/18] ARM64: dts: meson-gx-p23x-q20x: " Andreas Färber
2017-01-23 8:58 ` Neil Armstrong
2017-01-23 18:46 ` [PATCH 00/18] ARM64: meson: DT cleanups Kevin Hilman
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=31ca7ebb-6101-891f-e8c4-298635d1979e@suse.de \
--to=afaerber@suse.de \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@kernel.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).