linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Christian Rhodin <Crhodin@aptina.com>, linux-media@vger.kernel.org
Subject: Re: Pixel Formats
Date: Fri, 12 Apr 2013 12:17:15 +0200	[thread overview]
Message-ID: <1521576.ES8kTFfaXd@avalon> (raw)
In-Reply-To: <Pine.LNX.4.64.1303072227570.20470@axis700.grange>

(A bit late, sorry)

On Thursday 07 March 2013 22:37:26 Guennadi Liakhovetski wrote:
> On Wed, 6 Mar 2013, Christian Rhodin wrote:
> > Hi,
> > 
> > I'm looking for some guidance on the correct way to handle a new pixel
> > format.  What I'm dealing with is a CMOS image sensor that supports
> > dynamic switching between linear and iHDR modes.  iHDR stands for
> > "interlaced High Dynamic Range" and is a mode where odd and even lines
> > have different exposure times, typically with an 8:1 ratio.  When I
> > started implementing a driver for this sensor I used
> > "V4L2_MBUS_FMT_SGRBG10_1X10" as the format for the linear mode and
> > defined a new format "V4L2_MBUS_FMT_SGRBG10_IHDR_1X10" for the iHDR
> > mode.  I used the format to control which mode I put the sensor in.  But
> > now I'm having trouble switching modes without reinitializing the
> > sensor.  Does anyone (everyone?) have an opinion about the correct way
> > to implement this?  I'm thinking that the format is overloaded because
> > it represents both the size and type of the data.  Should I use a single
> > format and add a control to switch the mode?
> 
> I would vote for a single format with a control, maybe even somehow
> cluster it with the normal exposure, but I'm not an expert in that, not
> sure if it would make sense.

>From the above explanation about iHDR I assume that enabling iHDR mode 
produces an image with the same resolution as linear mode, not an image with 8 
times the number of lines compared to the linear mode. Please correct me if 
I'm wrong.

If my understanding of iHDR mode is correct, I agree with Guennadi. I don't 
think enabling iHDR changes the format, it "just" modifies the exposure time 
algorithm. A V4L2 control would thus be better than adding an iHDR variant to 
all existing formats.

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2013-04-12 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-07  3:59 Pixel Formats Christian Rhodin
2013-03-07 21:37 ` Guennadi Liakhovetski
2013-04-12 10:17   ` 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=1521576.ES8kTFfaXd@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=Crhodin@aptina.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-media@vger.kernel.org \
    /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).