From: "Andreas Färber" <afaerber@suse.de>
To: linux-amlogic@lists.infradead.org
Cc: "Carlo Caione" <carlo@caione.org>,
"Kevin Hilman" <khilman@baylibre.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Andreas Färber" <afaerber@suse.de>,
ada@kingnoval.com, "Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org
Subject: [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro
Date: Tue, 17 Jan 2017 23:54:58 +0100 [thread overview]
Message-ID: <20170117225459.4438-2-afaerber@suse.de> (raw)
In-Reply-To: <20170117225459.4438-1-afaerber@suse.de>
Cc: ada@kingnoval.com
Signed-off-by: Andreas Färber <afaerber@suse.de>
---
Originally I thought we would group by SoC (6, 8, 8b, gxbb, gxl, gmx, etc.)
but this got out of order with nexbox,a95x - so inserting kingnovel between
amlogic and nexbox here. If that's what we want going forward, we should move
the old entries to make the scheme clearer. The alternative would be to
reorder alphabetically within each SoC group, but nexbox,a95x with two SoCs
makes it difficult to categorize, we could choose gxbb as the earlier one.
Documentation/devicetree/bindings/arm/amlogic.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt b/Documentation/devicetree/bindings/arm/amlogic.txt
index 9b2b41ab6817..fb0ee7d9a921 100644
--- a/Documentation/devicetree/bindings/arm/amlogic.txt
+++ b/Documentation/devicetree/bindings/arm/amlogic.txt
@@ -45,5 +45,6 @@ Board compatible values:
- "amlogic,p231" (Meson gxl s905d)
- "amlogic,q200" (Meson gxm s912)
- "amlogic,q201" (Meson gxm s912)
+ - "kingnovel,r-box-pro" (Meson gxm S912)
- "nexbox,a95x" (Meson gxbb or Meson gxl s905x)
- "nexbox,a1" (Meson gxm s912)
--
2.10.2
WARNING: multiple messages have this Message-ID (diff)
From: afaerber@suse.de (Andreas Färber)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro
Date: Tue, 17 Jan 2017 23:54:58 +0100 [thread overview]
Message-ID: <20170117225459.4438-2-afaerber@suse.de> (raw)
In-Reply-To: <20170117225459.4438-1-afaerber@suse.de>
Cc: ada at kingnoval.com
Signed-off-by: Andreas F?rber <afaerber@suse.de>
---
Originally I thought we would group by SoC (6, 8, 8b, gxbb, gxl, gmx, etc.)
but this got out of order with nexbox,a95x - so inserting kingnovel between
amlogic and nexbox here. If that's what we want going forward, we should move
the old entries to make the scheme clearer. The alternative would be to
reorder alphabetically within each SoC group, but nexbox,a95x with two SoCs
makes it difficult to categorize, we could choose gxbb as the earlier one.
Documentation/devicetree/bindings/arm/amlogic.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt b/Documentation/devicetree/bindings/arm/amlogic.txt
index 9b2b41ab6817..fb0ee7d9a921 100644
--- a/Documentation/devicetree/bindings/arm/amlogic.txt
+++ b/Documentation/devicetree/bindings/arm/amlogic.txt
@@ -45,5 +45,6 @@ Board compatible values:
- "amlogic,p231" (Meson gxl s905d)
- "amlogic,q200" (Meson gxm s912)
- "amlogic,q201" (Meson gxm s912)
+ - "kingnovel,r-box-pro" (Meson gxm S912)
- "nexbox,a95x" (Meson gxbb or Meson gxl s905x)
- "nexbox,a1" (Meson gxm s912)
--
2.10.2
WARNING: multiple messages have this Message-ID (diff)
From: afaerber@suse.de (Andreas Färber)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro
Date: Tue, 17 Jan 2017 23:54:58 +0100 [thread overview]
Message-ID: <20170117225459.4438-2-afaerber@suse.de> (raw)
In-Reply-To: <20170117225459.4438-1-afaerber@suse.de>
Cc: ada at kingnoval.com
Signed-off-by: Andreas F?rber <afaerber@suse.de>
---
Originally I thought we would group by SoC (6, 8, 8b, gxbb, gxl, gmx, etc.)
but this got out of order with nexbox,a95x - so inserting kingnovel between
amlogic and nexbox here. If that's what we want going forward, we should move
the old entries to make the scheme clearer. The alternative would be to
reorder alphabetically within each SoC group, but nexbox,a95x with two SoCs
makes it difficult to categorize, we could choose gxbb as the earlier one.
Documentation/devicetree/bindings/arm/amlogic.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/amlogic.txt b/Documentation/devicetree/bindings/arm/amlogic.txt
index 9b2b41ab6817..fb0ee7d9a921 100644
--- a/Documentation/devicetree/bindings/arm/amlogic.txt
+++ b/Documentation/devicetree/bindings/arm/amlogic.txt
@@ -45,5 +45,6 @@ Board compatible values:
- "amlogic,p231" (Meson gxl s905d)
- "amlogic,q200" (Meson gxm s912)
- "amlogic,q201" (Meson gxm s912)
+ - "kingnovel,r-box-pro" (Meson gxm S912)
- "nexbox,a95x" (Meson gxbb or Meson gxl s905x)
- "nexbox,a1" (Meson gxm s912)
--
2.10.2
next prev parent reply other threads:[~2017-01-17 22:55 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 3:06 [PATCH 0/2] ARM64: meson-gxm: R-Box Pro enablement Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-17 3:35 ` Andreas Färber
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-18 22:18 ` Kevin Hilman
2017-01-17 22:54 ` [PATCH 1/3] Documentation: devicetree: Add Kingnovel vendor prefix Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber [this message]
2017-01-17 22:54 ` [PATCH 2/3] Documentation: devicetree: amlogic: Add R-Box Pro Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 9:35 ` Neil Armstrong
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 22:38 ` Andreas Färber
2017-01-18 23:38 ` Kevin Hilman
2017-01-18 23:38 ` Kevin Hilman
2017-01-18 23:38 ` Kevin Hilman
2017-01-18 23:38 ` Kevin Hilman
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-21 20:02 ` Rob Herring
2017-01-17 22:54 ` [PATCH 3/3] ARM64: dts: meson-gxm-rbox-pro: Add board compatible string Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-17 22:54 ` Andreas Färber
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:21 ` Kevin Hilman
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-23 18:32 ` Andreas Färber
2017-01-21 20:01 ` [PATCH 1/3] Documentation: devicetree: Add Kingnovel vendor prefix Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-21 20:01 ` Rob Herring
2017-01-17 23:06 ` [PATCH 1/2] ARM64: dts: meson-gxm: Add R-Box Pro Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-17 23:06 ` Andreas Färber
2017-01-18 22:27 ` Kevin Hilman
2017-01-18 22:27 ` Kevin Hilman
2017-01-18 22:27 ` Kevin Hilman
2017-01-19 8:10 ` Neil Armstrong
2017-01-19 8:10 ` Neil Armstrong
2017-01-19 8:10 ` Neil Armstrong
2017-01-17 3:06 ` [PATCH 2/2] ARM64: dts: meson-gxm-rbox-pro: Enable Bluetooth Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-17 3:06 ` Andreas Färber
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` Kevin Hilman
2017-01-18 22:29 ` 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=20170117225459.4438-2-afaerber@suse.de \
--to=afaerber@suse.de \
--cc=ada@kingnoval.com \
--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+dt@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 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.