The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Antoine Bouyer <antoine.bouyer@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: julien.vuillaumier@nxp.com, alexi.birlinger@nxp.com,
	daniel.baluta@nxp.com, peng.fan@nxp.com, frank.li@nxp.com,
	jacopo.mondi@ideasonboard.com, laurent.pinchart@ideasonboard.com,
	mchehab@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, michael.riesch@collabora.com,
	anthony.mcgivern@arm.com, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	imx@lists.linux.dev, ai.luthra@ideasonboard.com,
	paul.elder@ideasonboard.com
Subject: Re: [PATCH v1 00/11] media: Add iMX95 neoisp driver
Date: Thu, 7 May 2026 15:37:58 +0200	[thread overview]
Message-ID: <fac452bc-3bc0-4b50-86d9-abdfb83deb5b@nxp.com> (raw)
In-Reply-To: <20260416-olivine-cuttlefish-from-tartarus-ad3df2@quoll>

Le 16/04/2026 à 11:20, Krzysztof Kozlowski a écrit :
> 
> 
> On Mon, Apr 13, 2026 at 06:03:20PM +0200, Antoine Bouyer wrote:
>> Hello
>>
>> This patch series introduces the NXP Neo Image Signal Processor (ISP)
>> driver, used in the NXP i.MX95 SoC and future devices in the i.MX9 family.
>> The series also includes updates to the generic v4l2-isp interface to
>> support extended statistics required by the Neo ISP.
>>
>> The Neo ISP processes one or more camera streams, converting RAW formats
>> into YUV or RGB outputs. Its architecture is largely influenced by the
>> PISP driver. To limit the number of v4l2 devices, the driver supports only
>> one context, with three sink pads (main input, second input for HDR, and
>> parameter buffers) and three source pads (RGB output, IR output, and
>> statistics metadata).
>>
>> The driver supports the generic extensible v4l2-isp framework for
>> parameters, similar to rkisp1 and mali-c55, and applies the same approach
>> to statistics buffers. The generic v4l2-isp framework is modified to
>> factorize structure definitions and versioning, so that both parameters
>> and statistics buffers share the same mechanisms.
> 
> That's a v2, not v1.

Hi Krzysztof

Thanks for your review

Sorry, my mistake. My previous submission was an RFC, so I reset version 
counter to 1 by mistake when submitting this patch series.

> 
> Does this work:
> b4 diff 20260413160331.2611829-1-antoine.bouyer@nxp.com
> 
> ? No.
> 
> Should it work? Yes.

I hope v2 will do then ...

> 
> Also, implement previous feedback - I see no changelog, so I assume you
> just ignored everything. Judging by build process errors, it's even
> worse.

Oh no, don't worry, I did not ignore your comments: using maxItems for 
clocks, removing unused configs, and renaming filename to match the 
compatible used in imx95 SoC.

I tried to summarize these changes in this cover letter, but probably 
missing details.

They will be included in v2, along with the fix for the obvious error 
reported by the bot.

Best regards
Antoine

> 
> Best regards,
> Krzysztof
> 


      parent reply	other threads:[~2026-05-07 13:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260413160331.2611829-1-antoine.bouyer@nxp.com>
     [not found] ` <20260413160331.2611829-10-antoine.bouyer@nxp.com>
2026-05-06 14:26   ` [PATCH v1 09/11] media: platform: Add NXP Neoisp Image Signal Processor Geert Uytterhoeven
2026-05-07 13:48     ` Antoine Bouyer
2026-05-08  9:10       ` Geert Uytterhoeven
     [not found] ` <20260416-olivine-cuttlefish-from-tartarus-ad3df2@quoll>
2026-05-07 13:37   ` Antoine Bouyer [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=fac452bc-3bc0-4b50-86d9-abdfb83deb5b@nxp.com \
    --to=antoine.bouyer@nxp.com \
    --cc=ai.luthra@ideasonboard.com \
    --cc=alexi.birlinger@nxp.com \
    --cc=anthony.mcgivern@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frank.li@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=julien.vuillaumier@nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=michael.riesch@collabora.com \
    --cc=paul.elder@ideasonboard.com \
    --cc=peng.fan@nxp.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox