public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Todor Tomov <ttomov@mm-sol.com>
Cc: Todor Tomov <todor.tomov@linaro.org>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	mchehab@osg.samsung.com, hverkuil@xs4all.nl,
	geert@linux-m68k.org, matrandg@cisco.com, sakari.ailus@iki.fi,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v7 2/2] media: Add a driver for the ov5645 camera sensor.
Date: Fri, 03 Feb 2017 12:42:22 +0200	[thread overview]
Message-ID: <8305074.Jmm0xYKjpK@avalon> (raw)
In-Reply-To: <5893559F.7040607@mm-sol.com>

Hi Todor,

On Thursday 02 Feb 2017 17:51:59 Todor Tomov wrote:
> Hi,
> 
> Just to point it here - there is one more one-line correction needed below:
>
> On 11/14/2016 12:24 PM, Todor Tomov wrote:
> > The ov5645 sensor from Omnivision supports up to 2592x1944
> > and CSI2 interface.
> > 
> > The driver adds support for the following modes:
> > - 1280x960
> > - 1920x1080
> > - 2592x1944
> > 
> > Output format is packed 8bit UYVY.
> > 
> > Signed-off-by: Todor Tomov <todor.tomov@linaro.org>
> > ---
> > 
> >  drivers/media/i2c/Kconfig  |   12 +
> >  drivers/media/i2c/Makefile |    1 +
> >  drivers/media/i2c/ov5645.c | 1352 +++++++++++++++++++++++++++++++++++++++
> >  3 files changed, 1365 insertions(+)
> >  create mode 100644 drivers/media/i2c/ov5645.c
> 
> <snip>
> 
> > diff --git a/drivers/media/i2c/ov5645.c b/drivers/media/i2c/ov5645.c
> > new file mode 100644
> > index 0000000..2b33bc6
> > --- /dev/null
> > +++ b/drivers/media/i2c/ov5645.c
> > @@ -0,0 +1,1352 @@
> 
> <snip>
> 
> > +static int ov5645_entity_init_cfg(struct v4l2_subdev *subdev,
> > +				  struct v4l2_subdev_pad_config *cfg)
> > +{
> > +	struct v4l2_subdev_format fmt = { 0 };
> > +	struct ov5645 *ov5645 = to_ov5645(subdev);
> 
> This variable is unused and should be removed.

I've applied the two patches to my tree and fixed this. My plan is to send a 
pull request for v4.12 to give Rob time to ack the DT bindings.

> > +
> > +	fmt.which = cfg ? V4L2_SUBDEV_FORMAT_TRY : V4L2_SUBDEV_FORMAT_ACTIVE;
> > +	fmt.format.width = 1920;
> > +	fmt.format.height = 1080;
> > +
> > +	ov5645_set_format(subdev, cfg, &fmt);
> > +
> > +	return 0;
> > +}
> 
> <snip>

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2017-02-03 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-14 10:24 [PATCH v7 0/2] OV5645 camera sensor driver Todor Tomov
2016-11-14 10:24 ` [PATCH v7 1/2] media: i2c/ov5645: add the device tree binding document Todor Tomov
2016-11-14 12:29   ` Laurent Pinchart
2017-02-02 12:13   ` Todor Tomov
2016-11-14 10:24 ` [PATCH v7 2/2] media: Add a driver for the ov5645 camera sensor Todor Tomov
2016-11-14 12:38   ` Laurent Pinchart
2016-11-14 12:53     ` Todor Tomov
2017-02-02 15:51   ` Todor Tomov
2017-02-03 10:42     ` Laurent Pinchart [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=8305074.Jmm0xYKjpK@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=galak@codeaurora.org \
    --cc=geert@linux-m68k.org \
    --cc=hverkuil@xs4all.nl \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=linux-media@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=matrandg@cisco.com \
    --cc=mchehab@osg.samsung.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=todor.tomov@linaro.org \
    --cc=ttomov@mm-sol.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