From: Amin Gattout <amin.gattout@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: Michael Riesch <michael.riesch@collabora.com>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
Amin Gattout <amin.gattout@gmail.com>
Subject: [PATCH 2/4] dt-bindings: phy: rockchip-inno-csi-dphy: add rk3576 variant
Date: Thu, 20 Aug 2026 16:01:09 +0200 [thread overview]
Message-ID: <20260820-rk3576-dphy-v1-2-70e25e8d5e78@gmail.com> (raw)
In-Reply-To: <20260820-rk3576-dphy-v1-0-70e25e8d5e78@gmail.com>
The Rockchip RK3576 features two MIPI CSI-2 DPHYs compatible with this
binding. Unlike the RK3588 variant, each PHY instance only has an APB
reset line, so add the new compatible to the single-reset group as
well.
Signed-off-by: Amin Gattout <amin.gattout@gmail.com>
---
Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml b/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
index 03950b3cad08..92d0c961f4c4 100644
--- a/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
+++ b/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
@@ -21,6 +21,7 @@ properties:
- rockchip,rk3326-csi-dphy
- rockchip,rk3368-csi-dphy
- rockchip,rk3568-csi-dphy
+ - rockchip,rk3576-csi-dphy
- rockchip,rk3588-csi-dphy
reg:
@@ -89,6 +90,7 @@ allOf:
- rockchip,rk3326-csi-dphy
- rockchip,rk3368-csi-dphy
- rockchip,rk3568-csi-dphy
+ - rockchip,rk3576-csi-dphy
then:
properties:
resets:
--
2.43.0
WARNING: multiple messages have this Message-ID (diff)
From: Amin Gattout <amin.gattout@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: Michael Riesch <michael.riesch@collabora.com>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
Amin Gattout <amin.gattout@gmail.com>
Subject: [PATCH 2/4] dt-bindings: phy: rockchip-inno-csi-dphy: add rk3576 variant
Date: Thu, 20 Aug 2026 16:01:09 +0200 [thread overview]
Message-ID: <20260820-rk3576-dphy-v1-2-70e25e8d5e78@gmail.com> (raw)
In-Reply-To: <20260820-rk3576-dphy-v1-0-70e25e8d5e78@gmail.com>
The Rockchip RK3576 features two MIPI CSI-2 DPHYs compatible with this
binding. Unlike the RK3588 variant, each PHY instance only has an APB
reset line, so add the new compatible to the single-reset group as
well.
Signed-off-by: Amin Gattout <amin.gattout@gmail.com>
---
Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml b/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
index 03950b3cad08..92d0c961f4c4 100644
--- a/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
+++ b/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
@@ -21,6 +21,7 @@ properties:
- rockchip,rk3326-csi-dphy
- rockchip,rk3368-csi-dphy
- rockchip,rk3568-csi-dphy
+ - rockchip,rk3576-csi-dphy
- rockchip,rk3588-csi-dphy
reg:
@@ -89,6 +90,7 @@ allOf:
- rockchip,rk3326-csi-dphy
- rockchip,rk3368-csi-dphy
- rockchip,rk3568-csi-dphy
+ - rockchip,rk3576-csi-dphy
then:
properties:
resets:
--
2.43.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: Amin Gattout <amin.gattout@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>
Cc: Michael Riesch <michael.riesch@collabora.com>,
devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
Amin Gattout <amin.gattout@gmail.com>
Subject: [PATCH 2/4] dt-bindings: phy: rockchip-inno-csi-dphy: add rk3576 variant
Date: Thu, 20 Aug 2026 16:01:09 +0200 [thread overview]
Message-ID: <20260820-rk3576-dphy-v1-2-70e25e8d5e78@gmail.com> (raw)
In-Reply-To: <20260820-rk3576-dphy-v1-0-70e25e8d5e78@gmail.com>
The Rockchip RK3576 features two MIPI CSI-2 DPHYs compatible with this
binding. Unlike the RK3588 variant, each PHY instance only has an APB
reset line, so add the new compatible to the single-reset group as
well.
Signed-off-by: Amin Gattout <amin.gattout@gmail.com>
---
Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml b/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
index 03950b3cad08..92d0c961f4c4 100644
--- a/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
+++ b/Documentation/devicetree/bindings/phy/rockchip-inno-csi-dphy.yaml
@@ -21,6 +21,7 @@ properties:
- rockchip,rk3326-csi-dphy
- rockchip,rk3368-csi-dphy
- rockchip,rk3568-csi-dphy
+ - rockchip,rk3576-csi-dphy
- rockchip,rk3588-csi-dphy
reg:
@@ -89,6 +90,7 @@ allOf:
- rockchip,rk3326-csi-dphy
- rockchip,rk3368-csi-dphy
- rockchip,rk3568-csi-dphy
+ - rockchip,rk3576-csi-dphy
then:
properties:
resets:
--
2.43.0
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-08-20 14:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 14:01 [PATCH 0/4] phy: rockchip: add support for the RK3576 MIPI CSI-2 DPHYs Amin Gattout
2026-08-20 14:01 ` Amin Gattout
2026-08-20 14:01 ` Amin Gattout
2026-08-20 14:01 ` [PATCH 1/4] dt-bindings: soc: rockchip: add rk3576 csidphy grf syscon Amin Gattout
2026-08-20 14:01 ` Amin Gattout
2026-08-20 14:01 ` Amin Gattout
2026-08-20 18:16 ` Conor Dooley
2026-08-20 18:16 ` Conor Dooley
2026-08-20 18:16 ` Conor Dooley
2026-08-20 14:01 ` Amin Gattout [this message]
2026-08-20 14:01 ` [PATCH 2/4] dt-bindings: phy: rockchip-inno-csi-dphy: add rk3576 variant Amin Gattout
2026-08-20 14:01 ` Amin Gattout
2026-08-20 18:18 ` Conor Dooley
2026-08-20 18:18 ` Conor Dooley
2026-08-20 18:18 ` Conor Dooley
2026-08-20 14:01 ` [PATCH 3/4] phy: rockchip: phy-rockchip-inno-csidphy: add support for " Amin Gattout
2026-08-20 14:01 ` Amin Gattout
2026-08-20 14:01 ` Amin Gattout
2026-08-20 14:10 ` sashiko-bot
2026-08-20 14:10 ` sashiko-bot
2026-08-20 14:01 ` [PATCH 4/4] arm64: dts: rockchip: add csi dphy nodes to rk3576 Amin Gattout
2026-08-20 14:01 ` Amin Gattout
2026-08-20 14:01 ` Amin Gattout
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=20260820-rk3576-dphy-v1-2-70e25e8d5e78@gmail.com \
--to=amin.gattout@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-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@collabora.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=vkoul@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.