From: Dan Murphy <dmurphy@ti.com> To: robh+dt@kernel.org, jacek.anaszewski@gmail.com, pavel@ucw.cz, marek.behun@nic.cz, rdunlap@infradead.org Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org, Dan Murphy <dmurphy@ti.com> Subject: [PATCH v2 4/7] dt-bindings: leds: Add multicolor ID to the color ID list Date: Thu, 11 Apr 2019 14:38:45 -0500 [thread overview] Message-ID: <20190411193848.23140-5-dmurphy@ti.com> (raw) In-Reply-To: <20190411193848.23140-1-dmurphy@ti.com> Add a new color ID that is declared as MULTICOLOR as with the multicolor framework declaring a definitive color is not accurate as the node can contain multiple colors. Signed-off-by: Dan Murphy <dmurphy@ti.com> --- drivers/leds/led-class.c | 1 + include/dt-bindings/leds/common.h | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c index bfd46a9bba63..11dd78b63403 100644 --- a/drivers/leds/led-class.c +++ b/drivers/leds/led-class.c @@ -35,6 +35,7 @@ const char *led_colors[LED_COLOR_ID_COUNT] = { [LED_COLOR_ID_VIOLET] = "violet", [LED_COLOR_ID_YELLOW] = "yellow", [LED_COLOR_ID_IR] = "ir", + [LED_COLOR_ID_MULTI] = "multicolor", }; EXPORT_SYMBOL_GPL(led_colors); diff --git a/include/dt-bindings/leds/common.h b/include/dt-bindings/leds/common.h index c95f39b3a254..f6df2c63398e 100644 --- a/include/dt-bindings/leds/common.h +++ b/include/dt-bindings/leds/common.h @@ -64,6 +64,7 @@ #define LED_COLOR_ID_VIOLET 5 #define LED_COLOR_ID_YELLOW 6 #define LED_COLOR_ID_IR 7 -#define LED_COLOR_ID_COUNT 8 +#define LED_COLOR_ID_MULTI 8 +#define LED_COLOR_ID_COUNT 9 #endif /* __DT_BINDINGS_LEDS_H */ -- 2.21.0.5.gaeb582a983
WARNING: multiple messages have this Message-ID (diff)
From: Dan Murphy <dmurphy@ti.com> To: <robh+dt@kernel.org>, <jacek.anaszewski@gmail.com>, <pavel@ucw.cz>, <marek.behun@nic.cz>, <rdunlap@infradead.org> Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-leds@vger.kernel.org>, Dan Murphy <dmurphy@ti.com> Subject: [PATCH v2 4/7] dt-bindings: leds: Add multicolor ID to the color ID list Date: Thu, 11 Apr 2019 14:38:45 -0500 [thread overview] Message-ID: <20190411193848.23140-5-dmurphy@ti.com> (raw) In-Reply-To: <20190411193848.23140-1-dmurphy@ti.com> Add a new color ID that is declared as MULTICOLOR as with the multicolor framework declaring a definitive color is not accurate as the node can contain multiple colors. Signed-off-by: Dan Murphy <dmurphy@ti.com> --- drivers/leds/led-class.c | 1 + include/dt-bindings/leds/common.h | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c index bfd46a9bba63..11dd78b63403 100644 --- a/drivers/leds/led-class.c +++ b/drivers/leds/led-class.c @@ -35,6 +35,7 @@ const char *led_colors[LED_COLOR_ID_COUNT] = { [LED_COLOR_ID_VIOLET] = "violet", [LED_COLOR_ID_YELLOW] = "yellow", [LED_COLOR_ID_IR] = "ir", + [LED_COLOR_ID_MULTI] = "multicolor", }; EXPORT_SYMBOL_GPL(led_colors); diff --git a/include/dt-bindings/leds/common.h b/include/dt-bindings/leds/common.h index c95f39b3a254..f6df2c63398e 100644 --- a/include/dt-bindings/leds/common.h +++ b/include/dt-bindings/leds/common.h @@ -64,6 +64,7 @@ #define LED_COLOR_ID_VIOLET 5 #define LED_COLOR_ID_YELLOW 6 #define LED_COLOR_ID_IR 7 -#define LED_COLOR_ID_COUNT 8 +#define LED_COLOR_ID_MULTI 8 +#define LED_COLOR_ID_COUNT 9 #endif /* __DT_BINDINGS_LEDS_H */ -- 2.21.0.5.gaeb582a983
next prev parent reply other threads:[~2019-04-11 19:38 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-11 19:38 [PATCH v2 0/7] Multicolor Framework Dan Murphy 2019-04-11 19:38 ` Dan Murphy 2019-04-11 19:38 ` [PATCH v2 1/7] leds: multicolor: Add sysfs interface definition Dan Murphy 2019-04-11 19:38 ` Dan Murphy 2019-04-11 19:38 ` [PATCH v2 2/7] dt: bindings: Add multicolor class dt bindings documention Dan Murphy 2019-04-11 19:38 ` Dan Murphy 2019-04-11 22:07 ` Marek Behun 2019-04-11 22:07 ` Marek Behun 2019-04-12 11:50 ` Dan Murphy 2019-04-12 11:50 ` Dan Murphy 2019-04-12 19:10 ` Jacek Anaszewski 2019-04-12 22:02 ` Dan Murphy 2019-04-12 22:02 ` Dan Murphy 2019-04-13 9:54 ` Jacek Anaszewski 2019-04-12 18:14 ` Jacek Anaszewski 2019-04-12 18:46 ` Dan Murphy 2019-04-12 18:46 ` Dan Murphy 2019-04-12 19:24 ` Jacek Anaszewski 2019-04-11 19:38 ` [PATCH v2 3/7] documention: leds: Add multicolor class documentation Dan Murphy 2019-04-11 19:38 ` Dan Murphy 2019-04-11 19:38 ` Dan Murphy [this message] 2019-04-11 19:38 ` [PATCH v2 4/7] dt-bindings: leds: Add multicolor ID to the color ID list Dan Murphy 2019-04-11 19:38 ` [PATCH v2 5/7] leds: multicolor: Introduce a multicolor class definition Dan Murphy 2019-04-11 19:38 ` Dan Murphy 2019-04-11 19:38 ` [PATCH v2 6/7] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Dan Murphy 2019-04-11 19:38 ` Dan Murphy 2019-04-11 20:54 ` Dan Murphy 2019-04-11 20:54 ` Dan Murphy 2019-04-29 21:15 ` Rob Herring 2019-04-29 21:15 ` Rob Herring 2019-04-11 19:38 ` [PATCH v2 7/7] leds: lp50xx: Add the LP50XX family of the RGB LED driver Dan Murphy 2019-04-11 19:38 ` Dan Murphy 2019-04-11 20:53 ` Dan Murphy 2019-04-11 20:53 ` Dan Murphy
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=20190411193848.23140-5-dmurphy@ti.com \ --to=dmurphy@ti.com \ --cc=devicetree@vger.kernel.org \ --cc=jacek.anaszewski@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-leds@vger.kernel.org \ --cc=marek.behun@nic.cz \ --cc=pavel@ucw.cz \ --cc=rdunlap@infradead.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.