devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Oleh Kravchenko <oleg@kaa.org.ua>,
	devicetree@vger.kernel.org, linux-leds@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: Add vendor prefix and docs for CR0014114
Date: Tue, 27 Mar 2018 22:58:00 +0200	[thread overview]
Message-ID: <66fb58b2-2ae7-8edf-6c48-0f78f82c31a2@gmail.com> (raw)
In-Reply-To: <20180327164903.6307-1-oleg@kaa.org.ua>

Hi Oleh,

Thanks for the update.

Patch version is missing in the subject e.g. [PATCH v5 1/2].

On 03/27/2018 06:49 PM, Oleh Kravchenko wrote:
> - add vendor prefix for Crane;
> - add documentation and example for dt-bindings CR0014114.
> 
> Signed-off-by: Oleh Kravchenko <oleg@kaa.org.ua>
> ---
>  .../devicetree/bindings/leds/leds-cr0014114.txt    | 51 ++++++++++++++++++++++
>  .../devicetree/bindings/vendor-prefixes.txt        |  1 +
>  2 files changed, 52 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/leds/leds-cr0014114.txt
> 
> diff --git a/Documentation/devicetree/bindings/leds/leds-cr0014114.txt b/Documentation/devicetree/bindings/leds/leds-cr0014114.txt
> new file mode 100644
> index 000000000000..5f38f16aa08a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/leds-cr0014114.txt
> @@ -0,0 +1,51 @@
> +Crane Merchandising System - cr0014114 LED driver
> +-------------------------------------------------
> +
> +This LED Board is widely used in vending machines produced
> +by Crane Merchandising Systems.
> +
> +Required properties:
> +- compatible: "crane,cr0014114"
> +
> +LED sub-node properties:
> +- label :
> +	see Documentation/devicetree/bindings/leds/common.txt
> +- linux,default-trigger : (optional)
> +	see Documentation/devicetree/bindings/leds/common.txt
> +
> +Example
> +-------
> +
> +led-controller@0 {
> +	compatible = "crane,cr0014114";
> +	reg = <0>;
> +	spi-max-frequency = <50000>;
> +	#address-cells = <1>;
> +	#size-cells = <0>;
> +
> +	led@0 {
> +		reg = <0>;
> +		label = "cr0:red:coin";
> +	};
> +	led@1 {
> +		reg = <1>;
> +		label = "cr0:green:coin";
> +	};
> +	led@2 {
> +		reg = <2>;
> +		label = "cr0:blue:coin";
> +	};
> +	led@3 {
> +		reg = <3>;
> +		label = "cr1:red:bill";
> +	};
> +	led@4 {
> +		reg = <4>;
> +		label = "cr1:green:bill";
> +	};
> +	led@5 {
> +		reg = <5>;
> +		label = "cr1:blue:bill";
> +	};

Why cr0 and cr1? It should be cr0014114 to stick to the
current LED naming pattern <devicename:colour:function>.

Nonetheless, we lately came to the conclusion that devicename
segment is redundant in LED class device name, so until we change
LED naming convention officially, let's remove devicename segment
at least from DT and prepend the label with "cr0014114" in the driver.

Please compare how it is approached in [0] (not merged yet).

> +};
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index ae850d6c0ad3..f17949c365f5 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -75,6 +75,7 @@ cnxt	Conexant Systems, Inc.
>  compulab	CompuLab Ltd.
>  cortina	Cortina Systems, Inc.
>  cosmic	Cosmic Circuits
> +crane	Crane Connectivity Solutions
>  creative	Creative Technology Ltd
>  crystalfontz	Crystalfontz America, Inc.
>  cubietech	Cubietech, Ltd.
> 

[0] https://www.spinics.net/lists/devicetree/msg220561.html

