From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Michael Riesch <michael.riesch@collabora.com>
Cc: "Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Mehdi Djait" <mehdi.djait@linux.intel.com>,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Gerald Loacker" <gerald.loacker@wolfvision.net>,
"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
"Markus Elfring" <Markus.Elfring@web.de>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Kever Yang" <kever.yang@rock-chips.com>,
"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
"Sebastian Reichel" <sebastian.reichel@collabora.com>,
"Collabora Kernel Team" <kernel@collabora.com>,
"Paul Kocialkowski" <paulk@sys-base.io>,
"Alexander Shiyan" <eagle.alexander923@gmail.com>,
"Val Packett" <val@packett.cool>, "Rob Herring" <robh@kernel.org>,
"Philipp Zabel" <p.zabel@pengutronix.de>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
"Mehdi Djait" <mehdi.djait@bootlin.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"Bryan O'Donoghue" <bod@kernel.org>,
"Chen-Yu Tsai" <wens@csie.org>
Subject: Re: [PATCH v14 00/18] media: rockchip: add a driver for the rockchip camera interface
Date: Fri, 7 Nov 2025 20:54:41 +0200 [thread overview]
Message-ID: <20251107185441.GG5558@pendragon.ideasonboard.com> (raw)
In-Reply-To: <074cd08e-0412-49f9-8dd9-b1f96eb11717@collabora.com>
On Fri, Nov 07, 2025 at 07:41:59PM +0100, Michael Riesch wrote:
> On 11/7/25 18:32, Sakari Ailus wrote:
> > On Fri, Oct 24, 2025 at 02:51:29PM +0200, Michael Riesch via B4 Relay wrote:
> >> Habidere,
> >>
> >> This series introduces support for the Rockchip Camera Interface (CIF),
> >> which is featured in many Rockchip SoCs in different variations.
> >> For example, the PX30 Video Input Processor (VIP) is able to receive
> >> video data via the Digital Video Port (DVP, a parallel data interface)
> >> and transfer it into system memory using a double-buffering mechanism
> >> called ping-pong mode.
> >> The RK3568 Video Capture (VICAP) unit, on the other hand, features a
> >> DVP and a MIPI CSI-2 receiver that can receive video data independently
> >> (both using the ping-pong scheme).
> >> The different variants may have additional features, such as scaling
> >> and/or cropping.
> >> Finally, the RK3588 VICAP unit constitutes an essential piece of the
> >> camera interface with one DVP, six MIPI CSI-2 receivers, scale/crop
> >> units, and a data path multiplexer (to scaler units, to ISP, ...).
> >
> > I understand both RK3568 and RK3588 include an ISP. Do you have insight on
> > how would this work, should the support for the ISP be added later on?
>
> Short answer: Yes and yes.
>
> Long answer:
>
> The patch series at hand adds support for the PX30 VIP and the RK3568
> VICAP. I cannot really say something about the PX30, but on the RK3568
> VICAP and ISP are orthogonal (the ISP features its own MIPI CSI-2
> receiver, different from that introduced in this series). Thus, ISP
> support can be introduced anytime (whenever someone is motivated ;-)).
Won't they both be connected to the same sensor though, and probably the
same D-PHY in the SoC ? They don't seem entirely separate to me.
A block diagram that shows connections between the CSI-2 pins, D-PHY,
CSI-2 receivers, VICAP and ISP could help.
> Once this patch series is merged, I'll push out changes that introduce
> support for the RK3588 VICAP. We can discuss the integration of any
> RK3588 ISP in this scope then -- and there may be some things to discuss
> as there the VICAP and the ISP(s) are directly connected by means of a
> MUX unit in the VICAP.
>
> Alright?
--
Regards,
Laurent Pinchart
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-11-07 18:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 12:51 [PATCH v14 00/18] media: rockchip: add a driver for the rockchip camera interface Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 01/18] Documentation: admin-guide: media: add " Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 02/18] media: dt-bindings: video-interfaces: add defines for sampling modes Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 03/18] media: dt-bindings: add rockchip px30 vip Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 04/18] media: dt-bindings: add rockchip rk3568 vicap Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 05/18] media: dt-bindings: add rockchip rk3568 mipi csi-2 receiver Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 06/18] media: rockchip: add driver for the rockchip " Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 07/18] media: rockchip: add driver for the rockchip camera interface Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 08/18] media: rockchip: rkcif: add abstraction for interface and crop blocks Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 09/18] media: rockchip: rkcif: add abstraction for dma blocks Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 10/18] media: rockchip: rkcif: add support for px30 vip dvp capture Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 11/18] media: rockchip: rkcif: add support for rk3568 vicap " Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 12/18] media: rockchip: rkcif: add support for rk3568 vicap mipi capture Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 13/18] arm64: defconfig: enable rockchip camera interface and mipi csi-2 receiver Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 14/18] arm64: dts: rockchip: add the vip node to px30 Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 15/18] arm64: dts: rockchip: add vicap node to rk356x Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 16/18] arm64: dts: rockchip: add mipi csi-2 receiver " Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 17/18] arm64: dts: rockchip: enable vicap dvp on wolfvision pf5 io expander Michael Riesch via B4 Relay
2025-10-24 12:51 ` [PATCH v14 18/18] arm64: dts: rockchip: add radxa camera 8m on rock 3a csi port Michael Riesch via B4 Relay
2025-10-24 12:57 ` [PATCH v14 00/18] media: rockchip: add a driver for the rockchip camera interface Michael Riesch
2025-11-07 17:32 ` Sakari Ailus
2025-11-07 18:41 ` Michael Riesch
2025-11-07 18:54 ` Laurent Pinchart [this message]
2025-11-07 20:51 ` Michael Riesch
2025-11-10 8:43 ` Sakari Ailus
2025-11-10 10:29 ` Michael Riesch
2025-11-11 0:06 ` Laurent Pinchart
2025-11-11 8:37 ` Michael Riesch
2025-11-11 10:42 ` Michael Riesch
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=20251107185441.GG5558@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Markus.Elfring@web.de \
--cc=bod@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=eagle.alexander923@gmail.com \
--cc=gerald.loacker@wolfvision.net \
--cc=heiko@sntech.de \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.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=maxime.chevallier@bootlin.com \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@bootlin.com \
--cc=mehdi.djait@linux.intel.com \
--cc=michael.riesch@collabora.com \
--cc=nicolas.dufresne@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=paulk@sys-base.io \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=sebastian.reichel@collabora.com \
--cc=theo.lebrun@bootlin.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=val@packett.cool \
--cc=wens@csie.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