From: Liangbin Lian <jjm2473@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, quentin.schulz@cherry.de,
kever.yang@rock-chips.com, naoki@radxa.com,
honyuenkwun@gmail.com, inindev@gmail.com,
ivan8215145640@gmail.com, neil.armstrong@linaro.org,
mani@kernel.org, dsimic@manjaro.org, pbrobinson@gmail.com,
alchark@gmail.com, didi.debian@cknow.org, jjm2473@gmail.com,
jbx6244@gmail.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 2/3] dt-bindings: arm: rockchip: Add LinkEase EasePi R1
Date: Mon, 29 Sep 2025 14:57:13 +0800 [thread overview]
Message-ID: <20250929065714.27741-3-jjm2473@gmail.com> (raw)
In-Reply-To: <20250929065714.27741-1-jjm2473@gmail.com>
LinkEase EasePi R1 is a high-performance mini router based on RK3568.
Signed-off-by: Liangbin Lian <jjm2473@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 28db6bd6aa5b..ec2271cfb7e1 100644
--- a/Documentation/devicetree/bindings/arm/rockchip.yaml
+++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
@@ -726,6 +726,11 @@ properties:
- const: lckfb,tspi-rk3566
- const: rockchip,rk3566
+ - description: LinkEase EasePi R1
+ items:
+ - const: linkease,easepi-r1
+ - const: rockchip,rk3568
+
- description: Luckfox Core3576 Module based boards
items:
- enum:
--
2.51.0
next prev parent reply other threads:[~2025-09-29 6:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 6:57 [PATCH v3 0/3] arm64: dts: rockchip: introduce LinkEase EasePi R1 Liangbin Lian
2025-09-29 6:57 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: Document LinkEase Liangbin Lian
2025-09-29 12:27 ` Heiko Stuebner
2025-09-29 6:57 ` Liangbin Lian [this message]
2025-09-29 12:28 ` [PATCH v3 2/3] dt-bindings: arm: rockchip: Add LinkEase EasePi R1 Heiko Stuebner
2025-09-29 18:20 ` jjm2473
2025-10-06 15:43 ` Andrew Lunn
2025-10-07 14:56 ` jjm2473
2025-09-29 6:57 ` [PATCH v3 3/3] arm64: dts: rockchip: add " Liangbin Lian
2025-10-06 15:51 ` Andrew Lunn
2025-10-07 14:32 ` jjm2473
2025-10-07 14:57 ` Andrew Lunn
2025-10-07 16:25 ` Russell King (Oracle)
2025-10-07 16:32 ` Quentin Schulz
2025-10-07 17:29 ` jjm2473
2025-10-07 18:32 ` Andrew Lunn
2025-10-09 8:47 ` Alexey Charkov
2025-10-09 13:04 ` Andrew Lunn
2025-10-07 18:48 ` Russell King (Oracle)
2025-10-09 5:16 ` jjm2473
2025-09-29 10:20 ` [PATCH v3 0/3] arm64: dts: rockchip: introduce " Diederik de Haas
2025-09-29 18:09 ` jjm2473
2025-09-30 11:19 ` Diederik de Haas
2025-09-30 17:52 ` jjm2473
2025-10-07 16:27 ` Russell King (Oracle)
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=20250929065714.27741-3-jjm2473@gmail.com \
--to=jjm2473@gmail.com \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=didi.debian@cknow.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=inindev@gmail.com \
--cc=ivan8215145640@gmail.com \
--cc=jbx6244@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mani@kernel.org \
--cc=naoki@radxa.com \
--cc=neil.armstrong@linaro.org \
--cc=pbrobinson@gmail.com \
--cc=quentin.schulz@cherry.de \
--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;
as well as URLs for NNTP newsgroup(s).