From: Pavel Machek <pavel@ucw.cz>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Felipe Balbi <balbi@ti.com>, Bryan Wu <cooloney@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>,
"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: "advanced" LED controllers
Date: Mon, 2 Mar 2015 10:21:11 +0100 [thread overview]
Message-ID: <20150302092111.GA19233@amd> (raw)
In-Reply-To: <CAAVeFuJ7DCs_=iESJRcXwyQ09eD57dZCxGG5CD3LD9_ZGZHP2A@mail.gmail.com>
On Wed 2015-02-25 18:06:07, Alexandre Courbot wrote:
> On Wed, Feb 25, 2015 at 5:25 PM, Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
> > CC linux-gpio, as this looks like the LED equivalent of bulk gpio?
>
> Indeed. The LED core could implement something similar to
> gpiod_set_array() to allow several LEDs to be set in one call. If the
> controller supports it, it would then set all the LEDs at once,
> otherwise the core would apply the values serially.
>
> In leds-gpio.c, this multiple LED setting could be implemented by a
> single call to gpiod_set_array() and the right thing would happen.
Actually, there are two issues: some controlles can set all LEDs at
once, and some can program pwm level smoothly using given program (and
handle multiple leds in the process).
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-03-02 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150219211424.GN13603@saruman.tx.rr.com>
2015-02-25 8:25 ` "advanced" LED controllers Geert Uytterhoeven
2015-02-25 9:06 ` Alexandre Courbot
2015-03-02 9:21 ` Pavel Machek [this message]
2015-03-03 8:15 ` Alexandre Courbot
2015-03-08 20:57 ` RGB LED control (was Re: "advanced" LED controllers) Pavel Machek
2015-03-09 8:08 ` Geert Uytterhoeven
2015-03-09 9:08 ` Pavel Machek
2015-03-09 11:50 ` Måns Rullgård
2015-03-10 8:04 ` Pavel Machek
[not found] ` <CAK5ve-K4jyBSVk1CZ8qQrFgevqdbhdsgZ1ZYX2e-t07494oq4A@mail.gmail.com>
2015-03-11 9:34 ` Documentation: leds: clarify what 50% brightness means Pavel Machek
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=20150302092111.GA19233@amd \
--to=pavel@ucw.cz \
--cc=balbi@ti.com \
--cc=cooloney@gmail.com \
--cc=geert@linux-m68k.org \
--cc=gnurou@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rpurdie@rpsys.net \
/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;
as well as URLs for NNTP newsgroup(s).