From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
"H. Nikolaus Schaller" <hns@goldelico.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, kernel@pyra-handheld.com,
marek@goldelico.com, letux-kernel@openphoenux.org
Subject: [PATCH v2 0/2] driver: leds: is31fl319x dimmable LED driver
Date: Wed, 6 Jul 2016 12:02:42 +0200 [thread overview]
Message-ID: <cover.1467799364.git.hns@goldelico.com> (raw)
Changes V2:
* suggested by David Rifshin
* add more "compatible" strings for other chip variants/brands
* renumber output <reg> values to expect a range of 1..9
* fixes for typos and DT example, Kconfig message
* fix location in Makefile and Kconfig
* remove some dead/not implemented code
* use of_property_read_string for better error handling
* coding style improvements
* use devm_led_classdev_register and simplify error path
* suggested by Jacek Anaszewski
* fix more typos & writing style
* separate bindings document into a second patch
* max current property renamed and define uA instead of mA
* debugging message improvements
* remove platform data and header file completely and therefore require DT
* use regmap to handle caching and locking + i2c serialization
* suggested by Rob Herring
* bindings documentation style improvements
V1: 2016-04-18 20:43:18:
This patch adds a driver for the is31fl3196/99 dimmable dual/triple rgb
controller chips from ISSI.
H. Nikolaus Schaller (2):
drivers: led: is31fl319x: 1/3/6/9-channel light effect led driver
Bindings documentation for ISSI is31fl319x driver
.../devicetree/bindings/leds/is31fl319x.txt | 52 +++
drivers/leds/Kconfig | 8 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-is31fl319x.c | 354 +++++++++++++++++++++
4 files changed, 415 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/is31fl319x.txt
create mode 100644 drivers/leds/leds-is31fl319x.c
--
2.7.3
next reply other threads:[~2016-07-06 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 10:02 H. Nikolaus Schaller [this message]
2016-07-06 10:02 ` [PATCH v2 1/2] drivers: led: is31fl319x: 1/3/6/9-channel light effect led driver H. Nikolaus Schaller
2016-07-07 6:35 ` kbuild test robot
2016-07-07 8:47 ` Jacek Anaszewski
2016-07-07 9:03 ` H. Nikolaus Schaller
2016-07-07 11:32 ` Jacek Anaszewski
2016-07-07 13:00 ` H. Nikolaus Schaller
2016-07-07 14:19 ` Jacek Anaszewski
[not found] ` <cover.1467799364.git.hns-xXXSsgcRVICgSpxsJD1C4w@public.gmane.org>
2016-07-06 10:02 ` [PATCH v2 2/2] Bindings documentation for ISSI is31fl319x driver H. Nikolaus Schaller
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=cover.1467799364.git.hns@goldelico.com \
--to=hns@goldelico.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=j.anaszewski@samsung.com \
--cc=kernel@pyra-handheld.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marek@goldelico.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@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).