From: Dan Scally <dan.scally@ideasonboard.com>
To: David Carlier <devnexen@gmail.com>, linux-media@vger.kernel.org
Cc: jacopo.mondi@ideasonboard.com, mchehab@kernel.org,
hverkuil+cisco@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] media: mali-c55: Disable colour space conversion for RGB outputs
Date: Wed, 7 Oct 2026 10:11:44 +0100 [thread overview]
Message-ID: <a44bdd3f-c28d-4f45-9c1c-174f5d979617@ideasonboard.com> (raw)
In-Reply-To: <20261006234242.11934-1-devnexen@gmail.com>
Morning David, thanks for the patch
On 07/10/2026 00:42, David Carlier wrote:
> The colour space conversion block is only programmed for YUV formats,
> and its configuration is kept across streaming sessions. An RGB stream
> started after a YUV one thus still converts its output to YUV.
>
> Clear the conversion configuration for non-YUV formats.
>
> Fixes: d5f281f3dd29 ("media: mali-c55: Add Mali-C55 ISP driver")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: David Carlier <devnexen@gmail.com>
> ---
> drivers/media/platform/arm/mali-c55/mali-c55-capture.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/media/platform/arm/mali-c55/mali-c55-capture.c b/drivers/media/platform/arm/mali-c55/mali-c55-capture.c
> index ff01553026fb..2425a069a939 100644
> --- a/drivers/media/platform/arm/mali-c55/mali-c55-capture.c
> +++ b/drivers/media/platform/arm/mali-c55/mali-c55-capture.c
> @@ -577,6 +577,10 @@ static void mali_c55_cap_dev_format_configure(struct mali_c55_cap_dev *cap_dev)
> MALI_C55_REG_CS_CONV_CONFIG,
> MALI_C55_CS_CONV_FILTER_MASK,
> MALI_C55_CS_CONV_FILTER_ENABLE);
> + } else {
> + /* Don't inherit the conversion set up by a previous YUV stream. */
> + mali_c55_cap_dev_write(cap_dev, MALI_C55_REG_CS_CONV_CONFIG,
> + 0);
Makes sense to me:
Reviewed-by: Daniel Scally <dan.scally@ideasonboard.com>
> }
> }
>
prev parent reply other threads:[~2026-10-07 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 23:42 David Carlier
2026-10-07 9:11 ` Dan Scally [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=a44bdd3f-c28d-4f45-9c1c-174f5d979617@ideasonboard.com \
--to=dan.scally@ideasonboard.com \
--cc=devnexen@gmail.com \
--cc=hverkuil+cisco@kernel.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®