From: Stefan Wahren <stefan.wahren@i2se.com>
To: Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>
Subject: [PATCH RFC 0/3] leds: add SN3218 LED driver
Date: Thu, 28 Jan 2016 20:41:04 +0000 [thread overview]
Message-ID: <1454013667-25889-1-git-send-email-stefan.wahren@i2se.com> (raw)
This patch series implements support for the Si-En SN3218
18 Channel LED Driver through I2C. This implemention only write
data over I2C und get the platform data via DT.
The driver has been tested on a Raspberry Pi B.
Stefan Wahren (3):
of: Add vendor prefix for Si-En Technology
DT: add binding for SN3218 LED driver
leds: add SN3218 LED driver
.../devicetree/bindings/leds/leds-sn3218.txt | 41 ++++
.../devicetree/bindings/vendor-prefixes.txt | 1 +
drivers/leds/Kconfig | 8 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-sn3218.c | 254 ++++++++++++++++++++
5 files changed, 305 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/leds-sn3218.txt
create mode 100644 drivers/leds/leds-sn3218.c
--
1.7.9.5
next reply other threads:[~2016-01-28 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 20:41 Stefan Wahren [this message]
2016-01-28 20:41 ` [PATCH RFC 2/3] DT: add binding for SN3218 LED driver Stefan Wahren
2016-01-29 3:26 ` Rob Herring
[not found] ` <1454013667-25889-1-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2016-01-28 20:41 ` [PATCH RFC 1/3] of: Add vendor prefix for Si-En Technology Stefan Wahren
[not found] ` <1454013667-25889-2-git-send-email-stefan.wahren-eS4NqCHxEME@public.gmane.org>
2016-01-29 3:27 ` Rob Herring
2016-01-28 20:41 ` [PATCH RFC 3/3] leds: add SN3218 LED driver Stefan Wahren
2016-01-29 12:54 ` Jacek Anaszewski
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=1454013667-25889-1-git-send-email-stefan.wahren@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
/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).