From: Marek Behun <kabel@blackhole.sk>
To: linux-leds@vger.kernel.org
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>
Subject: turris omnia leds again: question
Date: Tue, 10 Mar 2020 18:38:24 +0100 [thread overview]
Message-ID: <20200310183824.1e4ad91d@blackhole.sk> (raw)
Hi,
I am going to try to send driver for Omnia LEDs again. The last time
there was a problem: on 05/01/2019 Jacek wrote:
> I wonder if we're doing right merging this driver in this form.
> We break the rule one-led-class-device-per-one-channel. We don't
> have LED multi color support yet, so this should support RGB LEDs
> in the old manner. Or switch to using LED multi color class.
> Once we will have LED multi color class, we will be able to add the
> support for it to the driver and make the driver configurable to be
> able to expose old interface or the LED multi color one.
> Moreover, the bindings should use led-sources property for grouping
> three channels under single LED class device. This is certainly to be
> fixed.
So I am going to try to modify the driver so that each channel creates
one LED class device. Do I understand this correctly then, that this
way when there are three channels (RGB) on one LED, all the 3 device
tree nodes for should have the same reg property, but different
led-sources property? Eg:
led@0,0 {
reg = <0>;
led-sources = <0>;
label = "omnia::heartbeat::red";
};
led@0,1 {
reg = <0>;
led-sources = <1>;
label = "omnia::heartbeat::green";
};
led@0,2 {
reg = <0>;
led-sources = <2>;
label = "omnia::heartbeat::blue";
};
Or did I misinterpret the led-sources property?
Thanks, Marek.
next reply other threads:[~2020-03-10 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 17:38 Marek Behun [this message]
2020-03-10 21:48 ` turris omnia leds again: question Jacek Anaszewski
2020-03-10 22:23 ` Marek Behun
2020-03-11 10:59 ` Jacek Anaszewski
2020-03-19 4:34 ` Marek Behun
2020-03-19 15:27 ` Marek Behun
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=20200310183824.1e4ad91d@blackhole.sk \
--to=kabel@blackhole.sk \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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