From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH v2] mt9v032: Export horizontal and vertical blanking as V4L2 controls
Date: Fri, 27 Jul 2012 01:02:04 +0200 [thread overview]
Message-ID: <4375414.cY8huNNgj1@avalon> (raw)
In-Reply-To: <20120726205401.GA26136@valkosipuli.retiisi.org.uk>
Hi Sakari,
On Thursday 26 July 2012 23:54:01 Sakari Ailus wrote:
> On Tue, Jul 24, 2012 at 01:10:42AM +0200, Laurent Pinchart wrote:
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > ---
> >
> > drivers/media/video/mt9v032.c | 36 +++++++++++++++++++++++++++++++++---
> > 1 files changed, 33 insertions(+), 3 deletions(-)
> >
> > Changes since v1:
> >
> > - Make sure the total horizontal time will not go below 660 when setting
> > the horizontal blanking control
> >
> > - Restrict the vertical blanking value to 3000 as documented in the
> > datasheet. Increasing the exposure time actually extends vertical
> > blanking, as long as the user doesn't forget to turn auto-exposure
> > off...
>
> Does binning either horizontally or vertically affect the blanking limits?
> If the process is analogue then the answer is typically "yes".
The datasheet doesn't specify whether binning and blanking can influence each
other.
> It's not directly related to this patch, but the effect of the driver just
> exposing one sub-device really shows better now. Besides lacking the way to
> specify binning as in the V4L2 subdev API (compose selection target), the
> user also can't use the crop bounds selection target to get the size of the
> pixel array.
>
> We could either accept this for the time being and fix it later on of fix it
> now.
>
> I prefer fixing it right now but admit that this patch isn't breaking
> anything, it rather is missing quite relevant functionality to control the
> sensor in a generic way.
I'd rather apply this patch first, as it doesn't break anything :-) Fixing the
problem will require discussions, and that will take time.
Binning/skipping is a pretty common feature in sensors. Exposing two sub-
devices like the SMIA++ driver does is one way to fix the problem, but do we
really want to do that for the vast majority of sensors ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2012-07-26 23:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 18:34 [PATCH 0/4] Aptinate sensors patches Laurent Pinchart
2012-07-23 18:34 ` [PATCH 1/4] v4l2-ctrls: Add v4l2_ctrl_[gs]_ctrl_int64() Laurent Pinchart
2012-07-23 18:35 ` [PATCH 2/4] mt9v032: Provide pixel rate control Laurent Pinchart
2012-07-23 18:35 ` [PATCH 3/4] mt9v032: Export horizontal and vertical blanking as V4L2 controls Laurent Pinchart
2012-07-23 23:10 ` [PATCH v2] " Laurent Pinchart
2012-07-26 20:54 ` Sakari Ailus
2012-07-26 23:02 ` Laurent Pinchart [this message]
2012-07-27 21:27 ` Sakari Ailus
2012-07-28 19:09 ` Laurent Pinchart
2012-08-13 14:18 ` Sakari Ailus
2012-08-13 23:26 ` Laurent Pinchart
2012-08-14 12:46 ` Sakari Ailus
2012-07-23 18:35 ` [PATCH 4/4] mt9p031: Fix horizontal and vertical blanking configuration Laurent Pinchart
2012-07-26 20:58 ` [PATCH 0/4] Aptinate sensors patches Sakari Ailus
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=4375414.cY8huNNgj1@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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;
as well as URLs for NNTP newsgroup(s).