From: Linus Walleij <linus.walleij@stericsson.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Milo Kim <Milo.Kim@ti.com>,
devicetree-discuss@lists.ozlabs.org,
Bryan Wu <cooloney@gmail.com>,
Gabriel Fernandez <gabriel.fernandez.st@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH] ARM: ux500: register LP5521 LEDs in the device tree
Date: Wed, 22 May 2013 10:12:11 +0200 [thread overview]
Message-ID: <1369210331-18545-1-git-send-email-linus.walleij@stericsson.com> (raw)
From: Linus Walleij <linus.walleij@linaro.org>
Based on pending device tree support in the LP55xx drivers
we can add the correct LED and channel configuration from the
ux500 device tree for all HREF variants.
Cc: Milo Kim <Milo.Kim@ti.com>
Cc: Bryan Wu <cooloney@gmail.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
arch/arm/boot/dts/href.dtsi | 38 ++++++++++++++++++++++++++++++++------
1 file changed, 32 insertions(+), 6 deletions(-)
diff --git a/arch/arm/boot/dts/href.dtsi b/arch/arm/boot/dts/href.dtsi
index 62523f6..e315429 100644
--- a/arch/arm/boot/dts/href.dtsi
+++ b/arch/arm/boot/dts/href.dtsi
@@ -63,16 +63,42 @@
};
i2c@80128000 {
- lp5521@0x33 {
- compatible = "lp5521";
+ lp5521@33 {
+ compatible = "national,lp5521";
reg = <0x33>;
+ label = "lp5521_pri";
+ clock-mode = /bits/ 8 <2>;
+ chan0 {
+ led-cur = /bits/ 8 <0x2f>;
+ max-cur = /bits/ 8 <0x5f>;
+ };
+ chan1 {
+ led-cur = /bits/ 8 <0x2f>;
+ max-cur = /bits/ 8 <0x5f>;
+ };
+ chan2 {
+ led-cur = /bits/ 8 <0x2f>;
+ max-cur = /bits/ 8 <0x5f>;
+ };
};
-
- lp5521@0x34 {
- compatible = "lp5521";
+ lp5521@34 {
+ compatible = "national,lp5521";
reg = <0x34>;
+ label = "lp5521_sec";
+ clock-mode = /bits/ 8 <2>;
+ chan0 {
+ led-cur = /bits/ 8 <0x2f>;
+ max-cur = /bits/ 8 <0x5f>;
+ };
+ chan1 {
+ led-cur = /bits/ 8 <0x2f>;
+ max-cur = /bits/ 8 <0x5f>;
+ };
+ chan2 {
+ led-cur = /bits/ 8 <0x2f>;
+ max-cur = /bits/ 8 <0x5f>;
+ };
};
-
bh1780@0x29 {
compatible = "rohm,bh1780gli";
reg = <0x33>;
--
1.7.11.3
next reply other threads:[~2013-05-22 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 8:12 Linus Walleij [this message]
2013-05-22 23:14 ` [PATCH] ARM: ux500: register LP5521 LEDs in the device tree Kim, Milo
[not found] ` <1369210331-18545-1-git-send-email-linus.walleij-0IS4wlFg1OjSUeElwK9/Pw@public.gmane.org>
2013-05-31 17:37 ` Bryan Wu
[not found] ` <CAK5ve-+oJL0fbtM=5xRSBjCztX1fP-fcwUvZurnj42hiXR5X+Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-03 8:18 ` Lee Jones
[not found] ` <20130603081805.GC3370-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-03 17:29 ` Bryan Wu
[not found] ` <CAK5ve-+ykvTfpfsyAfnoURwuZt1nF4aFPGU5yQa0HXXBmWW_9Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-04 7:35 ` Lee Jones
[not found] ` <20130604073507.GL3370-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-06-04 17:33 ` Bryan Wu
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=1369210331-18545-1-git-send-email-linus.walleij@stericsson.com \
--to=linus.walleij@stericsson.com \
--cc=Milo.Kim@ti.com \
--cc=cooloney@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=gabriel.fernandez.st@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).