Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gerald Loacker <gerald.loacker@wolfvision.net>
To: "Michael Riesch" <michael.riesch@collabora.com>,
	"Bryan O'Donoghue" <bod@kernel.org>,
	"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>,
	"Bryan O'Donoghue" <bryan.odonoghue@linaro.org>,
	"Markus Elfring" <Markus.Elfring@web.de>,
	"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
	"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>,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>
Cc: 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>
Subject: Re: [PATCH v11 00/17] media: rockchip: add a driver for the rockchip camera interface
Date: Mon, 13 Oct 2025 09:00:58 +0200	[thread overview]
Message-ID: <b7cccc39-612d-4736-8689-890b4077e730@wolfvision.net> (raw)
In-Reply-To: <de1a1dce-f60e-48a1-9945-d2c91b328df5@collabora.com>

Hi Michael, Bryan,

Am 10.10.2025 um 15:46 schrieb Michael Riesch:
> Hi Bryan,
> 
> On 10/10/25 14:15, Bryan O'Donoghue wrote:
>> On 17/09/2025 16:38, 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, ...).
>>>
>>> The v11 of the series adds a media controller centric V4L2 device driver
>>> for the Rockchip CIF with
>>>   - support for the PX30 VIP (not tested, though, due to the lack of HW)
>>>   - support for the RK3568 VICAP, including
>>>      - capturing frames from the DVP
>>>      - capturing frames from the MIPI CSI-2 receiver
>>>   - abstraction for the ping-pong scheme to allow for future extensions
>>>   - abstraction for the INTERFACE and CROP parts to allow for future
>>>     extensions
>>>   - initial support for different virtual channels (not tested, though,
>>>     due to the lack of HW)
>>> and a V4L2 subdevice driver for the Rockchip MIPI CSI-2 Receiver.
>>>
>>> The driver can be readily extended to provide support for the RK3588
>>> VICAP variant. In order to keep things simple, however, this extension
>>> shall be submitted separately.
>>>
>>> Looking forward to your comments!
>>>
>>> To: Mehdi Djait<mehdi.djait@linux.intel.com>
>>> To: Maxime Chevallier<maxime.chevallier@bootlin.com>
>>> To: Théo Lebrun<theo.lebrun@bootlin.com>
>>> To: Thomas Petazzoni<thomas.petazzoni@bootlin.com>
>>> To: Gerald Loacker<gerald.loacker@wolfvision.net>
>>> To: Bryan O'Donoghue<bryan.odonoghue@linaro.org>
>>> To: Markus Elfring<Markus.Elfring@web.de>
>>> To: Sakari Ailus<sakari.ailus@iki.fi>
>>> To: Laurent Pinchart<laurent.pinchart@ideasonboard.com>
>>> To: Mauro Carvalho Chehab<mchehab@kernel.org>
>>> To: Rob Herring<robh+dt@kernel.org>
>>> To: Krzysztof Kozlowski<krzk+dt@kernel.org>
>>> To: Conor Dooley<conor+dt@kernel.org>
>>> To: Heiko Stuebner<heiko@sntech.de>
>>> To: Kever Yang<kever.yang@rock-chips.com>
>>> To: Nicolas Dufresne<nicolas.dufresne@collabora.com>
>>> To: Sebastian Reichel<sebastian.reichel@collabora.com>
>>> To: Collabora Kernel Team<kernel@collabora.com>
>>> To: Paul Kocialkowski<paulk@sys-base.io>
>>> To: Alexander Shiyan<eagle.alexander923@gmail.com>
>>> To: Val Packett<val@packett.cool>
>>> To: Rob Herring<robh@kernel.org>
>>> To: Philipp Zabel<p.zabel@pengutronix.de>
>>> Cc:linux-media@vger.kernel.org
>>> Cc:devicetree@vger.kernel.org
>>> Cc:linux-kernel@vger.kernel.org
>>> Cc:linux-arm-kernel@lists.infradead.org
>>> Cc:linux-rockchip@lists.infradead.org
>>> Signed-off-by: Michael Riesch<michael.riesch@wolfvision.net>
>>> Signed-off-by: Michael Riesch<michael.riesch@collabora.com>
>>>
>>> Changes in v11:
>>> - rkcif: split large driver patch (6/13 of v10) into smaller
>>>    patches (6-11/17 of v11) (Bryan)
>>> - rkcsi: replaced devm_reset_control_array_get_exclusive with
>>>    devm_reset_control_get_exclusive (Philipp)
>>> - Link to v10:https://lore.kernel.org/r/20240220-rk3568-vicap-
>>> v10-0-62d8a7b209b4@collabora.com
>>
>> I believe it is the case and please feel free to correct me if I'm wrong
>> that you've dropped a long list of sob/co-develop-by, I think we
>> discussed that too, because of the level of change, it seems reasonable
>> too.
> 
> Correct. The tag list used to be quite complicated [0] due to the
> complicated history of this driver. Maxime worked on the driver up to
> v5, Mehdi up to v14, I added RK3568 support on top of Mehdi's v14 (with
> some valuable contributions from Gerald) and submitted that as v1. v2 of
> my work incorporated Mehdi's v14, and here we are, after several rounds
> of feedback, at soon-to-be v12 (or, in fact, v25).
> 
>> On question on that, are these people aware of the change and cc'd on
>> the list of recipients/contactable/agreeable to the change ?
> 
> I announced this plan as a response to your comment to v10 [1] with
> Maxime, Mehdi and Gerald on Cc: and did not hear any objections.
> 
> Hope that this is still OK for everybody!
> 

