All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] DocBook media: Clarify V4L2_FIELD_ANY for drivers
Date: Fri, 31 Oct 2014 15:49:12 +0000	[thread overview]
Message-ID: <5445654.FH7TshJYAP@f19simon> (raw)
In-Reply-To: <5453A289.5020007@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 1835 bytes --]

On Friday 31 October 2014 15:54:01 Hans Verkuil wrote:
> On 10/31/2014 03:48 PM, Simon Farnsworth wrote:
> > Documentation for enum v4l2_field did not make it clear that V4L2_FIELD_ANY
> > is only acceptable as input to the kernel, not as a response from the
> > driver.
> > 
> > Make it clear, to stop userspace developers like me assuming it can be
> > returned by the driver.
> > 
> > Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
> > ---
> >  Documentation/DocBook/media/v4l/io.xml | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/Documentation/DocBook/media/v4l/io.xml b/Documentation/DocBook/media/v4l/io.xml
> > index e5e8325..8918bb2 100644
> > --- a/Documentation/DocBook/media/v4l/io.xml
> > +++ b/Documentation/DocBook/media/v4l/io.xml
> > @@ -1422,7 +1422,10 @@ one of the <constant>V4L2_FIELD_NONE</constant>,
> >  <constant>V4L2_FIELD_BOTTOM</constant>, or
> >  <constant>V4L2_FIELD_INTERLACED</constant> formats is acceptable.
> >  Drivers choose depending on hardware capabilities or e.&nbsp;g. the
> > -requested image size, and return the actual field order. &v4l2-buffer;
> > +requested image size, and return the actual field order. If multiple
> > +field orders are possible the driver must choose one of the possible
> > +field orders during &VIDIOC-S-FMT; or &VIDIOC-TRY-FMT; and must not
> > +return V4L2_FIELD_ANY. &v4l2-buffer;
> 
> I would phrase it slightly differently:
> 
> "Drivers must never return <constant>V4L2_FIELD_ANY</constant>. If multiple
> field orders are possible the driver must choose one of the possible
> field orders during &VIDIOC-S-FMT; or &VIDIOC-TRY-FMT;."
> 

I like your wording better than mine. v2 patch sent.

-- 
Simon Farnsworth
Software Engineer
ONELAN Ltd
http://www.onelan.com

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2014-10-31 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 14:48 [PATCH] DocBook media: Clarify V4L2_FIELD_ANY for drivers Simon Farnsworth
2014-10-31 14:54 ` Hans Verkuil
2014-10-31 15:49   ` Simon Farnsworth [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=5445654.FH7TshJYAP@f19simon \
    --to=simon.farnsworth@onelan.co.uk \
    --cc=hverkuil@xs4all.nl \
    --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 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.