From: Dongjin Kim <tobetter@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] dt-bindings: rockchip: Add Hardkernel ODROID-M1 board
Date: Tue, 29 Mar 2022 18:44:45 +0900 [thread overview]
Message-ID: <20220329094446.415219-1-tobetter@gmail.com> (raw)
Add device tree binding for Hardkernel ODROID-M1 board based on RK3568
SoC.
Signed-off-by: Dongjin Kim <tobetter@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 eece92f83a2d..48fd0858a795 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -664,6 +664,11 @@ properties:
- const: rockchip,rk3568-bpi-r2pro
- const: rockchip,rk3568
+ - description: Rockchip RK3568 Hardkernel ODROID-M1
+ items:
+ - const: rockchip,rk3568-odroid-m1
+ - const: rockchip,rk3568
+
additionalProperties: true
...
--
2.32.0
WARNING: multiple messages have this Message-ID (diff)
From: Dongjin Kim <tobetter@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] dt-bindings: rockchip: Add Hardkernel ODROID-M1 board
Date: Tue, 29 Mar 2022 18:44:45 +0900 [thread overview]
Message-ID: <20220329094446.415219-1-tobetter@gmail.com> (raw)
Add device tree binding for Hardkernel ODROID-M1 board based on RK3568
SoC.
Signed-off-by: Dongjin Kim <tobetter@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 eece92f83a2d..48fd0858a795 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -664,6 +664,11 @@ properties:
- const: rockchip,rk3568-bpi-r2pro
- const: rockchip,rk3568
+ - description: Rockchip RK3568 Hardkernel ODROID-M1
+ items:
+ - const: rockchip,rk3568-odroid-m1
+ - const: rockchip,rk3568
+
additionalProperties: true
...
--
2.32.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Dongjin Kim <tobetter@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] dt-bindings: rockchip: Add Hardkernel ODROID-M1 board
Date: Tue, 29 Mar 2022 18:44:45 +0900 [thread overview]
Message-ID: <20220329094446.415219-1-tobetter@gmail.com> (raw)
Add device tree binding for Hardkernel ODROID-M1 board based on RK3568
SoC.
Signed-off-by: Dongjin Kim <tobetter@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 eece92f83a2d..48fd0858a795 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -664,6 +664,11 @@ properties:
- const: rockchip,rk3568-bpi-r2pro
- const: rockchip,rk3568
+ - description: Rockchip RK3568 Hardkernel ODROID-M1
+ items:
+ - const: rockchip,rk3568-odroid-m1
+ - const: rockchip,rk3568
+
additionalProperties: true
...
--
2.32.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-03-29 9:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 9:44 Dongjin Kim [this message]
2022-03-29 9:44 ` [PATCH 1/2] dt-bindings: rockchip: Add Hardkernel ODROID-M1 board Dongjin Kim
2022-03-29 9:44 ` Dongjin Kim
2022-03-29 9:44 ` [PATCH 2/2] arm64: dts: " Dongjin Kim
2022-03-29 9:44 ` Dongjin Kim
2022-03-29 9:44 ` Dongjin Kim
2022-03-29 17:12 ` Krzysztof Kozlowski
2022-03-29 17:12 ` Krzysztof Kozlowski
2022-03-29 17:12 ` Krzysztof Kozlowski
2022-04-05 2:32 ` Dongjin Kim
2022-04-05 2:32 ` Dongjin Kim
2022-04-05 2:32 ` Dongjin Kim
2022-04-05 6:13 ` Krzysztof Kozlowski
2022-04-05 6:13 ` Krzysztof Kozlowski
2022-04-05 6:13 ` Krzysztof Kozlowski
2022-04-16 12:07 ` Peter Geis
2022-04-16 12:07 ` Peter Geis
2022-04-16 12:07 ` Peter Geis
2022-04-17 17:45 ` Krzysztof Kozlowski
2022-04-17 17:45 ` Krzysztof Kozlowski
2022-04-17 17:45 ` Krzysztof Kozlowski
2022-04-17 20:55 ` Heiko Stuebner
2022-04-17 20:55 ` Heiko Stuebner
2022-04-17 20:55 ` Heiko Stuebner
2022-04-18 11:21 ` Krzysztof Kozlowski
2022-04-18 11:21 ` Krzysztof Kozlowski
2022-04-18 11:21 ` Krzysztof Kozlowski
2022-04-18 11:46 ` Peter Geis
2022-04-18 11:46 ` Peter Geis
2022-04-18 11:46 ` Peter Geis
2022-04-04 18:10 ` [PATCH 1/2] dt-bindings: " Rob Herring
2022-04-04 18:10 ` Rob Herring
2022-04-04 18:10 ` Rob Herring
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=20220329094446.415219-1-tobetter@gmail.com \
--to=tobetter@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 \
/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.