From: Andy Walls <awalls@md.metrocast.net>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] LED control
Date: Sat, 04 Sep 2010 15:50:25 -0400 [thread overview]
Message-ID: <1283629825.2060.16.camel@morgan.silverblock.net> (raw)
In-Reply-To: <20100904131048.6ca207d1@tele>
On Sat, 2010-09-04 at 13:10 +0200, Jean-Francois Moine wrote:
> Some media devices may have one or many lights (LEDs, illuminators,
> lamps..). This patch makes them controlable by the applications.
>
> Signed-off-by: Jean-Francois Moine <moinejf@free.fr>
Jean-Francois,
Thanks for the proposal. It looks OK to me.
Acked-by: Andy Walls <awalls@md.metrocast.net>
Regards,
Andy
> diff --git a/Documentation/DocBook/v4l/controls.xml b/Documentation/DocBook/v4l/controls.xml
> index 8408caa..c9b8ca5 100644
> --- a/Documentation/DocBook/v4l/controls.xml
> +++ b/Documentation/DocBook/v4l/controls.xml
> @@ -312,6 +312,13 @@ minimum value disables backlight compensation.</entry>
> information and bits 24-31 must be zero.</entry>
> </row>
> <row>
> + <entry><constant>V4L2_CID_LEDS</constant></entry>
> + <entry>integer</entry>
> + <entry>Switch on or off the LED(s) or illuminator(s) of the device.
> + The control type and values depend on the driver and may be either
> + a single boolean (0: off, 1:on) or the index in a menu type.</entry>
> + </row>
> + <row>
> <entry><constant>V4L2_CID_LASTP1</constant></entry>
> <entry></entry>
> <entry>End of the predefined control IDs (currently
> diff --git a/include/linux/videodev2.h b/include/linux/videodev2.h
> index 61490c6..3807492 100644
> --- a/include/linux/videodev2.h
> +++ b/include/linux/videodev2.h
> @@ -1045,8 +1045,10 @@ enum v4l2_colorfx {
>
> #define V4L2_CID_CHROMA_GAIN (V4L2_CID_BASE+36)
>
> +#define V4L2_CID_LEDS (V4L2_CID_BASE+37)
> +
> /* last CID + 1 */
> -#define V4L2_CID_LASTP1 (V4L2_CID_BASE+37)
> +#define V4L2_CID_LASTP1 (V4L2_CID_BASE+38)
>
> /* MPEG-class control IDs defined by V4L2 */
> #define V4L2_CID_MPEG_BASE (V4L2_CTRL_CLASS_MPEG | 0x900)
>
next prev parent reply other threads:[~2010-09-04 19:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 11:10 [PATCH] LED control Jean-Francois Moine
2010-09-04 19:50 ` Andy Walls [this message]
2010-09-05 7:56 ` Hans de Goede
2010-09-05 8:04 ` Peter Korsgaard
2010-09-05 8:19 ` Hans de Goede
2010-09-05 18:23 ` Andy Walls
2010-09-05 8:56 ` Jean-Francois Moine
2010-09-05 13:54 ` Hans de Goede
2010-09-05 18:43 ` Andy Walls
2010-09-05 19:34 ` Hans de Goede
2010-09-13 6:43 ` Laurent Pinchart
-- strict thread matches above, loose matches on Subject: below --
2009-03-14 11:59 Jean-Francois Moine
2009-03-14 12:17 ` Mauro Carvalho Chehab
2009-03-14 13:25 ` Jean-Francois Moine
2009-03-14 13:58 ` Andy Walls
2009-03-14 20:16 ` Trent Piepho
2009-03-15 9:50 ` Jean-Francois Moine
2009-03-15 10:16 ` Laurent Pinchart
2009-03-15 15:14 ` Trent Piepho
2009-03-17 8:28 ` Jean-Francois Moine
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=1283629825.2060.16.camel@morgan.silverblock.net \
--to=awalls@md.metrocast.net \
--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