mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mirela Rabulea <mirela.rabulea@nxp.com>
To: "mchehab@kernel.org" <mchehab@kernel.org>,
	"slongerbeam@gmail.com" <slongerbeam@gmail.com>,
	"hugues.fruchet@foss.st.com" <hugues.fruchet@foss.st.com>,
	"jacopo+renesas@jmondi.org" <jacopo+renesas@jmondi.org>
Cc: "Xavier Roumegue (OSS)" <xavier.roumegue@oss.nxp.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"G.N. Zhou" <guoniu.zhou@nxp.com>,
	Manish Bajaj <manish.bajaj@nxp.com>,
	Robert Chiras <robert.chiras@nxp.com>,
	dl-linux-imx <linux-imx@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH] media: ov5640: Fix set format, v4l2_mbus_pixelcode not updated
Date: Wed, 10 Nov 2021 18:03:50 +0000	[thread overview]
Message-ID: <08d2044ef00b438df4403e8533d6d07b37be4bee.camel@nxp.com> (raw)
In-Reply-To: <7f74b844-809b-6255-fe4a-e4cef55cbae7@foss.st.com>

Hi Hugues,

On Tue, 2021-11-09 at 15:19 +0100, Hugues FRUCHET - FOSS wrote:
> 
> Hi Mirela,
> 
> Thanks for patch, tested OK on my side:

Thanks, for testing!

Regards,
Mirela

> 
> Acked-by: Hugues Fruchet <hugues.fruchet@st.com>
> Tested-by: Hugues Fruchet <hugues.fruchet@st.com>
> 
> BR,
> Hugues.
> > 
> > -----Original Message-----
> > From: Mirela Rabulea (OSS) <mirela.rabulea@oss.nxp.com>
> > Sent: lundi 1 novembre 2021 20:53
> > To: slongerbeam@gmail.com; mchehab@kernel.org; Hugues FRUCHET <
> > hugues.fruchet@st.com>; jacopo+renesas@jmondi.org
> > Cc: guoniu.zhou@nxp.com; manish.bajaj@nxp.com; 
> > robert.chiras@nxp.com; xavier.roumegue@oss.nxp.com; 
> > linux-media@vger.kernel.org; linux-kernel@vger.kernel.org; 
> > linux-imx@nxp.com; Mirela Rabulea <mirela.rabulea@nxp.com>
> > Subject: [PATCH] media: ov5640: Fix set format, v4l2_mbus_pixelcode
> > not updated
> > 
> > From: Mirela Rabulea <mirela.rabulea@nxp.com>
> > 
> > In ov5640_set_fmt, pending_fmt_change will always be false, because
> > the sensor format is saved before comparing it with the previous
> > format:
> >       fmt = &sensor->fmt;...
> >       *fmt = *mbus_fmt;...
> >       if (mbus_fmt->code != sensor->fmt.code)
> >               sensor->pending_fmt_change = true;
> > This causes the sensor to capture with the previous pixelcode.
> > 
> > Also, changes might happen even for V4L2_SUBDEV_FORMAT_TRY, so fix
> > that.
> > 
> > Basically, revert back to the state before commit 071154499193
> > ("media: ov5640: Fix set format regression") as it was more clear,
> > and then update format even when pixelcode does not change, as
> > resolution might change.
> > 
> > Fixes: 071154499193 ("media: ov5640: Fix set format regression")
> > Fixes: 6949d864776e ("media: ov5640: do not change mode if format
> > or frame interval is unchanged")
> > Fixes: fb98e29ff1ea5 ("media: ov5640: fix mode change regression")
> > 
> > Signed-off-by: Mirela Rabulea <mirela.rabulea@nxp.com>
> > ---
> >   drivers/media/i2c/ov5640.c | 14 +++++++-------
> >   1 file changed, 7 insertions(+), 7 deletions(-)
> > 
> > diff --git a/drivers/media/i2c/ov5640.c
> > b/drivers/media/i2c/ov5640.c index ddbd71394db3..db5a19babe67
> > 100644
> > --- a/drivers/media/i2c/ov5640.c
> > +++ b/drivers/media/i2c/ov5640.c
> > @@ -2293,7 +2293,6 @@ static int ov5640_set_fmt(struct v4l2_subdev
> > *sd,
> >       struct ov5640_dev *sensor = to_ov5640_dev(sd);
> >       const struct ov5640_mode_info *new_mode;
> >       struct v4l2_mbus_framefmt *mbus_fmt = &format->format;
> > -     struct v4l2_mbus_framefmt *fmt;
> >       int ret;
> > 
> >       if (format->pad != 0)
> > @@ -2311,12 +2310,10 @@ static int ov5640_set_fmt(struct
> > v4l2_subdev *sd,
> >       if (ret)
> >               goto out;
> > 
> > -     if (format->which == V4L2_SUBDEV_FORMAT_TRY)
> > -             fmt = v4l2_subdev_get_try_format(sd, sd_state, 0);
> > -     else
> > -             fmt = &sensor->fmt;
> > -
> > -     *fmt = *mbus_fmt;
> > +     if (format->which == V4L2_SUBDEV_FORMAT_TRY) {
> > +             *v4l2_subdev_get_try_format(sd, sd_state, 0) =
> > *mbus_fmt;
> > +             goto out;
> > +     }
> > 
> >       if (new_mode != sensor->current_mode) {
> >               sensor->current_mode = new_mode;
> > @@ -2325,6 +2322,9 @@ static int ov5640_set_fmt(struct v4l2_subdev
> > *sd,
> >       if (mbus_fmt->code != sensor->fmt.code)
> >               sensor->pending_fmt_change = true;
> > 
> > +     /* update format even if code is unchanged, resolution might
> > change */
> > +     sensor->fmt = *mbus_fmt;
> > +
> >       __v4l2_ctrl_s_ctrl_int64(sensor->ctrls.pixel_rate,
> >                                ov5640_calc_pixel_rate(sensor));
> >   out:
> > --
> > 2.25.1
> > 

  reply	other threads:[~2021-11-10 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01 19:52 Mirela Rabulea (OSS)
     [not found] ` <PAXPR10MB4734B68AC186DCDA40A97CDFFE919@PAXPR10MB4734.EURPRD10.PROD.OUTLOOK.COM>
2021-11-09 14:19   ` Hugues FRUCHET - FOSS
2021-11-10 18:03     ` Mirela Rabulea [this message]
2021-12-14 18:36 ` Jacopo Mondi

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=08d2044ef00b438df4403e8533d6d07b37be4bee.camel@nxp.com \
    --to=mirela.rabulea@nxp.com \
    --cc=guoniu.zhou@nxp.com \
    --cc=hugues.fruchet@foss.st.com \
    --cc=jacopo+renesas@jmondi.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=manish.bajaj@nxp.com \
    --cc=mchehab@kernel.org \
    --cc=robert.chiras@nxp.com \
    --cc=slongerbeam@gmail.com \
    --cc=xavier.roumegue@oss.nxp.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

all inboxes | Powered by JetHome®