public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH] LED control
Date: Sat, 14 Mar 2009 14:25:13 +0100	[thread overview]
Message-ID: <20090314142513.315c52b0@free.fr> (raw)
In-Reply-To: <20090314091747.21153855@pedra.chehab.org>

On Sat, 14 Mar 2009 09:17:47 -0300
Mauro Carvalho Chehab <mchehab@infradead.org> wrote:

> On Sat, 14 Mar 2009 12:59:23 +0100
> Jean-Francois Moine <moinejf@free.fr> wrote:
> 
> > +	    <entry><constant>V4L2_CID_LEDS</constant></entry>
> > +	    <entry>integer</entry>
> > +	    <entry>Switch on or off the LEDs or illuminators of
> > the device. +In the control value, each LED may be coded in one bit
> > (0: off, 1: on) or in +many bits (light intensity).</entry>
> > +	  </row>
> > +	  <row>
> 
> The idea of having some sort of control over the LEDs is interesting,
> but we should have a better way of controlling it. If the LED may
> have more than one bit, maybe the better would be to create more than
> one CID entry. Something like:
> 
> V4L2_CID_LED_POWER	- for showing that the camera is being used
> V4L2_CID_LED_LIGHT	- for normal white light
> V4L2_CID_LED_INFRARED	- for dark light, using infrared
> ...
> 
> This way a driver can enumberate what kind of leds are available, and
> get the power intensity range for each individual one.

OK for V4L2_CID_LED_INFRARED: I already know a webcam type which needs
such a control, but I don't know if it is associated to a LED or to a
sensor capability.

I heard of some webcams with many LEDs (up to 6) and some of these last
ones may be independently switched on or off. But, actually, I don't
heard about individual or global LED power.

So, as I understand your controls, V4L2_CID_LED_LIGHT would contain a
bit array, one bit for each LED, and V4L2_CID_LED_POWER would give the
light intensity for all LEDs. This last control might be added later if
needed.

Am I right?

Cheers.

-- 
Ken ar c'hentañ	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/

  reply	other threads:[~2009-03-14 13:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-14 11:59 [PATCH] LED control Jean-Francois Moine
2009-03-14 12:17 ` Mauro Carvalho Chehab
2009-03-14 13:25   ` Jean-Francois Moine [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-09-04 11:10 Jean-Francois Moine
2010-09-04 19:50 ` Andy Walls
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

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=20090314142513.315c52b0@free.fr \
    --to=moinejf@free.fr \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox