From: Johan Jonker <jbx6244@gmail.com>
To: heiko@sntech.de
Cc: robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH v1 1/2] dt-bindings: arm: rockchip: add A95X Z2 description
Date: Sat, 20 Jun 2020 15:46:58 +0200 [thread overview]
Message-ID: <20200620134659.4592-2-jbx6244@gmail.com> (raw)
In-Reply-To: <20200620134659.4592-1-jbx6244@gmail.com>
Add A95X Z2 description for a board with rk3318 processor.
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index d4a404509..3d44b3cf0 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -25,6 +25,11 @@ properties:
- const: vamrs,rock960
- const: rockchip,rk3399
+ - description: A95X Z2
+ items:
+ - const: a95x,z2
+ - const: rockchip,rk3318
+
- description: Amarula Vyasa RK3288
items:
- const: amarula,vyasa-rk3288
--
2.11.0
WARNING: multiple messages have this Message-ID (diff)
From: Johan Jonker <jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org
Cc: robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [RFC PATCH v1 1/2] dt-bindings: arm: rockchip: add A95X Z2 description
Date: Sat, 20 Jun 2020 15:46:58 +0200 [thread overview]
Message-ID: <20200620134659.4592-2-jbx6244@gmail.com> (raw)
In-Reply-To: <20200620134659.4592-1-jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Add A95X Z2 description for a board with rk3318 processor.
Signed-off-by: Johan Jonker <jbx6244-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index d4a404509..3d44b3cf0 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -25,6 +25,11 @@ properties:
- const: vamrs,rock960
- const: rockchip,rk3399
+ - description: A95X Z2
+ items:
+ - const: a95x,z2
+ - const: rockchip,rk3318
+
- description: Amarula Vyasa RK3288
items:
- const: amarula,vyasa-rk3288
--
2.11.0
WARNING: multiple messages have this Message-ID (diff)
From: Johan Jonker <jbx6244@gmail.com>
To: heiko@sntech.de
Cc: linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: [RFC PATCH v1 1/2] dt-bindings: arm: rockchip: add A95X Z2 description
Date: Sat, 20 Jun 2020 15:46:58 +0200 [thread overview]
Message-ID: <20200620134659.4592-2-jbx6244@gmail.com> (raw)
In-Reply-To: <20200620134659.4592-1-jbx6244@gmail.com>
Add A95X Z2 description for a board with rk3318 processor.
Signed-off-by: Johan Jonker <jbx6244@gmail.com>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index d4a404509..3d44b3cf0 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -25,6 +25,11 @@ properties:
- const: vamrs,rock960
- const: rockchip,rk3399
+ - description: A95X Z2
+ items:
+ - const: a95x,z2
+ - const: rockchip,rk3318
+
- description: Amarula Vyasa RK3288
items:
- const: amarula,vyasa-rk3288
--
2.11.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-20 13:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-20 13:46 [RFC PATCH v1 0/2] rk3318 A95X Z2 board Johan Jonker
2020-06-20 13:46 ` Johan Jonker
2020-06-20 13:46 ` Johan Jonker
2020-06-20 13:46 ` Johan Jonker [this message]
2020-06-20 13:46 ` [RFC PATCH v1 1/2] dt-bindings: arm: rockchip: add A95X Z2 description Johan Jonker
2020-06-20 13:46 ` Johan Jonker
2020-07-15 19:29 ` Rob Herring
2020-07-15 19:29 ` Rob Herring
2020-07-15 19:29 ` Rob Herring
2020-07-16 12:05 ` Johan Jonker
2020-07-16 12:05 ` Johan Jonker
2020-07-16 12:05 ` Johan Jonker
2020-07-16 13:34 ` Robin Murphy
2020-07-16 13:34 ` Robin Murphy
2020-07-16 16:11 ` Johan Jonker
2020-07-16 16:11 ` Johan Jonker
2020-07-16 16:11 ` Johan Jonker
2020-07-16 19:18 ` Robin Murphy
2020-07-16 19:18 ` Robin Murphy
2020-07-16 19:18 ` Robin Murphy
2020-06-20 13:46 ` [RFC PATCH v1 2/2] arm64: dts: rockchip: add rk3318 A95X Z2 board Johan Jonker
2020-06-20 13:46 ` Johan Jonker
2020-06-20 13:46 ` Johan Jonker
2020-06-22 8:01 ` [RFC PATCH v1 0/2] " Johan Jonker
2020-06-22 8:01 ` Johan Jonker
2020-06-25 8:38 ` Johan Jonker
2020-06-25 8:38 ` Johan Jonker
2020-06-25 8:38 ` Johan Jonker
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=20200620134659.4592-2-jbx6244@gmail.com \
--to=jbx6244@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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.