From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: William Swanson <william.swanson@fuel7.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Ken Petit <ken@fuel7.com>,
sakari.ailus@iki.fi
Subject: Re: [PATCH] omap3isp: Add support for interlaced input data
Date: Wed, 09 Jan 2013 23:35:26 +0100 [thread overview]
Message-ID: <2574136.Nmpnc7I1z4@avalon> (raw)
In-Reply-To: <50ECA285.2000909@fuel7.com>
Hi William,
On Tuesday 08 January 2013 14:49:41 William Swanson wrote:
> On 01/07/2013 04:20 AM, Laurent Pinchart wrote:
> > What do you get in the memory buffers ? Are fields captured in separate
> > buffers or combined in a single buffer ? If they're combined, are they
> > interleaved or sequential in memory ?
>
> I believe the data is combined in a single buffer, with alternate fields
> interleaved.
Could you please double-check that ? I'd like to be sure, not just believe :-)
In that case the OMAP3 ISP driver should set the v4l2_pix_format::field to
V4L2_FIELD_INTERLACED in the format-related ioctl when an interlaced format is
used. I suppose this could be added later - Sakari, any opinion ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-01-09 22:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 2:12 [PATCH] omap3isp: Add support for interlaced input data William Swanson
2012-12-25 21:05 ` Laurent Pinchart
2012-12-27 20:27 ` Mauro Carvalho Chehab
2013-01-04 19:52 ` William Swanson
2013-01-07 12:20 ` Laurent Pinchart
2013-01-08 22:49 ` William Swanson
2013-01-09 22:35 ` Laurent Pinchart [this message]
2013-01-14 22:21 ` William Swanson
2013-01-14 22:23 ` William Swanson
2013-01-21 10:06 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2013-01-05 0:09 William Swanson
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=2574136.Nmpnc7I1z4@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=ken@fuel7.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=sakari.ailus@iki.fi \
--cc=william.swanson@fuel7.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.