From: Jean-Francois Moine <moinejf@free.fr>
To: Hans Verkuil <hverkuil@xs4all.nl>, Hans de Goede <hdegoede@redhat.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] Illuminators and status LED controls
Date: Tue, 7 Sep 2010 19:57:18 +0200 [thread overview]
Message-ID: <20100907195718.066b2986@tele> (raw)
In-Reply-To: <201009071730.33642.hverkuil@xs4all.nl>
On Tue, 7 Sep 2010 17:30:33 +0200
Hans Verkuil <hverkuil@xs4all.nl> wrote:
> enum v4l2_illuminator {
> V4L2_ILLUMINATOR_OFF = 0,
> V4L2_ILLUMINATOR_ON = 1,
> };
> #define V4L2_CID_ILLUMINATOR_0 (V4L2_CID_BASE+37)
> #define V4L2_CID_ILLUMINATOR_1 (V4L2_CID_BASE+38)
>
> enum v4l2_led {
> V4L2_LED_AUTO = 0,
> V4L2_LED_OFF = 1,
> V4L2_LED_ON = 2,
> };
> #define V4L2_CID_LED_0 (V4L2_CID_BASE+39)
>
> Simple and straightforward.
Hi,
Hans (de Goede), is this OK for you? I think that if we find more
illuminators or LEDs on some devices, we may add more V4L2_CID_xxx_n
controls.
Hans (Verkuil), may we have the same enum's for both light types?
Something like:
enum v4l2_light {
V4L2_LIGHT_OFF = 0,
V4L2_LIGHT_ON = 1,
V4L2_LIGHT_AUTO = 2,
V4L2_LIGHT_BLINK = 3,
};
Regards.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2010-09-07 17:57 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
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 [this message]
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=20100907195718.066b2986@tele \
--to=moinejf@free.fr \
--cc=hdegoede@redhat.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.