[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200608080043.GN9947@valkosipuli.retiisi.org.uk>
Date: Mon, 8 Jun 2020 11:00:43 +0300
From: Sakari Ailus <sakari.ailus@....fi>
To: Andrey Konovalov <andrey.konovalov@...aro.org>
Cc: mchehab@...nel.org, manivannan.sadhasivam@...aro.org,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
c.barrett@...mos.com, a.brela@...mos.com, peter.griffin@...aro.org
Subject: Re: [PATCH v3 08/10] media: i2c: imx290: Add support to enumerate
all frame sizes
On Sun, Jun 07, 2020 at 07:28:56PM +0300, Andrey Konovalov wrote:
> Hi Sakari,
>
> Thank you for the review!
>
> On 26.05.2020 12:17, Sakari Ailus wrote:
> > Hi Andrey,
> >
> > On Sun, May 24, 2020 at 10:25:03PM +0300, Andrey Konovalov wrote:
> > > From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
> > >
> > > Add support to enumerate all frame sizes supported by IMX290. This is
> > > required for using with userspace tools such as libcamera.
> > >
> > > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
> > > Signed-off-by: Andrey Konovalov <andrey.konovalov@...aro.org>
> > > ---
> > > drivers/media/i2c/imx290.c | 20 ++++++++++++++++++++
> > > 1 file changed, 20 insertions(+)
> > >
> > > diff --git a/drivers/media/i2c/imx290.c b/drivers/media/i2c/imx290.c
> > > index 6e70ff22bc5f..88850f3b1427 100644
> > > --- a/drivers/media/i2c/imx290.c
> > > +++ b/drivers/media/i2c/imx290.c
> > > @@ -471,6 +471,25 @@ static int imx290_enum_mbus_code(struct v4l2_subdev *sd,
> > > return 0;
> > > }
> > > +static int imx290_enum_frame_size(struct v4l2_subdev *subdev,
> > > + struct v4l2_subdev_pad_config *cfg,
> > > + struct v4l2_subdev_frame_size_enum *fse)
> > > +{
> > > + if ((fse->code != imx290_formats[0].code) &&
> > > + (fse->code != imx290_formats[1].code))
> > > + return -EINVAL;
> >
> > Please skip the modes that do not have the code specified by the user. They
> > should not be enumerated here.
>
> I've double checked this part of the code, and it doesn't seem to need changes.
> The reason is that for the both codes the set of the modes and the frame sizes is
> exactly the same. And the fse->code check above just guards against the codes not
> supported by the driver at all.
Indeed. Please then ignore the comment.
--
Sakari Ailus
Powered by blists - more mailing lists