From: gilles <gilles.gigan@gmail.com>
To: linux-media@vger.kernel.org
Subject: Comments on V4L controls
Date: Fri, 13 Feb 2009 09:44:55 +1100 [thread overview]
Message-ID: <4994A667.2000909@gmail.com> (raw)
Hi everyone,
Sorry for double posting, but I originally sent this to the old mailing
list. Here it is:
I have a couple of comments / suggestions regarding the part on controls of
the V4L2 api:
Some controls, such as pan relative and tilt relative are write-only, and
reading their value makes little sense. Yet, there is no way of knowing
about this, but to try and read a value and be greeted with EINVAL or
similar. There is already a read-only flag (V4L2_CTRL_FLAG_READ_ONLY) in
struct v4l2_query. Does it make sense to add another one for write-only
controls ?
The extended controls Pan / Tilt reset are defined in the API as boolean
controls. Shouldnt these be defined as buttons instead, as they dont really
hold a state (enabled/disabled) ?
Comments are welcome.
Cheers,
Gilles
next reply other threads:[~2009-02-12 22:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 22:44 gilles [this message]
2009-02-18 14:51 ` Comments on V4L controls Laurent Pinchart
2009-02-20 6:56 ` 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=4994A667.2000909@gmail.com \
--to=gilles.gigan@gmail.com \
--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