I agree with that!

Regards,
Gerald

> Best regards,
> Michael
> 
> [0]
> https://lore.kernel.org/linux-media/20240220-rk3568-vicap-v10-6-62d8a7b209b4@collabora.com/
> [1]
> https://lore.kernel.org/linux-media/23ccc744-745d-4a31-a79c-2d64bf1ed43d@collabora.com/
> 


_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

      reply	other threads:[~2025-10-13  7:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <HSTnNzc6MTLHGWih5qjlI2nvVECP8FVdcQVeBON4KlWYLtEaWIlNmEpKTU_vlqitbIIHMpabKnvnmpEQFqHYxQ==@protonmail.internalid>
2025-09-17 15:38 ` [PATCH v11 00/17] media: rockchip: add a driver for the rockchip camera interface Michael Riesch via B4 Relay
2025-09-17 15:38   ` [PATCH v11 01/17] Documentation: admin-guide: media: add " Michael Riesch via B4 Relay
2025-09-17 15:38   ` [PATCH v11 02/17] media: dt-bindings: video-interfaces: add defines for sampling modes Michael Riesch via B4 Relay
2025-09-17 15:38   ` [PATCH v11 03/17] media: dt-bindings: add rockchip px30 vip Michael Riesch via B4 Relay
2025-09-30  0:17     ` Bryan O'Donoghue
2025-09-17 15:38   ` [PATCH v11 04/17] media: dt-bindings: add rockchip rk3568 vicap Michael Riesch via B4 Relay
2025-09-30  0:20     ` Bryan O'Donoghue
2025-09-17 15:38   ` [PATCH v11 05/17] media: dt-bindings: add rockchip rk3568 mipi csi-2 receiver Michael Riesch via B4 Relay
2025-09-22 17:11     ` Rob Herring
2025-09-29 21:46       ` Michael Riesch
2025-10-07 20:00     ` Sakari Ailus
2025-10-09  9:09       ` Michael Riesch
2025-09-17 15:38   ` [PATCH v11 06/17] media: rockchip: add driver for the rockchip " Michael Riesch via B4 Relay
2025-10-10 12:01     ` Bryan O'Donoghue
2025-09-17 15:38   ` [PATCH v11 07/17] media: rockchip: add driver for the rockchip camera interface Michael Riesch via B4 Relay
2025-09-19  7:49     ` Gerald Loacker
2025-10-10 12:29     ` Bryan O'Donoghue
2025-09-17 15:38   ` [PATCH v11 08/17] media: rockchip: rkcif: add abstraction for interface and crop blocks Michael Riesch via B4 Relay
2025-09-19  7:49     ` Gerald Loacker
2025-09-17 15:38   ` [PATCH v11 09/17] media: rockchip: rkcif: add abstraction for dma blocks Michael Riesch via B4 Relay
2025-09-19  7:50     ` Gerald Loacker
2025-09-17 15:38   ` [PATCH v11 10/17] media: rockchip: rkcif: add support for px30 vip dvp capture Michael Riesch via B4 Relay
2025-09-19  7:51     ` Gerald Loacker
2025-10-07 20:12     ` Sakari Ailus
2025-10-09  8:26       ` Michael Riesch
2025-09-17 15:38   ` [PATCH v11 11/17] media: rockchip: rkcif: add support for rk3568 vicap " Michael Riesch via B4 Relay
2025-09-19  7:52     ` Gerald Loacker
2025-09-17 15:38   ` [PATCH v11 12/17] media: rockchip: rkcif: add support for rk3568 vicap mipi capture Michael Riesch via B4 Relay
2025-09-17 15:38   ` [PATCH v11 13/17] arm64: defconfig: enable rockchip camera interface and mipi csi-2 receiver Michael Riesch via B4 Relay
2025-09-17 15:38   ` [PATCH v11 14/17] arm64: dts: rockchip: add the vip node to px30 Michael Riesch via B4 Relay
2025-09-17 15:38   ` [PATCH v11 15/17] arm64: dts: rockchip: add vicap node to rk356x Michael Riesch via B4 Relay
2025-09-17 15:38   ` [PATCH v11 16/17] arm64: dts: rockchip: add mipi csi-2 receiver " Michael Riesch via B4 Relay
2025-09-17 15:38   ` [PATCH v11 17/17] arm64: dts: rockchip: enable vicap dvp on wolfvision pf5 io expander Michael Riesch via B4 Relay
2025-09-19  7:48   ` [PATCH v11 00/17] media: rockchip: add a driver for the rockchip camera interface Gerald Loacker
2025-10-10 12:15   ` Bryan O'Donoghue
2025-10-10 13:46     ` Michael Riesch
2025-10-13  7:00       ` Gerald Loacker [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=b7cccc39-612d-4736-8689-890b4077e730@wolfvision.net \
    --to=gerald.loacker@wolfvision.net \
    --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=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=kever.yang@rock-chips.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --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 \
    /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