From: Dmitry Yashin <dmt.yashin@gmail.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
Philipp Zabel <p.zabel@pengutronix.de>,
Heiko Stuebner <heiko@sntech.de>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Dmitry Yashin <dmt.yashin@gmail.com>
Subject: [PATCH v2 2/5] dt-bindings: arm: rockchip: add Forlinx FET3568-C
Date: Fri, 16 Oct 2026 15:29:34 +0500 [thread overview]
Message-ID: <20261016-ok3568-c-v2-2-068d68430e6d@gmail.com> (raw)
In-Reply-To: <20261016-ok3568-c-v2-0-068d68430e6d@gmail.com>
FET3568-C is an System on Module made by Forlinx based on Rockchip RK3568.
This SoM used by OK3568-C Board.
FET3568-C features:
- Rockchip RK3568
- DDR4 1/2/4/8 GB
- eMMC 8/16/32/64 GB
- RK809 PMIC
Add devicetree binding for Forlinx FET3568-C SoM.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Dmitry Yashin <dmt.yashin@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 a799bb843f74..30a6794861cc 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -324,6 +324,13 @@ properties:
- const: firefly,rk3568-roc-pc
- const: rockchip,rk3568
+ - description: Forlinx FET3568-C SoM
+ items:
+ - enum:
+ - forlinx,ok3568-c
+ - const: forlinx,fet3568-c
+ - const: rockchip,rk3568
+
- description: Forlinx FET3588-C SoM
items:
- enum:
--
2.56.0
next prev parent reply other threads:[~2026-10-16 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:29 [PATCH v2 0/5] arm64: dts: rockchip: add Forlinx OK3568-C Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 1/5] dt-bindings: net: rfkill-gpio: document reset-gpios property Dmitry Yashin
2026-10-16 10:29 ` Dmitry Yashin [this message]
2026-10-16 10:29 ` [PATCH v2 3/5] arm64: dts: rockchip: add Forlinx FET3568-C Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 4/5] arm64: dts: rockchip: add Forlinx OK3568-C Dmitry Yashin
2026-10-16 10:29 ` [PATCH v2 5/5] arm64: dts: rockchip: add FIT-PCIE-SATA overlay Dmitry Yashin
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=20261016-ok3568-c-v2-2-068d68430e6d@gmail.com \
--to=dmt.yashin@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=heiko@sntech.de \
--cc=johannes@sipsolutions.net \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.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