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,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: [PATCH v2] media: rppx1: bls: read the raw pattern from the PRE2 acquisition module
Date: Tue, 18 Aug 2026 12:05:15 +0200 [thread overview]
Message-ID: <aoQuSs1aSw2Z4Wyq@zed> (raw)
In-Reply-To: <20260818095929.3194503-1-lilinmao@kylinos.cn>
Hi Linmao
On Tue, Aug 18, 2026 at 05:59:29PM +0800, Linmao Li wrote:
> rppx1_bls_swap_regs() gets the Bayer pattern from the acquisition
> module. The PRE1 path uses pre1.acq, but the PRE2 path mistakenly uses
> pre2.bls. The BLS module does not store a Bayer pattern, so PRE2 would
> read zero (RGGB) and map fixed black levels to the wrong colour
> registers.
>
> PRE2 is not started or dispatched yet, so the bug is currently latent.
> Read the pattern from pre2.acq, as the PRE1 path does, so that enabling
> PRE2 does not start out with the wrong register mapping.
>
> Signed-off-by: Linmao Li <lilinmao@kylinos.cn>
> Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Thanks
Reviewed-by: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
> ---
> Changes since v1 [1]:
> - no code changes;
> - dropped the Fixes: tag, the patch is expected to be collected together
> with the driver for v7.3;
> - picked up Niklas' Reviewed-by;
> - resent after Jacopo offered to collect this one as well [2].
>
> v1 was patch 2/2 of "media: rppx1: parameters block fixes"; its patch
> 1/2 is on the list separately as "[PATCH v2] media: rppx1: describe the
> MAIN_POST white balance gains block".
>
> [1] https://lore.kernel.org/linux-media/20260817104529.3132552-3-lilinmao@kylinos.cn/
> [2] https://lore.kernel.org/linux-media/aoQniglSwAEH3V0D@zed/
>
> drivers/media/platform/dreamchip/rppx1/rppx1_bls.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/dreamchip/rppx1/rppx1_bls.c b/drivers/media/platform/dreamchip/rppx1/rppx1_bls.c
> index 01a61db279bf7..71c5561457d52 100644
> --- a/drivers/media/platform/dreamchip/rppx1/rppx1_bls.c
> +++ b/drivers/media/platform/dreamchip/rppx1/rppx1_bls.c
> @@ -70,7 +70,7 @@ rppx1_bls_swap_regs(struct rpp_module *mod, const u32 input[4], u32 output[4])
>
> /* Swap to pattern used in our path, PRE1 or PRE2. */
> struct rpp_module *acq = mod == &mod->rpp->pre1.bls ?
> - &mod->rpp->pre1.acq : &mod->rpp->pre2.bls;
> + &mod->rpp->pre1.acq : &mod->rpp->pre2.acq;
> enum rpp_raw_pattern pattern = acq->info.acq.raw_pattern;
>
> for (unsigned int i = 0; i < 4; ++i)
> --
> 2.25.1
>
>
prev parent reply other threads:[~2026-08-18 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 9:59 [PATCH v2] media: rppx1: bls: read the raw pattern from the PRE2 acquisition module Linmao Li
2026-08-18 10:05 ` 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=aoQuSs1aSw2Z4Wyq@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+renesas@ragnatech.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox