All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sylwester Nawrocki <snjw23@gmail.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 19:17:46 +0100	[thread overview]
Message-ID: <10910238.HhAgf4n5o5@avalon> (raw)
In-Reply-To: <4F5005A3.9060503@gmail.com>

Hi Sylwester,

On Friday 02 March 2012 00:26:27 Sylwester Nawrocki wrote:
> 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.

It could indeed be a little bit confusing for users/applications, but having a 
separate private focus control wouldn't be much better :-) In both cases an 
application will need to know how to use the focus controls anyway.

-- 
Regards,

Laurent Pinchart


      reply	other threads:[~2012-03-02 18:17 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
2012-03-02 18:17       ` Laurent Pinchart [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=10910238.HhAgf4n5o5@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=snjw23@gmail.com \
    --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 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.