All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: "linux-media\@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: Peter Korsgaard <jacmet@sunsite.dk>,
	Andy Walls <awalls@md.metrocast.net>,
	eduardo.valentin@nokia.com,
	ext Eino-Ville Talvala <talvala@stanford.edu>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH] Illuminators and status LED controls
Date: Thu, 9 Sep 2010 08:07:02 +0200	[thread overview]
Message-ID: <20100909080702.1687d29a@tele> (raw)
In-Reply-To: <87fwxkcbat.fsf@macbook.be.48ers.dk>

On Wed, 08 Sep 2010 20:58:18 +0200
Peter Korsgaard <jacmet@sunsite.dk> wrote:
> >>>>> "Andy" == Andy Walls <awalls@md.metrocast.net> writes:
>  Andy> Incandescent and Halogen lamps that effect an image coming
>  Andy> into a camera are *not* LEDs that blink or flash automatically
>  Andy> based on driver or system trigger events.  They are components
>  Andy> of a video capture system with which a human attempts to
>  Andy> adjust the appearance of an image of a subject by changing the
>  Andy> subject's environment.  These illuminators are not some
>  Andy> generically connected device, but controlled by GPIO's on the
>  Andy> camera's bridge or sensor chip itself.  Such an illuminator
>  Andy> will essentially be used only in conjunction with the camera.
> 
> Agreed.
> 
>  Andy> Status LEDs integrated into webcam devices that are not
>  Andy> generically connected devices but controlled with GPIOs on the
>  Andy> camera's bridge or sensor chip will also essentially be used
>  Andy> only in conjunction with the camera.
> 
> Or for any other usage the user envision - E.G. I could imagine using
> the status led of the webcam in my macbook for hard disk or wifi
> activity. I'm sure other people can come up with more creative use
> cases as well.
> 
>  Andy> Turning these sorts camera specific illuminators and LEDs on
>  Andy> an off should be as simple to implement for an application
>  Andy> developer as it is to grasp the concept of turning a light
>  Andy> bulb on and off.
> 
> The point is that the logic rarely needs to be in the v4l
> applications. The status LEDs should by default go on when the v4l
> device is active and go off again when not like it used to do. A v4l
> application developer would normally not want to worry about such
> things, and only care about the video data.
> 
> But if a user wants something special / non-standard, then it's just a
> matter of changing LED trigger in /sys/class/leds/..
	[snip]
> Again, for status LEDs I don't see any reason why a standard v4l tool
> would care. As I mentioned above, illuminators are a different story
> (comparable to a gain setting imho).
	[snip]
> Again, I see the sysfs LED interface for status LEDs as more of a
> user/administrator interface than a programming API.

Hi,

If I may resume this exchange:

- the (microscope or device dependant) illuminators may be controlled
  by v4l2,

- the status LED should be controlled by the LED interface.

Does everybody agree?

Regards.

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

  parent reply	other threads:[~2010-09-09  6:06 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 20:33 [PATCH] Illuminators and status LED controls 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-09-09 14:41 Andy Walls
2010-09-09 13:17 ` Hans de Goede
2010-09-09 21:37   ` Andy Walls
2010-09-09 14:14 Andy Walls
2010-09-09 13:16 ` Hans de Goede
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-07 16:35 Andy Walls
2010-09-06 18:11 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
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

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=20100909080702.1687d29a@tele \
    --to=moinejf@free.fr \
    --cc=awalls@md.metrocast.net \
    --cc=eduardo.valentin@nokia.com \
    --cc=hdegoede@redhat.com \
    --cc=jacmet@sunsite.dk \
    --cc=linux-media@vger.kernel.org \
    --cc=talvala@stanford.edu \
    /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.