Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	Hans Verkuil <hans@jjverkuil.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v2 2/2] Revert "media: renesas: vsp1: brx: Fix format propagation"
Date: Wed, 27 May 2026 09:48:17 +0200	[thread overview]
Message-ID: <20260527074817.GA468138@killaraus.ideasonboard.com> (raw)
In-Reply-To: <0977c2c0-79ea-4435-9e1c-f54ca5e18342@leemhuis.info>

Hi Thorsten,

On Wed, May 27, 2026 at 09:35:03AM +0200, Thorsten Leemhuis wrote:
> On 5/6/26 23:56, Laurent Pinchart wrote:
> > This reverts commit 937f3e6b51f1cea079be9ba642665f2bf8bcc31f.
> > 
> > The change to format propagation in the BRx broke configuration of the
> > DRM pipeline. Revert it to fix the regression.
> 
> Laurent, is this still on your radar? From the outside it looks like
> this fix for the 7.1 regression should ideally go to Linus this week, as
> he ideally wants all known regression fixed by -rc6.
> 
> But it's easy to miss things from the outside, so if this is not a
> proper regression, the revert obsolete, or something like that, just
> mention it.

Thank you for the reminder. Hans, Mauro, this series seems to not have
been merged in the media fixes branch. Could you pick it up ?

> > The original commit was meant to fix a v4l2-compliance failure, with no
> > known userspace applications being affected beside test tools. Reverting
> > is the simplest option, a more comprehensive fix can be developed (and
> > tested more thoroughly) later.
> > 
> > Reported-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> > Closes: https://lore.kernel.org/linux-media/CA+V-a8t481xuwava0nb7uY9CUPqFWZ_8EP0xrK3BgumP7HDcLg@mail.gmail.com
> > Fixes: 937f3e6b51f1 ("media: renesas: vsp1: brx: Fix format propagation")
> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> >  drivers/media/platform/renesas/vsp1/vsp1_brx.c | 10 ++--------
> >  1 file changed, 2 insertions(+), 8 deletions(-)
> > 
> > diff --git a/drivers/media/platform/renesas/vsp1/vsp1_brx.c b/drivers/media/platform/renesas/vsp1/vsp1_brx.c
> > index b1a2c68e9944..9d93cb8b8e82 100644
> > --- a/drivers/media/platform/renesas/vsp1/vsp1_brx.c
> > +++ b/drivers/media/platform/renesas/vsp1/vsp1_brx.c
> > @@ -156,20 +156,14 @@ static int brx_set_format(struct v4l2_subdev *subdev,
> >  		compose->height = format->height;
> >  	}
> >  
> > -	/*
> > -	 * Propagate the format code to all pads, and the whole format to the
> > -	 * source pad.
> > -	 */
> > +	/* Propagate the format code to all pads. */
> >  	if (fmt->pad == BRX_PAD_SINK(0)) {
> >  		unsigned int i;
> >  
> > -		for (i = 0; i < brx->entity.source_pad; ++i) {
> > +		for (i = 0; i <= brx->entity.source_pad; ++i) {
> >  			format = v4l2_subdev_state_get_format(state, i);
> >  			format->code = fmt->format.code;
> >  		}
> > -
> > -		format = v4l2_subdev_state_get_format(state, i);
> > -		*format = fmt->format;
> >  	}
> >  
> >  done:

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2026-05-27  7:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 21:56 [PATCH v2 0/2] media: renesas: vsp1: Fix display pipeline regression Laurent Pinchart
2026-05-06 21:56 ` [PATCH v2 1/2] Revert "media: renesas: vsp1: Initialize format on all pads" Laurent Pinchart
2026-05-07 16:01   ` Lad, Prabhakar
2026-05-06 21:56 ` [PATCH v2 2/2] Revert "media: renesas: vsp1: brx: Fix format propagation" Laurent Pinchart
2026-05-07 16:02   ` Lad, Prabhakar
2026-05-27  7:35   ` Thorsten Leemhuis
2026-05-27  7:48     ` Laurent Pinchart [this message]
2026-05-29 10:30       ` Laurent Pinchart

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=20260527074817.GA468138@killaraus.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hans@jjverkuil.nl \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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