From: Pavel Machek <pavel@ucw.cz>
To: Dan Murphy <dmurphy@ti.com>
Cc: jacek.anaszewski@gmail.com, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v3 2/7] dt-bindings: mfd: LMU: Add the ramp up/down property
Date: Wed, 1 May 2019 00:01:41 +0200 [thread overview]
Message-ID: <20190430220140.GB20410@amd> (raw)
In-Reply-To: <20190430191730.19450-3-dmurphy@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
On Tue 2019-04-30 14:17:25, Dan Murphy wrote:
> Document the ramp-up and ramp-down property in the binding.
> Removing the "sec" from the property definition as seconds is
> implied.
>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
>
> v3 - No changes added Reviewed-by Rob - https://lore.kernel.org/patchwork/patch/1058759/
>
> v2 - Fixed commit message as this was not just a modification but adding documentation
> https://lore.kernel.org/patchwork/patch/1054504/
>
> .../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 86ca786d54fc..adae96c79d39 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:
"properties".
> - 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
Can you use ramp-up/down-us for consistency?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-04-30 22:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 19:17 [PATCH v3 0/7] LMU Common code intro Dan Murphy
2019-04-30 19:17 ` Dan Murphy
2019-04-30 19:17 ` [PATCH v3 1/7] dt-bindings: mfd: LMU: Fix lm3632 dt binding example Dan Murphy
2019-04-30 19:17 ` Dan Murphy
2019-04-30 19:17 ` [PATCH v3 2/7] dt-bindings: mfd: LMU: Add the ramp up/down property Dan Murphy
2019-04-30 19:17 ` Dan Murphy
2019-04-30 22:01 ` Pavel Machek [this message]
2019-05-06 17:53 ` Dan Murphy
2019-05-06 17:53 ` Dan Murphy
2019-04-30 19:17 ` [PATCH v3 3/7] dt-bindings: mfd: LMU: Add ti,brightness-resolution Dan Murphy
2019-04-30 19:17 ` Dan Murphy
2019-04-30 19:17 ` [PATCH v3 4/7] leds: TI LMU: Add common code for TI LMU devices Dan Murphy
2019-04-30 19:17 ` Dan Murphy
2019-04-30 19:23 ` Randy Dunlap
2019-04-30 19:30 ` Dan Murphy
2019-04-30 19:30 ` Dan Murphy
2019-04-30 19:32 ` Jacek Anaszewski
2019-04-30 19:34 ` Dan Murphy
2019-04-30 19:34 ` Dan Murphy
2019-04-30 19:17 ` [PATCH v3 5/7] dt-bindings: ti-lmu: Modify dt bindings for the LM3697 Dan Murphy
2019-04-30 19:17 ` Dan Murphy
2019-04-30 22:05 ` Pavel Machek
2019-04-30 22:07 ` Dan Murphy
2019-04-30 22:07 ` Dan Murphy
2019-04-30 22:08 ` Pavel Machek
2019-04-30 19:17 ` [PATCH v3 6/7] mfd: ti-lmu: Remove support for LM3697 Dan Murphy
2019-04-30 19:17 ` Dan Murphy
2019-04-30 19:17 ` [PATCH v3 7/7] leds: lm3697: Introduce the lm3697 driver Dan Murphy
2019-04-30 19:17 ` Dan Murphy
2019-04-30 22:05 ` [PATCH v3 0/7] LMU Common code intro Jacek Anaszewski
2019-04-30 22:05 ` Jacek Anaszewski
2019-05-01 9:45 ` Jacek Anaszewski
2019-05-08 6:21 ` Lee Jones
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=20190430220140.GB20410@amd \
--to=pavel@ucw.cz \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.