From: Michael Riesch <michael.riesch@collabora.com>
To: Amin Gattout <amin.gattout@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add MIPI CSI-2 receiver support for RK3576
Date: Mon, 7 Sep 2026 12:42:43 +0200 [thread overview]
Message-ID: <0fda1cf1-8df7-4e50-be6d-dc17ca3591cf@collabora.com> (raw)
In-Reply-To: <20260826-csi-2-rcv-dts-v1-0-bcd8d459684d@gmail.com>
Hi Amin,
On 8/26/26 14:33, Amin Gattout wrote:
> This series adds the device tree binding and the SoC nodes for the
> MIPI CSI-2 receiver units of the Rockchip RK3576. The receiver is the
> same Synopsys DesignWare IP as in the RK3568 and the register map is
> identical, so the existing driver is used unchanged via a fallback
> compatible.
>
> Only the two receivers fed by the Innosilicon D-PHYs in full mode
> (MIPI1 and MIPI3) are added; see patch 2 for the details.
>
> This series depends on the RK3576 CSI D-PHY series [1], which provides
> the csi_dphy0/csi_dphy1 nodes referenced here.
>
> [1] https://lore.kernel.org/r/20260820-rk3576-dphy-v1-0-70e25e8d5e78@gmail.com
Thanks for your work, LGTM!
Just one thing: It would be great if you could describe your test setup
a bit (HW components, test case, ...).
>
> Signed-off-by: Amin Gattout <amin.gattout@gmail.com>
For this series:
Reviewed-by: Michael Riesch <michael.riesch@collabora.com>
Best regards,
Michael
> ---
> Amin Gattout (2):
> media: dt-bindings: rockchip,rk3568-mipi-csi2: add rk3576 compatible
> arm64: dts: rockchip: add mipi csi-2 receiver nodes to rk3576
>
> .../bindings/media/rockchip,rk3568-mipi-csi2.yaml | 1 +
> arch/arm64/boot/dts/rockchip/rk3576.dtsi | 52 ++++++++++++++++++++++
> 2 files changed, 53 insertions(+)
> ---
> base-commit: bd5f485f3f026225b86573e559af0b7254ef4184
> change-id: 20260825-csi-2-rcv-dts-7712bd834de6
> prerequisite-change-id: 20260819-rk3576-dphy-2304f848215b:v1
> prerequisite-patch-id: fbe2d84f88709b8bf846debe6b8ce62c4392ca63
> prerequisite-patch-id: 9bce33933ae69e8cc7f7ef2f0d9acb969620bc85
> prerequisite-patch-id: aca697161c21e19fe3a7f62f208da0f6c3b666e1
> prerequisite-patch-id: 8f45701f840680a35e044f43ebd3087282847990
>
> Best regards,
> --
> Amin Gattout <amin.gattout@gmail.com>
>
prev parent reply other threads:[~2026-09-07 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 12:33 [PATCH 0/2] Add MIPI CSI-2 receiver support for RK3576 Amin Gattout
2026-08-26 12:33 ` [PATCH 1/2] media: dt-bindings: rockchip,rk3568-mipi-csi2: add rk3576 compatible Amin Gattout
2026-08-26 16:02 ` Conor Dooley
2026-08-26 12:33 ` [PATCH 2/2] arm64: dts: rockchip: add mipi csi-2 receiver nodes to rk3576 Amin Gattout
2026-09-07 10:42 ` Michael Riesch [this message]
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=0fda1cf1-8df7-4e50-be6d-dc17ca3591cf@collabora.com \
--to=michael.riesch@collabora.com \
--cc=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-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.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 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.