From: Andrew Lunn <andrew@lunn.ch>
To: cooloney@gmail.com, rpurdie@rpsys.net
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux ARM <linux-arm-kernel@lists.infradead.org>,
Andrew Lunn <andrew@lunn.ch>,
Matthew.Fatheree@belkin.com
Subject: [PATCH 0/2] Driver for TI tlc59116 16 Channel i2c LED driver
Date: Fri, 9 Jan 2015 01:26:16 +0100 [thread overview]
Message-ID: <1420763178-10115-1-git-send-email-andrew@lunn.ch> (raw)
This patchset is a driver for the TI tlc59116 16 Channel i2c LED
driver. This driver is used on the Belkin WRT1900AC access point and
the C code is derived from code Belkin contributed to OpenWRT.
However it has been extensively re-written, and a device tree binding
added to replace platform data.
Cc: Matthew.Fatheree@belkin.com
Andrew Lunn (2):
leds: tlc59116: Document binding for the TI 16 Channel i2c LED driver
leds: tlc59116: Driver for the TI 16 Channel i2c LED driver
.../devicetree/bindings/leds/leds-tlc59116.txt | 41 ++++
drivers/leds/Kconfig | 7 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-tlc59116.c | 253 +++++++++++++++++++++
4 files changed, 302 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/leds-tlc59116.txt
create mode 100644 drivers/leds/leds-tlc59116.c
--
2.1.3
next reply other threads:[~2015-01-09 0:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 0:26 Andrew Lunn [this message]
2015-01-09 0:26 ` [PATCH 1/2] leds: tlc59116: Document binding for the TI 16 Channel i2c LED driver Andrew Lunn
2015-01-09 1:02 ` Bryan Wu
2015-01-09 1:34 ` Andrew Lunn
[not found] ` <1420763178-10115-1-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2015-01-09 0:26 ` [PATCH 2/2] leds: tlc59116: Driver " Andrew Lunn
[not found] ` <1420763178-10115-3-git-send-email-andrew-g2DYL2Zd6BY@public.gmane.org>
2015-01-09 0:36 ` Varka Bhadram
2015-01-09 1:42 ` Andrew Lunn
2015-01-09 1:26 ` Bryan Wu
2015-01-09 1:38 ` Andrew Lunn
2015-01-09 12:46 ` Imre Kaloz
2015-01-09 13:58 ` Andrew Lunn
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=1420763178-10115-1-git-send-email-andrew@lunn.ch \
--to=andrew@lunn.ch \
--cc=Matthew.Fatheree@belkin.com \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-leds@vger.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).