From: Dan Murphy <dmurphy@ti.com>
To: <robh+dt@kernel.org>, <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>
Cc: <linux-kernel@vger.kernel.org>, <linux-leds@vger.kernel.org>,
Dan Murphy <dmurphy@ti.com>
Subject: [PATCH 1/5] dt-bindings: mfd: Update the ramp up/down property
Date: Mon, 25 Mar 2019 09:23:59 -0500 [thread overview]
Message-ID: <20190325142403.30447-2-dmurphy@ti.com> (raw)
In-Reply-To: <20190325142403.30447-1-dmurphy@ti.com>
Modify the ramp-up/down property and add the property description
to the binding.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
---
.../devicetree/bindings/mfd/ti-lmu.txt | 20 ++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
diff --git a/Documentation/devicetree/bindings/mfd/ti-lmu.txt b/Documentation/devicetree/bindings/mfd/ti-lmu.txt
index 980394d701a7..d9d529de6dc1 100644
--- a/Documentation/devicetree/bindings/mfd/ti-lmu.txt
+++ b/Documentation/devicetree/bindings/mfd/ti-lmu.txt
@@ -25,6 +25,12 @@ Required properties:
Optional property:
- enable-gpios: A GPIO specifier for hardware enable pin.
+ - ramp-up-ms: Current ramping from one brightness level to
+ the a higher brightness level.
+ Range from 2048 us - 117.44 s
+ - ramp-down-ms: Current ramping from one brightness level to
+ the a lower brightness level.
+ Range from 2048 us - 117.44 s
Required node:
- backlight: All LMU devices have backlight child nodes.
@@ -90,7 +96,7 @@ lm3631@29 {
lcd_bl {
led-sources = <0 1>;
- ramp-up-msec = <300>;
+ ramp-up-ms = <300>;
};
};
};
@@ -152,15 +158,15 @@ lm3633@36 {
main {
label = "main_lcd";
led-sources = <1 2>;
- ramp-up-msec = <500>;
- ramp-down-msec = <500>;
+ ramp-up-ms = <500>;
+ ramp-down-ms = <500>;
};
front {
label = "front_lcd";
led-sources = <0>;
- ramp-up-msec = <1000>;
- ramp-down-msec = <0>;
+ ramp-up-ms = <1000>;
+ ramp-down-ms = <0>;
};
};
@@ -212,8 +218,8 @@ lm3697@36 {
lcd {
led-sources = <0 1 2>;
- ramp-up-msec = <200>;
- ramp-down-msec = <200>;
+ ramp-up-ms = <200>;
+ ramp-down-ms = <200>;
};
};
--
2.19.0
next prev parent reply other threads:[~2019-03-25 14:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 14:23 [PATCH 0/5] TI LMU rework Dan Murphy
2019-03-25 14:23 ` Dan Murphy [this message]
2019-04-04 8:19 ` [PATCH 1/5] dt-bindings: mfd: Update the ramp up/down property Lee Jones
2019-04-04 12:07 ` Dan Murphy
2019-03-25 14:24 ` [PATCH 2/5] leds: TI LMU: Add common code for TI LMU devices Dan Murphy
2019-04-04 13:22 ` Pavel Machek
2019-03-25 14:24 ` [PATCH 3/5] dt-bindings: ti-lmu: Modify dt bindings for the LM3697 Dan Murphy
2019-04-03 20:10 ` Jacek Anaszewski
2019-04-03 20:23 ` Dan Murphy
2019-04-04 18:39 ` Jacek Anaszewski
2019-04-04 19:27 ` Dan Murphy
2019-04-04 19:31 ` Jacek Anaszewski
2019-04-04 19:34 ` Dan Murphy
2019-03-25 14:24 ` [PATCH 4/5] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2019-04-04 8:17 ` Lee Jones
2019-04-04 8:18 ` Lee Jones
2019-04-04 12:09 ` Dan Murphy
2019-03-25 14:24 ` [PATCH 5/5] leds: lm3697: Introduce the lm3697 driver Dan Murphy
2019-04-13 20:06 ` Pavel Machek
2019-04-15 12:49 ` Dan Murphy
2019-04-15 14:03 ` Pavel Machek
2019-04-15 19:53 ` Dan Murphy
2019-04-03 12:02 ` [PATCH 0/5] TI LMU rework Dan Murphy
2019-04-03 20:14 ` Jacek Anaszewski
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=20190325142403.30447-2-dmurphy@ti.com \
--to=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.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).