From: Shimrra Shai <shimrrashai@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, heiko@sntech.de,
krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-pm@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh@kernel.org, Shimrra Shai <shimrrashai@gmail.com>
Subject: [PATCH v4 1/2] dt-bindings: arm: rockchip: Add Firefly ITX-3588J board
Date: Mon, 16 Dec 2024 15:41:51 -0600 [thread overview]
Message-ID: <20241216214152.58387-2-shimrrashai@gmail.com> (raw)
In-Reply-To: <20241216214152.58387-1-shimrrashai@gmail.com>
Document board compatible bindings.
Signed-off-by: Shimrra Shai <shimrrashai@gmail.com>
---
Documentation/devicetree/bindings/arm/rockchip.yaml | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
index 753199a12..fc7ee86e2 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -167,6 +167,13 @@ properties:
- const: engicam,px30-core
- const: rockchip,px30
+ - description: Firefly Core-3588J-based boards
+ items:
+ - enum:
+ - firefly,itx-3588j
+ - const: firefly,core-3588j
+ - const: rockchip,rk3588
+
- description: Firefly Core-PX30-JD4 on MB-JD4-PX30 baseboard
items:
- const: firefly,px30-jd4-core-mb
--
2.45.2
next prev parent reply other threads:[~2024-12-16 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 21:41 [PATCH v4 0/2] arm64: dts: rockchip: Add Firefly ITX-3588J Board Shimrra Shai
2024-12-16 21:41 ` Shimrra Shai [this message]
2024-12-17 6:01 ` [PATCH v4 1/2] dt-bindings: arm: rockchip: Add Firefly ITX-3588J board Krzysztof Kozlowski
2025-01-09 23:03 ` Heiko Stübner
2024-12-16 21:41 ` [PATCH v4 2/2] arm64: dts: rockchip: add DTs for Firefly ITX-3588J and its Core-3588J SoM Shimrra Shai
2025-01-09 23:15 ` [PATCH v4 0/2] arm64: dts: rockchip: Add Firefly ITX-3588J Board Heiko Stuebner
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=20241216214152.58387-2-shimrrashai@gmail.com \
--to=shimrrashai@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--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