From: Peter Korsgaard <jacmet@sunsite.dk>
To: Andy Walls <awalls@md.metrocast.net>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Hans de Goede <hdegoede@redhat.com>,
Jean-Francois Moine <moinejf@free.fr>,
"linux-media\@vger.kernel.org" <linux-media@vger.kernel.org>,
eduardo.valentin@nokia.com,
ext Eino-Ville Talvala <talvala@stanford.edu>
Subject: Re: [PATCH] Illuminators and status LED controls
Date: Fri, 10 Sep 2010 09:19:00 +0200 [thread overview]
Message-ID: <87r5h2awwr.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1284079784.4438.192.camel@morgan.silverblock.net> (Andy Walls's message of "Thu, 09 Sep 2010 20:49:44 -0400")
>>>>> "Andy" == Andy Walls <awalls@md.metrocast.net> writes:
Hi,
Andy> Given choices I made when I patched up gspca/cpia1.c for my
Andy> prototype LED API usage, I got these associations
Andy> By exposed LED name:
Andy> /sys/class/leds/video0:white:illuminator0
Indeed. But didn't we just decide that illuminators were an integral
part of the video handling (similar to gain control), and only use the
LED API for status LEDs that don't directly interfere with the video
data?
Andy> The LED API has some shortcomings/annoyances:
Andy> - The method a driver provides to set the LED brightness cannot sleep,
Andy> so a workqueue is needed to simply turn a hardware light on and off for
Andy> USB devices.
Andy> - The Documentation is not very good for end-users or kernel developers
Andy> on using the LED API.
No? I agree that the documentation is pretty minimalistic, but ok - It's
not that complicated.
Andy> - For an LED trigger not to override a user's desire to inhibit an LED,
Andy> the user needs to know to cancel all the triggers on an LED before
Andy> setting the LEDs brightness to 0.
Only a single trigger can be active at a time for a given LED.
Andy> Again, that happens to be the only real compelling use case I see for
Andy> using the LED API. However, I doubt many users will try to take
Andy> advantage of it, and I suspect even less will succeed in getting it
Andy> configured right. Good documentation could go a long way in correcting
Andy> that.
That and using the LED for something else (perhaps with another trigger
like I eplained earlier with wlan/hdd activity).
Andy> If a user configures multiple LED triggers on an LED, those triggers
Andy> will compete with each other. The net result is the most recent event
Andy> from the driver, any LED triggers wins, or user manipulation of sysfs
Andy> brightness.
Only a single trigger can be active at a time for a given LED.
Andy> With indicators that's annoying, but not a failure. With illuminators,
Andy> that is a failure.
Again, I don't think we should use the LED API for something as integral
to the video signal as illuminators.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-09-10 7:19 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 14:01 [PATCH] Illuminators and status LED controls 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 [this message]
2010-09-10 13:30 ` 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-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-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=87r5h2awwr.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=awalls@md.metrocast.net \
--cc=eduardo.valentin@nokia.com \
--cc=hdegoede@redhat.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=moinejf@free.fr \
--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.