All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Correct way to do s_ctrl ioctl taking into account subdev 	framework?
Date: Sun, 27 Jun 2010 07:12:59 -0300	[thread overview]
Message-ID: <4C27242B.9040609@redhat.com> (raw)
In-Reply-To: <AANLkTimAXMupX9hYyfiTwZdi4d9a1v_N5sdz8k6b_Xhs@mail.gmail.com>

Em 27-06-2010 00:26, Devin Heitmueller escreveu:
> On Sat, Jun 26, 2010 at 9:34 PM, Mauro Carvalho Chehab
> <mchehab@redhat.com> wrote:
>> would do the trick. Yet, the application is broken, as it is considering a positive
>> return as an error. A positive code should never be considered as an error. So, we
>> need to fix v4l2-ctl as well (ok, returning 1 is wrong as well, as this is a non-v4l2
>> compliance in this case).
> 
> A strict interpretation of the spec would read that returning zero is
> success, -1 is an well-formed error condition, and *ANYTHING* else is
> a violation of the spec and an application used for testing compliance
> should complain very loudly (which is exactly what it does).
> 
> In effect, the only patch I would consider valid for v4l2-ctl would be
> one that makes the error even more LOUD than it already is.

It should output it as an API violation, not as a failure on setting the value.
That's said, I think that a few ioctl calls used to return positive values under
certain special conditions. Not sure if this is a non-compliance or if the 
API allows it.

Cheers,
Mauro

  reply	other threads:[~2010-06-27 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 18:37 Correct way to do s_ctrl ioctl taking into account subdev framework? Devin Heitmueller
2010-06-26 18:51 ` Hans Verkuil
2010-06-26 19:04   ` Devin Heitmueller
2010-06-27  1:34     ` Mauro Carvalho Chehab
2010-06-27  3:26       ` Devin Heitmueller
2010-06-27 10:12         ` Mauro Carvalho Chehab [this message]
2010-06-27  9:12     ` 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=4C27242B.9040609@redhat.com \
    --to=mchehab@redhat.com \
    --cc=dheitmueller@kernellabs.com \
    --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.