From: Jean-Francois Moine <moinejf@free.fr>
To: Trent Piepho <xyzzy@speakeasy.org>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH] LED control
Date: Sun, 15 Mar 2009 10:50:37 +0100 [thread overview]
Message-ID: <20090315105037.6266687a@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.58.0903141315300.28292@shell2.speakeasy.net>
On Sat, 14 Mar 2009 13:16:11 -0700 (PDT)
Trent Piepho <xyzzy@speakeasy.org> wrote:
> There is already a sysfs led interface, you could just have the driver
> export the leds to the led subsystem and use that.
Yes, but:
- this asks to have a kernel generated with CONFIG_NEW_LEDS,
- the user must use some new program to access /sys/class/leds/<device>,
- he must know how the LEDs of his webcam are named in the /sys tree.
While, when the LEDs are handled by a simple control, the user may
quickly change all webcam parameters from a single program as v4l2-ctl.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2009-03-15 9:55 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
2009-03-14 13:58 ` Andy Walls
2009-03-14 20:16 ` Trent Piepho
2009-03-15 9:50 ` Jean-Francois Moine [this message]
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=20090315105037.6266687a@free.fr \
--to=moinejf@free.fr \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=xyzzy@speakeasy.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