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 0/7] Multicolor Framework
Date: Thu, 11 Apr 2019 14:38:41 -0500 [thread overview]
Message-ID: <20190411193848.23140-1-dmurphy@ti.com> (raw)
I have updated the patchset for the multicolor framework and scrubed the base
code. I have incoroporated the minor changes that were asked for. But I still
have not added any code for the brightness models as this is still in discussion.
I have also included the TI LP50xx driver that demonstrates how to use the
Multicolor framework.
Finally I have built this on top of Jacek's LED name composition patchset
https://lore.kernel.org/patchwork/project/lkml/list/?series=388765
The MC FW will leverage the COLOR_ID and led_colors definitions provided there.
And I have added a new COLOR_ID to support this framework because with multicolor
having to declare a top level color for the directory just did not make sense
So the directory would be appended with multicolor which would denote that this
directory supports the MC FW
multicolor:activity multicolor:standby multicolor:status
Dan
Dan Murphy (7):
leds: multicolor: Add sysfs interface definition
dt: bindings: Add multicolor class dt bindings documention
documention: leds: Add multicolor class documentation
dt-bindings: leds: Add multicolor ID to the color ID list
leds: multicolor: Introduce a multicolor class definition
dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers
leds: lp50xx: Add the LP50XX family of the RGB LED driver
.../ABI/testing/sysfs-class-led-multicolor | 91 +++
.../devicetree/bindings/leds/common.txt | 2 +
.../bindings/leds/leds-class-multicolor.txt | 142 ++++
.../devicetree/bindings/leds/leds-lp50xx.txt | 142 ++++
Documentation/leds/leds-class-multicolor.txt | 99 +++
Documentation/leds/leds-lp50xx.txt | 36 +
drivers/leds/Kconfig | 17 +
drivers/leds/Makefile | 2 +
drivers/leds/led-class-multicolor.c | 401 ++++++++++
drivers/leds/led-class.c | 1 +
drivers/leds/leds-lp50xx.c | 716 ++++++++++++++++++
include/dt-bindings/leds/common.h | 3 +-
include/linux/led-class-multicolor.h | 74 ++
13 files changed, 1725 insertions(+), 1 deletion(-)
create mode 100644 Documentation/ABI/testing/sysfs-class-led-multicolor
create mode 100644 Documentation/devicetree/bindings/leds/leds-class-multicolor.txt
create mode 100644 Documentation/devicetree/bindings/leds/leds-lp50xx.txt
create mode 100644 Documentation/leds/leds-class-multicolor.txt
create mode 100644 Documentation/leds/leds-lp50xx.txt
create mode 100644 drivers/leds/led-class-multicolor.c
create mode 100644 drivers/leds/leds-lp50xx.c
create mode 100644 include/linux/led-class-multicolor.h
--
2.21.0.5.gaeb582a983
next reply other threads:[~2019-04-11 19:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 19:38 Dan Murphy [this message]
2019-04-11 19:38 ` [PATCH v2 1/7] leds: multicolor: Add sysfs interface definition Dan Murphy
2019-04-11 19:38 ` [PATCH v2 2/7] dt: bindings: Add multicolor class dt bindings documention Dan Murphy
2019-04-11 22:07 ` Marek Behun
2019-04-12 11:50 ` Dan Murphy
2019-04-12 19:10 ` Jacek Anaszewski
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 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 ` [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 ` [PATCH v2 6/7] dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers Dan Murphy
2019-04-11 20:54 ` Dan Murphy
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 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-1-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: 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).