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>,
kaloz@openwrt.org, Andrew Lunn <andrew@lunn.ch>,
Matthew.Fatheree@belkin.com
Subject: [PATCHv2 0/2] Driver for TI tlc59116 16 Channel i2c LED driver
Date: Fri, 9 Jan 2015 23:45:43 +0100 [thread overview]
Message-ID: <1420843545-30892-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
Since v1:
s/uint8_t/u8/g
Remove empty line
Removed #gpio-cells
Added select REGMAP_I2C
Sorted #includes into alphabetic order
Added missing MODULE_DEVICE_TABLE(of, ...)
Check return value of regmap_write()
Simplified tlc59116_set_mode()
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 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 22:45 Andrew Lunn [this message]
2015-01-09 22:45 ` [PATCHv2 1/2] leds: tlc59116: Document binding for the TI 16 Channel i2c LED driver Andrew Lunn
2015-01-09 22:45 ` [PATCHv2 2/2] leds: tlc59116: Driver " Andrew Lunn
2015-01-13 18:55 ` Bryan Wu
2015-01-13 19:13 ` Andrew Lunn
2015-01-13 19:18 ` Bryan Wu
2015-01-13 19:28 ` 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=1420843545-30892-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=kaloz@openwrt.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).