From: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
To: Linmao Li <lilinmao@kylinos.cn>
Cc: "Jacopo Mondi" <jacopo.mondi+renesas@ideasonboard.com>,
"Jai Luthra" <jai.luthra+renesas@ideasonboard.com>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: rppx1: describe the MAIN_POST white balance gains block
Date: Tue, 18 Aug 2026 11:37:12 +0200 [thread overview]
Message-ID: <aoQniglSwAEH3V0D@zed> (raw)
In-Reply-To: <20260818020933.3153280-1-lilinmao@kylinos.cn>
Hello Linmao
On Tue, Aug 18, 2026 at 10:09:33AM +0800, Linmao Li wrote:
> rppx1_ext_params_blocks_info[] is indexed by block type and is built
> with designated initialisers, so a block type without an entry is left
> as a zero-sized hole. RPPX1_PARAMS_BLOCK_TYPE_AWBG_POST is the only
> such hole: a block reporting that type and a size of zero passes
> v4l2_isp_params_validate_buffer(), which then has nothing to advance
> the walk with.
>
> Describe the block, so the array covers all block types the uAPI
> defines. The MAIN_POST white balance gains module is probed and started
> with the rest of the POST pipe, and RPPX1_PARAMS_MAX_SIZE already
> reserves room for all three white balance gains blocks.
>
> The block is not dispatched by rppx1_params(), in line with the other
> described blocks that have no users yet.
>
> Signed-off-by: Linmao Li <lilinmao@kylinos.cn>
Thanks
Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> ---
> Changes since v1 [1]:
> - dropped the rppx1_params() dispatch hunk, the block stays undispatched
> like the other described blocks that have no users yet (Niklas);
> - retitled, and the commit message now leads with the hole in the array;
> - dropped the Fixes: tag, the fix is expected to be collected together
> with the driver for v7.3 (Jacopo).
I'll sync with Sakari/Hans to see if this can collected as soon as
-rc1 is out
>
> The second patch of v1, "media: rppx1: bls: read the raw pattern from
> the PRE2 acquisition module", is dropped for now and will be resent when
> PRE2 support lands.
If you wish to resend, we could collect that one as well!
Thanks
j
>
> The zero-sized block problem in the common validator is addressed by
> David Carlier's "media: v4l2-isp: reject zero-sized parameter blocks"
> [2], so it is not touched here.
>
> [1] https://lore.kernel.org/linux-media/20260817104529.3132552-1-lilinmao@kylinos.cn/
> [2] https://lore.kernel.org/linux-media/20260815193839.141406-1-devnexen@gmail.com/
>
> drivers/media/platform/dreamchip/rppx1/rpp_params.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/media/platform/dreamchip/rppx1/rpp_params.c b/drivers/media/platform/dreamchip/rppx1/rpp_params.c
> index a75a27a8afd09..5e6727d589464 100644
> --- a/drivers/media/platform/dreamchip/rppx1/rpp_params.c
> +++ b/drivers/media/platform/dreamchip/rppx1/rpp_params.c
> @@ -25,6 +25,7 @@ rppx1_ext_params_blocks_info[] = {
> RPPX1_PARAMS_BLOCK_INFO(LSC_PRE2, lsc),
> RPPX1_PARAMS_BLOCK_INFO(AWBG_PRE1, awbg),
> RPPX1_PARAMS_BLOCK_INFO(AWBG_PRE2, awbg),
> + RPPX1_PARAMS_BLOCK_INFO(AWBG_POST, awbg),
> RPPX1_PARAMS_BLOCK_INFO(CCOR_POST, ccor),
> RPPX1_PARAMS_BLOCK_INFO(HIST_PRE1, hist),
> RPPX1_PARAMS_BLOCK_INFO(HIST_PRE2, hist),
> --
> 2.25.1
>
>
prev parent reply other threads:[~2026-08-18 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 2:09 [PATCH v2] media: rppx1: describe the MAIN_POST white balance gains block Linmao Li
2026-08-18 8:17 ` Niklas Söderlund
2026-08-18 9:37 ` Jacopo Mondi [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=aoQniglSwAEH3V0D@zed \
--to=jacopo.mondi@ideasonboard.com \
--cc=jacopo.mondi+renesas@ideasonboard.com \
--cc=jai.luthra+renesas@ideasonboard.com \
--cc=lilinmao@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sakari.ailus@linux.intel.com \
/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.