public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Stefan Wahren <stefan.wahren@i2se.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
	Jacek Anaszewski <j.anaszewski@samsung.com>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org
Subject: Re: [PATCH RFC 2/3] DT: add binding for SN3218 LED driver
Date: Thu, 28 Jan 2016 21:26:36 -0600	[thread overview]
Message-ID: <20160129032636.GA17048@rob-hp-laptop> (raw)
In-Reply-To: <1454013667-25889-3-git-send-email-stefan.wahren@i2se.com>

On Thu, Jan 28, 2016 at 08:41:06PM +0000, Stefan Wahren wrote:
> This patch adds the binding for Si-En Technology SN3218
> 18-Channel LED driver.
> 
> Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
> ---
>  .../devicetree/bindings/leds/leds-sn3218.txt       |   41 ++++++++++++++++++++
>  1 file changed, 41 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/leds/leds-sn3218.txt

One nit, otherwise:

Acked-by: Rob Herring <robh@kernel.org>

> 
> diff --git a/Documentation/devicetree/bindings/leds/leds-sn3218.txt b/Documentation/devicetree/bindings/leds/leds-sn3218.txt
> new file mode 100644
> index 0000000..bf632df
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/leds-sn3218.txt
> @@ -0,0 +1,41 @@
> +* Si-En Technology - SN3218 18-Channel LED Driver
> +
> +Required properties:
> +- compatible :
> +	"si-en,sn3218"
> +- address-cells : must be 1
> +- size-cells : must be 0
> +- reg : I2C slave address, typically 0x54
> +
> +Each led is represented as a sub-node of the si-en,sn3218 device.
> +
> +LED sub-node properties:
> +- label : (optional) see Documentation/devicetree/bindings/leds/common.txt
> +- reg : number of LED line (could be from 0 to 17)
> +- linux,default-trigger : (optional)
> +   see Documentation/devicetree/bindings/leds/common.txt
> +
> +Example:
> +
> +sn3218@54 {
> +	compatible = "si-en,sn3218";
> +	#address-cells = <1>;
> +	#size-cells = <0>;
> +	reg = <0x54>;
> +
> +	led1@0 {

Just led@X please.

> +		label = "led1";
> +		reg = <0x0>;
> +	};
> +
> +	led2@1 {
> +		label = "led2";
> +		reg = <0x1>;
> +	};
> +
> +	led3@2 {
> +		label = "led3";
> +		reg = <0x2>;
> +	};
> +};
> +
> -- 
> 1.7.9.5
> 

  reply	other threads:[~2016-01-29  3:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 20:41 [PATCH RFC 0/3] leds: add SN3218 LED driver Stefan Wahren
2016-01-28 20:41 ` [PATCH RFC 2/3] DT: add binding for " Stefan Wahren
2016-01-29  3:26   ` Rob Herring [this message]
     [not found] ` <1454013667-25889-1-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2016-01-28 20:41   ` [PATCH RFC 1/3] of: Add vendor prefix for Si-En Technology Stefan Wahren
     [not found]     ` <1454013667-25889-2-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2016-01-29  3:27       ` Rob Herring
2016-01-28 20:41   ` [PATCH RFC 3/3] leds: add SN3218 LED driver Stefan Wahren
2016-01-29 12:54     ` 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=20160129032636.GA17048@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=j.anaszewski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rpurdie@rpsys.net \
    --cc=stefan.wahren@i2se.com \
    /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