From: Grant Likely <grant.likely@secretlab.ca>
To: cooloney@gmail.com, rpurdie@rpsys.net
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
Marek Belisko <marek.belisko@open-nandra.com>
Subject: Re: [PATCH v3 2/2] Add documentation for tca6507 devicetree bindings.
Date: Thu, 15 Nov 2012 18:12:34 +0000 [thread overview]
Message-ID: <20121115181234.37B173E199F@localhost> (raw)
In-Reply-To: <1352755511-28436-2-git-send-email-marek.belisko@open-nandra.com>
On Mon, 12 Nov 2012 22:25:11 +0100, Marek Belisko <marek.belisko@open-nandra.com> wrote:
> Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com>
> ---
> Documentation/devicetree/bindings/leds/tca6507.txt | 40 ++++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/tca6507.txt
>
> diff --git a/Documentation/devicetree/bindings/leds/tca6507.txt b/Documentation/devicetree/bindings/leds/tca6507.txt
> new file mode 100644
> index 0000000..a49eb0c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/tca6507.txt
> @@ -0,0 +1,40 @@
> +LEDs conected to tca6507
> +
> +Required properties:
> +- compatible : should be : "ti,tca6507".
> +
> +Each led is represented as a sub-node of the ti,tca6507 device.
> +
> +LED sub-node properties:
> +- label : label for this LED
> +- reg : number of LED line (could be from 0 to 6)
> +- linux,default-trigger : (optional) This parameter, if present, is a
> + string defining the trigger assigned to the LED. Current triggers are:
> + "backlight" - LED will act as a back-light, controlled by the framebuffer
> + system
> + "default-on" - LED will turn on
> + "heartbeat" - LED "double" flashes at a load average based rate
> + "ide-disk" - LED indicates disk activity
> + "timer" - LED flashes at a fixed, configurable rate
This is cut-and-paste from bindings/gpio/led.txt. It should be split
into a separate file and referenced by both bindings. Otherwise the
binding looks fine.
> +
> +Examples:
> +
> +tca6507@45 {
> + compatible = "ti,tca6507";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <0x45>;
> +
> + led0: red_aux@0 {
> + label = "red:aux";
> + reg = <0x0>;
> + };
> +
> + led1: green_aux@1 {
Don't use underscores in node names. Use '-'. (There isn't a technical
reason for this. It is just convention)
g.
next prev parent reply other threads:[~2012-11-15 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 21:25 [PATCH v3 1/2] leds/tca6507: Add support for devicetree Marek Belisko
2012-11-12 21:25 ` [PATCH v3 2/2] Add documentation for tca6507 devicetree bindings Marek Belisko
2012-11-14 1:05 ` Bryan Wu
2012-11-14 19:26 ` Stephen Warren
[not found] ` <50A3F06F.20809-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-11-14 22:50 ` Bryan Wu
2012-11-15 18:12 ` Grant Likely [this message]
2012-11-14 1:01 ` [PATCH v3 1/2] leds/tca6507: Add support for devicetree 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=20121115181234.37B173E199F@localhost \
--to=grant.likely@secretlab.ca \
--cc=cooloney@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marek.belisko@open-nandra.com \
--cc=rpurdie@rpsys.net \
/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).