-- 
Best regards,
Jacek Anaszewski



  parent reply	other threads:[~2018-03-27 20:59 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <026d9ec2-f2bd-18b9-d5fa-f593d40e2f57@kaa.org.ua>
2018-03-12 15:33 ` [PATCH] leds: add LED driver for CR0014114 board Oleh Kravchenko
2018-03-12 15:45   ` Peter Meerwald-Stadler
2018-03-12 15:54     ` Oleh Kravchenko
2018-03-17  8:19   ` Jacek Anaszewski
2018-03-12 15:58 ` [PATCH v2] " Oleh Kravchenko
2018-03-13 12:45   ` [PATCH v3] " Oleh Kravchenko
2018-03-16 21:14     ` Pavel Machek
2018-03-16 21:29       ` Oleh Kravchenko
2018-03-16 21:33         ` Pavel Machek
2018-03-16 21:40           ` Oleh Kravchenko
2018-03-16 22:10             ` Pavel Machek
2018-03-26 12:15             ` [PATCH v4 1/2] dt-bindings: Add vendor prefix and docs for CR0014114 Oleh Kravchenko
2018-03-26 12:15               ` [PATCH v4 2/2] leds: add LED driver for CR0014114 board Oleh Kravchenko
2018-03-27 16:14               ` [PATCH v4 1/2] dt-bindings: Add vendor prefix and docs for CR0014114 Rob Herring
2018-03-27 16:49               ` [PATCH " Oleh Kravchenko
2018-03-27 16:49                 ` [PATCH 2/2] leds: add LED driver for CR0014114 board Oleh Kravchenko
2018-03-27 20:58                   ` Jacek Anaszewski
2018-03-28  6:53                   ` [PATCH v6 1/2] dt-bindings: Add vendor prefix and docs for CR0014114 Oleh Kravchenko
2018-03-28  6:53                     ` [PATCH v6 2/2] leds: add LED driver for CR0014114 board Oleh Kravchenko
2018-03-28 15:43                     ` [PATCH v6 1/2] dt-bindings: Add vendor prefix and docs for CR0014114 Rob Herring
2018-03-28 18:56                     ` [PATCH v7 " Oleh Kravchenko
2018-03-28 18:56                       ` [PATCH v7 2/2] leds: add LED driver for CR0014114 board Oleh Kravchenko
2018-04-02 12:53                         ` [PATCH v8 1/2] dt-bindings: Add vendor prefix and docs for CR0014114 Oleh Kravchenko
2018-04-02 12:53                           ` [PATCH v8 2/2] leds: add LED driver for CR0014114 board Oleh Kravchenko
2018-04-03 10:48                             ` Pavel Machek
2018-04-10 18:59                             ` Jacek Anaszewski
2018-04-10 20:24                               ` Oleh Kravchenko
2018-04-09 19:18                           ` [PATCH v8 1/2] dt-bindings: Add vendor prefix and docs for CR0014114 Jacek Anaszewski
2018-04-09 21:10                           ` Rob Herring
2018-03-27 20:58                 ` Jacek Anaszewski [this message]
2018-03-28  6:36                   ` [PATCH " Oleh Kravchenko
2018-03-28 19:21                     ` Jacek Anaszewski
2018-03-28 19:48                       ` Oleh Kravchenko
2018-03-28 20:23                         ` Jacek Anaszewski
2018-03-29 18:56                           ` Oleh Kravchenko
2018-03-30 10:10                             ` Jacek Anaszewski
2018-03-18 12:49     ` [PATCH v3] leds: add LED driver for CR0014114 board Rob Herring
2018-03-18 20:03       ` Jacek Anaszewski
2018-03-18 23:38         ` Rob Herring
2018-03-19 21:18           ` Standardized LED function names [was: Re: [PATCH v3] leds: add LED driver for CR0014114 board] Jacek Anaszewski
2018-03-27 15:31             ` Rob Herring
2018-03-30 10:53               ` Jacek Anaszewski
2018-03-30 20:59                 ` Rob Herring
2018-04-15 16:15                 ` Pavel Machek
2018-04-15 18:30                   ` Jacek Anaszewski
2018-04-15 16:15             ` 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=66fb58b2-2ae7-8edf-6c48-0f78f82c31a2@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=oleg@kaa.org.ua \
    /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).