All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@iki.fi>
To: Shravan.Chippa@microchip.com
Cc: paul.j.murphy@intel.com, daniele.alessandrelli@intel.com,
	mchehab@kernel.org, linux-media@vger.kernel.org,
	linux-kernel@vger.kernel.org, Conor.Dooley@microchip.com,
	Prakash.Battu@microchip.com
Subject: Re: [PATCH v4] media: i2c: imx334: support lower bandwidth mode
Date: Sun, 2 Oct 2022 15:00:12 +0300	[thread overview]
Message-ID: <Yzl9TCGtR/ddHNOG@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <PH0PR11MB56110214AA9709893DD5100281589@PH0PR11MB5611.namprd11.prod.outlook.com>

On Sun, Oct 02, 2022 at 04:42:06AM +0000, Shravan.Chippa@microchip.com wrote:
> > > > > > +830,13 @@ static int imx334_set_pad_format(struct v4l2_subdev
> > > > > > *sd,
> > > > > >
> > > > > >       mutex_lock(&imx334->mutex);
> > > > > >
> > > > > > -     mode = &supported_mode;
> > > > > > +     imx334->cur_code = imx334_get_format_code(imx334, fmt);
> > > > >
> > > > > This should be done only for the active format.
> > > > Are you expecting  if condition to check the current bus code with
> > > set_pad_fromat bus code?
> > >
> > > Only assign the cur_code field when setting the active format.
> > I have taken reference from imx219 driver cur_code will update if the requested
> > format bus code maches with available bus_codes list if not mached with
> > available bus_codes it will use defaults one only.
> > am I missing any thing here ?
> 
> R u expecting to change the current bus code when get the V4L2_SUBDEV_FORMAT_ACTIVE requested?
> I will try to modify in the next revision this case.

Yes, please.

-- 
Sakari Ailus

  reply	other threads:[~2022-10-02 12:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20  5:10 [PATCH v4] media: i2c: imx334: support lower bandwidth mode shravan kumar
2022-09-20 12:14 ` Sakari Ailus
2022-09-26 11:32   ` Shravan.Chippa
2022-09-26 16:51     ` Sakari Ailus
2022-10-01  8:51       ` Shravan.Chippa
2022-10-02  4:42         ` Shravan.Chippa
2022-10-02 12:00           ` Sakari Ailus [this message]
2022-10-02 12:28         ` Sakari Ailus
2022-10-12  9:27           ` Shravan.Chippa

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=Yzl9TCGtR/ddHNOG@valkosipuli.retiisi.eu \
    --to=sakari.ailus@iki.fi \
    --cc=Conor.Dooley@microchip.com \
    --cc=Prakash.Battu@microchip.com \
    --cc=Shravan.Chippa@microchip.com \
    --cc=daniele.alessandrelli@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=paul.j.murphy@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.