From: Sylwester Nawrocki <snjw23@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, Sakari Ailus <sakari.ailus@iki.fi>,
Hans Verkuil <hverkuil@xs4all.nl>,
Sylwester Nawrocki <sylvester.nawrocki@gmail.com>
Subject: Re: [PATCH/RFC][DRAFT] V4L: Add camera auto focus controls
Date: Fri, 02 Mar 2012 00:26:27 +0100 [thread overview]
Message-ID: <4F5005A3.9060503@gmail.com> (raw)
In-Reply-To: <1441235.tcAt0gpJAF@avalon>
Hi Laurent,
On 03/01/2012 11:30 PM, Laurent Pinchart wrote:
> One option would be to disable the focus area control when the focus distance
> is set to a value different than normal (or the other way around). Control
> change events could be used to report that to userspace. Would that work with
> your hardware ?
What would work, would be disabling the focus distance control when the focus
area is set to a value different than "all".
I have also been considering adding an extra menu entry for the focus distance
control, indicating some "neutral" state, but disabling the other control
sounds like a better idea. I couldn't find anything reasonable, as there was
already the focus distance "normal" menu entry.
Then, after the focus are is set to, for instance, "spot", transition to
the focus distance "macro" would be only possible through focus area "all"
(where the focus distance is enabled again). I guess it's acceptable.
It's only getting a bit harder for applications to present a single list
of the focus modes to the user, since they would, for instance, grey out
the entries corresponding to disabled control. It shouldn't be a big deal
though.
--
Regards,
Sylwester
next prev parent reply other threads:[~2012-03-01 23:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 21:33 [PATCH/RFC][DRAFT] V4L: Add camera auto focus controls Sylwester Nawrocki
2012-02-26 16:57 ` Sylwester Nawrocki
2012-02-26 17:10 ` Sylwester Nawrocki
2012-03-01 22:30 ` Laurent Pinchart
2012-03-01 23:26 ` Sylwester Nawrocki [this message]
2012-03-02 18:17 ` Laurent Pinchart
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=4F5005A3.9060503@gmail.com \
--to=snjw23@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=sylvester.nawrocki@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox