From: Hans de Goede <hdegoede@redhat.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Jean-Francois Moine <moinejf@free.fr>, linux-media@vger.kernel.org
Subject: Re: [PATCH] Illuminators and status LED controls
Date: Tue, 07 Sep 2010 13:59:19 +0200 [thread overview]
Message-ID: <4C862917.5050903@redhat.com> (raw)
In-Reply-To: <201009071147.22643.hverkuil@xs4all.nl>
Hi all,
On 09/07/2010 11:47 AM, Hans Verkuil wrote:
> On Tuesday, September 07, 2010 11:44:18 Hans de Goede wrote:
>> Replying to myself.
>>
>> On 09/07/2010 11:42 AM, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 09/07/2010 09:30 AM, Hans Verkuil wrote:
>>>> On Monday, September 06, 2010 20:11:05 Jean-Francois Moine wrote:
>>>>> Hi,
>>>>>
>>>>> This new proposal cancels the previous 'LED control' patch.
>>>>>
>>>>> Cheers.
>>>>>
>>>>>
>>>>
>>>> Hi Jean-Francois,
>>>>
>>>> You must also add support for these new controls in v4l2-ctrls.c in
>>>> v4l2_ctrl_get_menu(), v4l2_ctrl_get_name() and v4l2_ctrl_fill().
>>>>
>>>> How is CID_ILLUMINATORS supposed to work in the case of multiple lights?
>>>> Wouldn't a bitmask type be more suitable to this than a menu type? There
>>>> isn't a bitmask type at the moment, but this seems to be a pretty good
>>>> candidate for a type like that.
>>>>
>>>> Actually, for the status led I would also use a bitmask since there may be
>>>> multiple leds. I guess you would need two bitmasks: one to select auto vs
>>>> manual, and one for the manual settings.
>>>>
>>>
>>> So far I've not seen cameras with multiple status leds, I do have seen camera
>>> which have the following settings for their 1 led (logitech uvc cams):
>>> auto
>>> on
>>> off
>>> blinking
>>>
>>> So I think a menu type is better suited, and that is what the current (private)
>>> uvc control uses.
>>
>> The same argument more or less goes for the CID_ILLIMUNATORS controls. Also given
>> that we currently don't have a bitmask type I think introducing one without a really
>> really good reason is a bad idea as any exiting apps won't know how to deal with it.
>
> But I can guarantee that we will get video devices with multiple leds in the
> future. So we need to think *now* about how to do this. One simple option is of course
> to name the controls CID_ILLUMINATOR0 and CID_LED0. That way we can easily add LED1,
> LED2, etc. later without running into weird inconsistent control names.
>
Naming them LED0 and ILLUMINATOR0 works for me. Note about the illuminator one,
if you look at the patch it made the illuminator control a menu with the following
options:
Both off
Top on, Bottom off
Top off, Bottom on
Both on
Which raises the question do we leave this as is, or do we make this 2 boolean
controls. I personally would like to vote for keeping it as is, as both lamps
illuminate the same substrate in this case, and esp. switching between
Top on, Bottom off to Top off, Bottom on in one go is a good feature to have
UI wise (iow switch from top to bottom lighting or visa versa.
Regards,
Hans
next prev parent reply other threads:[~2010-09-07 13:53 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 18:11 [PATCH] Illuminators and status LED controls Jean-Francois Moine
2010-09-07 7:16 ` Hans de Goede
2010-09-07 7:30 ` Hans Verkuil
2010-09-07 9:42 ` Hans de Goede
2010-09-07 9:44 ` Hans de Goede
2010-09-07 9:47 ` Hans Verkuil
2010-09-07 11:59 ` Hans de Goede [this message]
2010-09-07 14:50 ` Hans Verkuil
2010-09-07 13:04 ` Hans de Goede
2010-09-07 15:30 ` Hans Verkuil
2010-09-07 17:57 ` Jean-Francois Moine
2010-09-07 18:42 ` Hans Verkuil
2010-09-07 21:21 ` Hans Verkuil
2010-09-07 22:29 ` Theodore Kilgore
2010-09-08 5:17 ` Hans Verkuil
2010-09-07 21:14 ` Hans de Goede
2010-09-09 6:55 ` Hans Verkuil
2010-09-09 11:15 ` Hans de Goede
2010-09-09 13:38 ` Hans Verkuil
2010-09-13 6:53 ` Laurent Pinchart
2010-09-13 6:47 ` Laurent Pinchart
2010-09-13 6:59 ` Hans Verkuil
2010-09-07 19:12 ` Eduardo Valentin
-- strict thread matches above, loose matches on Subject: below --
2010-09-07 16:35 Andy Walls
2010-09-07 20:33 Andy Walls
2010-09-08 2:16 ` Eino-Ville Talvala
2010-09-08 7:59 ` Eduardo Valentin
2010-09-08 16:37 ` Andy Walls
2010-09-08 18:58 ` Peter Korsgaard
2010-09-08 19:27 ` Alex Deucher
2010-09-09 4:07 ` Andy Walls
2010-09-13 7:00 ` Laurent Pinchart
2010-09-09 6:07 ` Jean-Francois Moine
2010-09-09 6:25 ` Hans Verkuil
2010-09-09 6:55 ` Peter Korsgaard
2010-09-09 11:17 ` Hans de Goede
2010-09-09 13:29 ` Hans Verkuil
2010-09-09 11:48 ` Hans de Goede
2010-09-13 7:04 ` Laurent Pinchart
2010-09-13 8:06 ` Hans Verkuil
2010-09-13 11:45 ` Mauro Carvalho Chehab
2010-09-13 13:49 ` Andy Walls
2010-09-13 14:38 ` Mauro Carvalho Chehab
2010-09-16 10:09 ` Laurent Pinchart
2010-09-10 13:40 ` Andy Walls
2010-09-09 14:01 Andy Walls
2010-09-09 14:17 ` Hans Verkuil
2010-09-09 19:26 ` Peter Korsgaard
2010-09-10 0:49 ` Andy Walls
2010-09-10 7:19 ` Peter Korsgaard
2010-09-10 13:30 ` Andy Walls
2010-09-09 14:14 Andy Walls
2010-09-09 13:16 ` Hans de Goede
2010-09-09 14:41 Andy Walls
2010-09-09 13:17 ` Hans de Goede
2010-09-09 21:37 ` Andy Walls
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=4C862917.5050903@redhat.com \
--to=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
/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;
as well as URLs for NNTP newsgroup(s).