From: "Andrew F. Davis" <afd@ti.com>
To: Dan Murphy <dmurphy@ti.com>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <jacek.anaszewski@gmail.com>,
<pavel@ucw.cz>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-leds@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] dt: bindings: lm3601x: Introduce the lm3601x driver
Date: Tue, 8 May 2018 10:32:59 -0500 [thread overview]
Message-ID: <554b283f-7c27-e2de-3052-e5119dba9396@ti.com> (raw)
In-Reply-To: <20180508141704.24271-1-dmurphy@ti.com>
On 05/08/2018 09:17 AM, Dan Murphy wrote:
> Introduce the device tree bindings for the lm3601x
> family of LED torch, flash and IR drivers.
>
> Signed-off-by: Dan Murphy <dmurphy@ti.com>
> ---
>
> v2 - No changes - https://patchwork.kernel.org/patch/10384587/
>
> .../devicetree/bindings/leds/leds-lm3601x.txt | 51 +++++++++++++++++++
> 1 file changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3601x.txt
>
> diff --git a/Documentation/devicetree/bindings/leds/leds-lm3601x.txt b/Documentation/devicetree/bindings/leds/leds-lm3601x.txt
> new file mode 100644
> index 000000000000..38cdabf6ca7e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/leds-lm3601x.txt
> @@ -0,0 +1,51 @@
> +* Texas Instruments - lm3601x Single-LED Flash Driver
> +
> +The LM3601X are ultra-small LED flash drivers that
> +provides a high level of adjustability.
> +
> +Required properties:
> + - compatible : Can be one of the following
> + "ti,lm3601x"
No wildcard compatibles, drop this.
> + "ti,lm36010"
> + "ti,lm36011"
> + - reg : I2C slave address
> + - #address-cells : 1
> + - #size-cells : 0
> +
> +Required child properties:
> + - reg : 0 - Indicates to support and register a torch interface
> + 1 - Indicates to support and register a strobe interface
> + 2 - Indicates to support and register an ir interface
> +
> +Optional child properties:
> + - label : see Documentation/devicetree/bindings/leds/common.txt
> +
Relative path might work better here.
> +Example:
> +led-controller@64 {
> + compatible = "ti,lm3601x";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0x64>;
> +
> + led@0 {
> + reg = <0>;
> + label = "white:torch";
> + led-max-microamp=<10000>;
> + };
> +
> + led@1 {
> + reg = <1>;
> + label = "white:strobe";
> + flash-max-microamp=<10000>;
> + flash-max-timeout-us=<800>;
> + };
> +
> + led@2 {
> + reg = <2>;
> + label = "invisible:ir";
> + };
> +}
> +
> +For more product information please see the links below:
> +http://www.ti.com/product/LM36010
> +http://www.ti.com/product/LM36011
>
next prev parent reply other threads:[~2018-05-08 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 14:17 [PATCH v2 1/2] dt: bindings: lm3601x: Introduce the lm3601x driver Dan Murphy
2018-05-08 14:17 ` [PATCH v2 2/2] leds: lm3601x: Introduce the lm3601x LED driver Dan Murphy
2018-05-08 15:49 ` Andrew F. Davis
2018-05-08 16:09 ` Dan Murphy
2018-05-08 15:32 ` Andrew F. Davis [this message]
2018-05-08 16:10 ` [PATCH v2 1/2] dt: bindings: lm3601x: Introduce the lm3601x driver Dan Murphy
2018-05-10 11:28 ` Pavel Machek
2018-05-10 12:04 ` Dan Murphy
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=554b283f-7c27-e2de-3052-e5119dba9396@ti.com \
--to=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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