From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Pawel Osciak <p.osciak@samsung.com>
Cc: "'Linux Media Mailing List'" <linux-media@vger.kernel.org>,
"'Hans Verkuil'" <hverkuil@xs4all.nl>,
"'Hans de Goede'" <hdegoede@redhat.com>,
kyungmin.park@samsung.com
Subject: Re: [RFC v4] Multi-plane buffer support for V4L2 API
Date: Mon, 12 Jul 2010 18:29:07 -0300 [thread overview]
Message-ID: <4C3B8923.1040109@redhat.com> (raw)
In-Reply-To: <004b01cb1f98$e586ae10$b0940a30$%osciak@samsung.com>
Hi Pawel,
Em 09-07-2010 15:59, Pawel Osciak escreveu:
> Hello,
>
> This is the fourth version of the multi-plane API extensions proposal.
> I think that we have reached a stage at which it is more or less finalized.
>
> Rationale can be found at the beginning of the original thread:
> http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/11212
With Hans proposed changes that you've already acked, I think the proposal is ok,
except for one detail:
> 4. Format enumeration
> ----------------------------------
> struct v4l2_fmtdesc, used for format enumeration, does include the v4l2_buf_type
> enum as well, so the new types can be handled properly here as well.
> For drivers supporting both versions of the API, 1-plane formats should be
> returned for multiplanar buffer types as well, for consistency. In other words,
> for multiplanar buffer types, the formats returned are a superset of those
> returned when enumerating with the old buffer types.
>
We shouldn't mix types here. If the userspace is asking for multi-planar types,
the driver should return just the multi-planar formats.
If the userspace wants to know about both, it will just call for both types of
formats.
Cheers,
Mauro
next prev parent reply other threads:[~2010-07-12 21:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 18:59 [RFC v4] Multi-plane buffer support for V4L2 API Pawel Osciak
2010-07-10 16:25 ` Hans Verkuil
2010-07-12 9:14 ` Pawel Osciak
2010-07-12 12:23 ` Hans Verkuil
2010-07-12 21:29 ` Mauro Carvalho Chehab [this message]
2010-07-13 9:43 ` Pawel Osciak
2010-07-17 10:27 ` Hans Verkuil
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=4C3B8923.1040109@redhat.com \
--to=mchehab@redhat.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=p.osciak@samsung.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.