linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: linux-leds@vger.kernel.org, cooloney@gmail.com, jogo@openwrt.org,
	f.fainelli@gmail.com, cernekee@gmail.com
Cc: "Álvaro Fernández Rojas" <noltari@gmail.com>
Subject: [PATCH 1/2] leds: add DT binding for BCM6328 LED controller
Date: Thu,  2 Apr 2015 13:54:20 +0200	[thread overview]
Message-ID: <1427975661-29964-2-git-send-email-noltari@gmail.com> (raw)
In-Reply-To: <1427975661-29964-1-git-send-email-noltari@gmail.com>

This adds device tree binding documentation for the Broadcom BCM6328 LED
controller.

Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
Signed-off-by: Jonas Gorski <jogo@openwrt.org>
---
 .../devicetree/bindings/leds/leds-bcm6328.txt      | 173 +++++++++++++++++++++
 1 file changed, 173 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/leds/leds-bcm6328.txt

diff --git a/Documentation/devicetree/bindings/leds/leds-bcm6328.txt b/Documentation/devicetree/bindings/leds/leds-bcm6328.txt
new file mode 100644
index 0000000..e63d27f
--- /dev/null
+++ b/Documentation/devicetree/bindings/leds/leds-bcm6328.txt
@@ -0,0 +1,173 @@
+LEDs connected to Broadcom BCM6328 controller
+
+Required properties:
+- compatible : should be : "brcm,bcm6328-leds".
+- #address-cells: must be 1
+- #size-cells: must be 0
+- reg: BCM6328 LED controller address and size.
+
+Optional properties:
+- brcm,serial-leds: enable Serial LEDs.
+
+Each led is represented as a sub-node of the brcm,bcm6328-leds device.
+
+LED sub-node properties:
+- reg : LED pin number (could be from 0 to 23).
+- compatible : should be : "brcm,bcm6328-led".
+
+Normal LED:
+- label (optional) : see Documentation/devicetree/bindings/leds/common.txt
+- active-low (optional) : LED is active low.
+- default-state (optional): see
+  Documentation/devicetree/bindings/leds/leds-gpio.txt
+- linux,default-trigger (optional): see
+  Documentation/devicetree/bindings/leds/common.txt
+
+Hardware controlled LED:
+- brcm,hardware-controlled (optional) : LED is hardware controlled.
+- brcm,link-selection (optional) : LED link selection values.
+- brcm,activity-selection (optional) : LED activity selection values.
+
+example 1) BCM6328
+
+leds0: led-controller@10000800 {
+	compatible = "brcm,bcm6328-leds";
+	#address-cells = <1>;
+	#size-cells = <0>;
+	reg = <0x10000800 0x24>;
+
+	alarm_red@2 {
+		compatible = "brcm,bcm6328-led";
+		reg = <2>;
+		active-low;
+		label = "red:alarm";
+	};
+	inet_green@3 {
+		compatible = "brcm,bcm6328-led";
+		reg = <3>;
+		active-low;
+		label = "green:inet";
+	};
+	power_green@4 {
+		compatible = "brcm,bcm6328-led";
+		reg = <4>;
+		active-low;
+		label = "green:power";
+		default-state = "on";
+	};
+	ephy0_spd@17 {
+		compatible = "brcm,bcm6328-led";
+		reg = <17>;
+		brcm,hardware-controlled;
+	};
+	ephy1_spd@18 {
+		compatible = "brcm,bcm6328-led";
+		reg = <18>;
+		brcm,hardware-controlled;
+	};
+	ephy2_spd@19 {
+		compatible = "brcm,bcm6328-led";
+		reg = <19>;
+		brcm,hardware-controlled;
+	};
+	ephy3_spd@20 {
+		compatible = "brcm,bcm6328-led";
+		reg = <20>;
+		brcm,hardware-controlled;
+	};
+};
+
+example 2) BCM63268
+
+leds0: led-controller@10001900 {
+	compatible = "brcm,bcm6328-leds";
+	#address-cells = <1>;
+	#size-cells = <0>;
+	reg = <0x10001900 0x24>;
+	brcm,serial-leds;
+
+	gphy0_spd0@0 {
+		compatible = "brcm,bcm6328-led";
+		reg = <0>;
+		brcm,hardware-controlled;
+		brcm,link-selection = <0>;
+	};
+	gphy0_spd1@1 {
+		compatible = "brcm,bcm6328-led";
+		reg = <1>;
+		brcm,hardware-controlled;
+		brcm,link-selection = <1>;
+	};
+	inet_red@2 {
+		compatible = "brcm,bcm6328-led";
+		reg = <2>;
+		active-low;
+		label = "red:inet";
+	};
+	dsl_green@3 {
+		compatible = "brcm,bcm6328-led";
+		reg = <3>;
+		active-low;
+		label = "green:dsl";
+	};
+	usb_green@4 {
+		compatible = "brcm,bcm6328-led";
+		reg = <4>;
+		active-low;
+		label = "green:usb";
+	};
+	wps_green@7 {
+		compatible = "brcm,bcm6328-led";
+		reg = <7>;
+		active-low;
+		label = "green:wps";
+	};
+	inet_green@8 {
+		compatible = "brcm,bcm6328-led";
+		reg = <8>;
+		active-low;
+		label = "green:inet";
+	};
+	ephy0_act@9 {
+		compatible = "brcm,bcm6328-led";
+		reg = <9>;
+		brcm,hardware-controlled;
+	};
+	ephy1_act@10 {
+		compatible = "brcm,bcm6328-led";
+		reg = <10>;
+		brcm,hardware-controlled;
+	};
+	ephy2_act@11 {
+		compatible = "brcm,bcm6328-led";
+		reg = <11>;
+		brcm,hardware-controlled;
+	};
+	gphy0_act@12 {
+		compatible = "brcm,bcm6328-led";
+		reg = <12>;
+		brcm,hardware-controlled;
+	};
+	ephy0_spd@13 {
+		compatible = "brcm,bcm6328-led";
+		reg = <13>;
+		brcm,hardware-controlled;
+	};
+	ephy1_spd@14 {
+		compatible = "brcm,bcm6328-led";
+		reg = <14>;
+		brcm,hardware-controlled;
+	};
+	ephy2_spd@15 {
+		compatible = "brcm,bcm6328-led";
+		reg = <15>;
+		brcm,hardware-controlled;
+	};
+	power_green@20 {
+		compatible = "brcm,bcm6328-led";
+		reg = <20>;
+		active-low;
+		label = "green:power";
+		default-state = "on";
+	};
+};
-- 
1.9.1

  reply	other threads:[~2015-04-02 11:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-02 11:54 [PATCH 0/2] BCM6328 LED driver Álvaro Fernández Rojas
2015-04-02 11:54 ` Álvaro Fernández Rojas [this message]
2015-04-03  2:06   ` [PATCH 1/2] leds: add DT binding for BCM6328 LED controller Florian Fainelli
2015-04-03 12:19     ` Álvaro Fernández Rojas
2015-04-03 14:46       ` Jonas Gorski
2015-04-02 11:54 ` [PATCH 2/2] leds: add BCM6328 LED driver Álvaro Fernández Rojas
2015-04-05 15:08 ` [PATCH v2 0/2] " Álvaro Fernández Rojas
2015-04-05 15:08   ` [PATCH v2 1/2] leds: add DT binding for BCM6328 LED controller Álvaro Fernández Rojas
2015-04-16 14:39     ` Jacek Anaszewski
2015-04-05 15:08   ` [PATCH 2/2] leds: add BCM6328 LED driver Álvaro Fernández Rojas
2015-04-16 14:37     ` Jacek Anaszewski
2015-04-18  9:14       ` Jonas Gorski
2015-04-20  7:12         ` Jacek Anaszewski
2015-04-24 17:06   ` [PATCH v3 0/2] " Álvaro Fernández Rojas
2015-04-24 17:06     ` [PATCH v3 1/2] leds: add DT binding for BCM6328 LED controller Álvaro Fernández Rojas
2015-04-26 11:09       ` Jacek Anaszewski
2015-04-24 17:06     ` [PATCH v3 2/2] leds: add BCM6328 LED driver Álvaro Fernández Rojas
2015-04-26 12:15     ` [PATCH v4 0/2] " Álvaro Fernández Rojas
2015-04-26 12:15       ` [PATCH v4 1/2] leds: add DT binding for BCM6328 LED controller Álvaro Fernández Rojas
2015-04-28  8:18         ` Jacek Anaszewski
2015-04-26 12:15       ` [PATCH v4 2/2] leds: add BCM6328 LED driver Álvaro Fernández Rojas
2015-04-28  8:18         ` Jacek Anaszewski
2015-04-28 16:50       ` [PATCH v5 0/2] " Álvaro Fernández Rojas
2015-04-28 16:50         ` [PATCH v5 1/2] leds: add DT binding for BCM6328 LED controller Álvaro Fernández Rojas
2015-04-28 16:50         ` [PATCH v5 2/2] leds: add BCM6328 LED driver Álvaro Fernández Rojas
     [not found]         ` <1430239850-26120-1-git-send-email-noltari-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-04-29  0:46           ` [PATCH v5 0/2] " 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=1427975661-29964-2-git-send-email-noltari@gmail.com \
    --to=noltari@gmail.com \
    --cc=cernekee@gmail.com \
    --cc=cooloney@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=jogo@openwrt.org \
    --cc=linux-leds@vger.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).