devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: list@c-mauderer.de
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
	Jacek Anaszewski <jacek.anaszewski@gmail.com>,
	Dan Murphy <dmurphy@ti.com>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Christian Mauderer <oss@c-mauderer.de>
Subject: Re: [PATCH 1/2] dt-bindings: leds: Add binding for ubnt-spi LED.
Date: Sat, 4 May 2019 18:12:37 +0200	[thread overview]
Message-ID: <20190504161237.GA24060@amd> (raw)
In-Reply-To: <20190504122825.11883-1-list@c-mauderer.de>

[-- Attachment #1: Type: text/plain, Size: 2228 bytes --]

On Sat 2019-05-04 14:28:24, list@c-mauderer.de wrote:
> From: Christian Mauderer <oss@c-mauderer.de>
> 
> This patch adds the binding documentation for the LED controller found
> in Ubiquity airCube ISP devices.
> 
> Signed-off-by: Christian Mauderer <oss@c-mauderer.de>
> ---
> 
> I tested the patches with a 4.14 and a 4.19 kernel on the current OpenWRT.
> Although I didn't get the kernel running due to file system problems they build
> fine with a 5.1-rc7.
> 
> I shortly described the protocol of the controller in a comment in the driver
> file in the second patch.
> 
> Checkpatch gives the following warning for both patches:
> 
>   WARNING: added, moved or deleted file(s), does MAINTAINERS need
> updating?

Ignore that :-).

> diff --git a/Documentation/devicetree/bindings/leds/leds-ubnt-spi.txt b/Documentation/devicetree/bindings/leds/leds-ubnt-spi.txt
> new file mode 100644
> index 000000000000..ab1478cdc139
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/leds-ubnt-spi.txt
> @@ -0,0 +1,49 @@
> +Binding for the controller based LED found in Ubiquity airCube ISP and most
> +likely some other Ubiquity devices.

It would be good to know what chip it is.. and name the binding
accordingly.

Alternatively, call its led-spi-byte, or something, as it is really
trivial protocol. Maybe other chips will have same interface?

> +Example for the airCube ISP (with SPI controller matching that device):
> +
> +led_spi {
> +	compatible = "spi-gpio";
> +	#address-cells = <1>;
> +	#size-cells = <0>;
> +
> +	gpio-sck = <&gpio 3 GPIO_ACTIVE_HIGH>;
> +	gpio-mosi = <&gpio 2 GPIO_ACTIVE_HIGH>;
> +	cs-gpios = <&gpio 1 GPIO_ACTIVE_HIGH>;
> +	num-chipselects = <1>;
> +
> +	led_ubnt@0 {
> +		compatible = "ubnt,spi-led";
> +		reg = <0>;
> +		spi-max-frequency = <100000>;
> +
> +		led {
> +			label = "system";
> +			/* keep the LED slightly on to show powered device */
> +			ubnt-spi,off_bright = /bits/ 8 <4>;
> +		};
> +	};
> +};

Otherwise looks good to me,

Acked-by: Pavel Machek <pavel@ucw.cz>

-- 
(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 --]

  parent reply	other threads:[~2019-05-04 16:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-04 12:28 [PATCH 1/2] dt-bindings: leds: Add binding for ubnt-spi LED list
2019-05-04 12:28 ` [PATCH 2/2] leds: ubnt-spi: Add Ubnt AirCube ISP LED driver list
2019-05-04 16:20   ` Pavel Machek
2019-05-04 16:43     ` Christian Mauderer
2019-05-04 17:25       ` Pavel Machek
2019-05-04 16:12 ` Pavel Machek [this message]
2019-05-04 16:46   ` [PATCH 1/2] dt-bindings: leds: Add binding for ubnt-spi LED Christian Mauderer
2019-05-04 19:34 ` Jacek Anaszewski
2019-05-04 19:45   ` Jacek Anaszewski
2019-05-04 20:01     ` Christian Mauderer
2019-05-04 20:07       ` Jacek Anaszewski
2019-05-04 19:48   ` Christian Mauderer
2019-05-04 20:01     ` Jacek Anaszewski
2019-05-04 20:34       ` Pavel Machek
2019-05-04 22:17         ` Pavel Machek
2019-05-05  8:01           ` Christian Mauderer
2019-05-05 10:56           ` Jacek Anaszewski
2019-05-05 11:51             ` Christian Mauderer
2019-05-05 12:15               ` Jacek Anaszewski
2019-05-05 11:54             ` Pavel Machek

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=20190504161237.GA24060@amd \
    --to=pavel@ucw.cz \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-leds@vger.kernel.org \
    --cc=list@c-mauderer.de \
    --cc=mark.rutland@arm.com \
    --cc=oss@c-mauderer.de \
    --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;
as well as URLs for NNTP newsgroup(s).