All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] LED control
Date: Sun, 05 Sep 2010 09:56:54 +0200	[thread overview]
Message-ID: <4C834D46.5030801@redhat.com> (raw)
In-Reply-To: <20100904131048.6ca207d1@tele>

Hi all,

On 09/04/2010 01:10 PM, 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>
>
> -- Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/
>
>
> led.patch
>
>
> 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>

I think that using one control for both status leds (which is what we are usually
talking about) and illuminator(s) is a bad idea. I'm fine with standardizing these,
but can we please have 2 CID's one for status lights and one for the led. Esp, as I
can easily see us supporting a microscope in the future where the microscope itself
or other devices with the same bridge will have a status led, so then we will need
2 separate controls anyways.

Regards,

Hans

  parent reply	other threads:[~2010-09-05  7: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
2010-09-05  7:56 ` Hans de Goede [this message]
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=4C834D46.5030801@redhat.com \
    --to=hdegoede@redhat.com \
    --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 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.