linux-kernel - Re: [PATCH v4 0/5] media: imx8qxp: add parallel camera support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DE1JMG95RZME.2YSV10RI9AME4@gmail.com>
Date: Thu, 06 Nov 2025 10:34:48 +0000
From: "Rui Miguel Silva" <rmfrfs@...il.com>
To: "Frank Li" <Frank.li@....com>, "Laurent Pinchart"
 <laurent.pinchart@...asonboard.com>, "Mauro Carvalho Chehab"
 <mchehab@...nel.org>, "Hans Verkuil" <hverkuil+cisco@...nel.org>
Cc: "Shawn Guo" <shawnguo@...nel.org>, "Sascha Hauer"
 <s.hauer@...gutronix.de>, "Pengutronix Kernel Team"
 <kernel@...gutronix.de>, "Fabio Estevam" <festevam@...il.com>, "Martin
 Kepplinger" <martink@...teo.de>, "Purism Kernel Team" <kernel@...i.sm>,
 "Rob Herring" <robh@...nel.org>, "Krzysztof Kozlowski"
 <krzk+dt@...nel.org>, "Conor Dooley" <conor+dt@...nel.org>, "Philipp Zabel"
 <p.zabel@...gutronix.de>, <linux-media@...r.kernel.org>,
 <imx@...ts.linux.dev>, <linux-arm-kernel@...ts.infradead.org>,
 <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>, "Alice Yuan"
 <alice.yuan@....com>, "Krzysztof Kozlowski"
 <krzysztof.kozlowski@...aro.org>, "Robert Chiras" <robert.chiras@....com>,
 "Zhipeng Wang" <zhipeng.wang_1@....com>, "Hans Verkuil"
 <hans@...erkuil.nl>, "Sakari Ailus" <sakari.ailus@....fi>, "Kieran Bingham"
 <kieran.bingham@...asonboard.com>
Subject: Re: [PATCH v4 0/5] media: imx8qxp: add parallel camera support

On Wed Nov 5, 2025 at 7:31 PM WET, Frank Li wrote:

> On Wed, Nov 05, 2025 at 07:19:28PM +0200, Laurent Pinchart wrote:
>> Hi Frank,
>>
>> On Wed, Nov 05, 2025 at 12:03:05PM -0500, Frank Li wrote:
>> > On Wed, Sep 03, 2025 at 09:56:29AM -0400, Frank Li wrote:
>> > > On Tue, Sep 02, 2025 at 02:39:20PM +0200, Laurent Pinchart wrote:
>> > > > On Tue, Sep 02, 2025 at 08:01:40AM -0400, Frank Li wrote:
>> > > > > On Tue, Aug 05, 2025 at 04:08:22AM +0300, Laurent Pinchart wrote:
>> > > > > > Hi Frank,
>> > > > > >
>> > > > > > Thank you for the patches.
>> > > > > >
>> > > > > > I've quite busy these days, and I don't believe I will have time to
>> > > > > > review this series before coming back from OSS Europe at the beginning
>> > > > > > of September. Let's see if anyone on CC could volunteer.
>> > > > >
>> > > > > Laurent Pincha
>> > > > > 	I hope you have good time at OSS.
>> > > > >
>> > > > > 	Do you have chance to review this patch?
>> > > >
>> > > > I'm going through my mail backlog, which is really big at the moment.
>> > >
>> > > Understand.
>> > >
>> > > > I'd like someone else to volunteer to review this series. It won't scale
>> > > > if I have to review all NXP media patches in my spare time :-/
>> > >
>> > > Yes, but none volunteer review this in passed months. Expecially key
>> > > reviewer. I am reviewing i3c patches. but Not familiar v4l system yet. It
>> > > need scalable solution. I can help filter some common and simple problem
>> > > from beginning.
>> >
>> > Laurent Pinchart:
>> >
>> > 	Do you have chance to check this serise? this one should be related simple.
>> > 	This one sent at 7/29. Still not any volunteer to review it.
>>
>> I'm afraid I won't have time to review this for the time being. My spare
>> time is already exhausted by all the other drivers I maintain upstream.
>>
>> > 	How do we move forward?
>>
>> I think this is a question for the subsystem maintainers. Hans, Mauro ?
>
> Mauro Carvalho Chehab and Hans Verkuil:
>
> 	Laurent provided great help about review and land i.MX related
> patches in past, who are quite famillar with i.MX chips. But he is quite
> busy. So the whole reviews cycles takes quite long time and offten cross
> some merge windows.
>
> 	In pull requests for 6.19:
> https://lore.kernel.org/all/4989c563-47f4-478c-80c4-41f7e98597e4@kernel.org/
> only 10 patches, and 4 patches is trivial clean up.
>
> 	In reviewing patch queue, there are
> 	1: media: nxp: imx8-isi: Add ISI support for i.MX95
> 	   https://lore.kernel.org/imx/20251105-isi_imx95-v3-0-3987533cca1c@nxp.com/T/#t
> 	   This one already review, but I am not sure if it capture 6.19 cycle because
> PULL-request already sent.
>
> 	2: Add MIPI CSI-2 support for i.MX8ULP
> 	   https://lore.kernel.org/imx/20251023-csi2_imx8ulp-v7-0-5ecb081ce79b@nxp.com/
>
> 	3: media: add imx93 mipi/controller csi support
> 	   https://lore.kernel.org/imx/20250821-95_cam-v3-0-c9286fbb34b9@nxp.com/
> 	   This one is quite big, but first 10 patches is simple trivial cleanup patches.
> 	   I post at 8/27, but get first feedback around 10/27, I am not
> 	   sure if missing somethings.
>
> 	4: This series, laurent already said no time review it.
>
> 	5: ap1302 sensor patches
>            https://lore.kernel.org/imx/20250811-ap1302-v4-0-80cc41b91662@nxp.com/
>            binding already ACK, most maintainer want to pick binding with
> 	   driver together, but not an feedback since 8/11.
>
> 	I jump into and help do some review.
>
> 	The questions is how to move forward pending patches, like [3], [4],
> [5]. How to keep good community channel to avoid long time pending?

Sorry, but like Laurent I am really without spare cycles to go over the
patch series that have arrived in media (also I do not have any hw anymore).
So, Frank or maybe Laurent knows someone that would like to be add also as
maintainer of this drivers for me would be great, that would also help to
avoid such bottlenecks.

Thanks in advance,
Cheers,
    Rui
>
> Best regards
> Frank Li