From: Varka Bhadram <varkabhadram@gmail.com>
To: Ingi Kim <ingi2.kim@samsung.com>,
cooloney@gmail.com, rpurdie@rpsys.net, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org
Cc: sakari.ailus@iki.fi, j.anaszewski@samsung.com, joe@perches.com,
sw0312.kim@samsung.com, cw00.choi@samsung.com,
jh80.chung@samsung.com, ideal.song@samsung.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH v7 0/3] Add ktd2692 Flash LED driver using LED Flash class
Date: Fri, 24 Apr 2015 15:00:35 +0530 [thread overview]
Message-ID: <553A0D3B.2060101@gmail.com> (raw)
In-Reply-To: <1429795085-22171-1-git-send-email-ingi2.kim@samsung.com>
On 04/23/2015 06:48 PM, Ingi Kim wrote:
> This patch adds ktd2692 Flash LED driver with LED Flash class
>
> Change in v7:
> - Add flash-max-microamp property for Flash LED
> - Change gpio-legacy interface to gpio consumer interface
>
> Change in v6 resend:
> - Adjust indent using checkpatch.pl script with strict option
>
> Change in v6:
> - Change goto label to if-else
> - Change DT binding style for LED device binding
>
> Change in v5:
> - Clean up the code
> - Fix help message of Kconfig
> - Fix issue related with regulator and mutex usage
> - Remove tab spaces in bindings
>
> Change in v4:
> - Clean up the code
> - Modify binding documentation of ktd2692
>
> Change in v3:
> - Clean up the code
> - Add aux gpio pin to control Flash LED
>
> Change in v2:
> - Introduction of LED Flash class as Jacek's comment
> - Supplement of binding documentation
> - Rename gpio control pin and remove unused pin
> - Add regulator for the Flash LED
>
> Ingi Kim (3):
> of: Add vendor prefix for Kinetic technologies
> leds: ktd2692: add device tree bindings for ktd2692
> leds: Add ktd2692 flash LED driver
>
> .../devicetree/bindings/leds/leds-ktd2692.txt | 47 +++
> .../devicetree/bindings/vendor-prefixes.txt | 1 +
> drivers/leds/Kconfig | 9 +
> drivers/leds/Makefile | 1 +
> drivers/leds/leds-ktd2692.c | 435 +++++++++++++++++++++
> 5 files changed, 493 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/leds/leds-ktd2692.txt
> create mode 100644 drivers/leds/leds-ktd2692.c
>
Reviewed-by: Varka Bhadram <varkabhadram@gmail.com>
Thanks
--
Varka Bhadram
prev parent reply other threads:[~2015-04-24 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 13:18 [PATCH v7 0/3] Add ktd2692 Flash LED driver using LED Flash class Ingi Kim
2015-04-23 13:18 ` [PATCH v7 1/3] of: Add vendor prefix for Kinetic technologies Ingi Kim
2015-04-23 13:18 ` [PATCH v7 2/3] leds: ktd2692: add device tree bindings for ktd2692 Ingi Kim
2015-04-24 13:29 ` Jacek Anaszewski
2015-04-27 6:32 ` Ingi Kim
2015-04-23 13:18 ` [PATCH v7 3/3] leds: Add ktd2692 flash LED driver Ingi Kim
2015-04-24 9:30 ` Varka Bhadram [this message]
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=553A0D3B.2060101@gmail.com \
--to=varkabhadram@gmail.com \
--cc=cooloney@gmail.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ideal.song@samsung.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=ingi2.kim@samsung.com \
--cc=j.anaszewski@samsung.com \
--cc=jh80.chung@samsung.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
--cc=sakari.ailus@iki.fi \
--cc=sw0312.kim@samsung.com \
/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).