From: Ingi Kim <ingi2.kim@samsung.com>
To: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
sameo@linux.intel.com, lee.jones@linaro.org, rpurdie@rpsys.net,
j.anaszewski@samsung.com
Cc: inki.dae@samsung.com, sw0312.kim@samsung.com,
beomho.seo@samsung.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
Ingi Kim <ingi2.kim@samsung.com>
Subject: [PATCH v2 0/3] Add RT5033 Flash LED driver
Date: Mon, 12 Oct 2015 22:12:55 +0900 [thread overview]
Message-ID: <1444655578-19806-1-git-send-email-ingi2.kim@samsung.com> (raw)
This patch supports flash led of RT5033 PMIC.
Changes since v2:
- Split MFC code from rt5033 flash led patch
- Fix typo error
- Change naming of mfd register back again
- Fix compile error
Ingi Kim (3):
leds: rt5033: Add DT binding for RT5033
mfd: rt5033: Add RT5033 Flash led sub device
leds: rt5033: Add RT5033 Flash led device driver
.../devicetree/bindings/leds/leds-rt5033.txt | 38 ++++
drivers/leds/Kconfig | 8 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-rt5033.c | 223 +++++++++++++++++++++
drivers/mfd/rt5033.c | 6 +-
include/linux/mfd/rt5033-private.h | 49 +++++
include/linux/mfd/rt5033.h | 22 +-
7 files changed, 344 insertions(+), 3 deletions(-)
create mode 100644 Documentation/devicetree/bindings/leds/leds-rt5033.txt
create mode 100644 drivers/leds/leds-rt5033.c
--
2.0.5
next reply other threads:[~2015-10-12 13:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 13:12 Ingi Kim [this message]
2015-10-12 13:12 ` [PATCH v2 1/3] leds: rt5033: Add DT binding for RT5033 Ingi Kim
2015-10-12 13:12 ` [PATCH v2 2/3] mfd: rt5033: Add RT5033 Flash led sub device Ingi Kim
2015-10-13 7:06 ` Lee Jones
2015-10-13 8:03 ` Ingi Kim
2015-10-12 13:12 ` [PATCH v2 3/3] leds: rt5033: Add RT5033 Flash led device driver Ingi Kim
2015-10-12 15:10 ` Jacek Anaszewski
2015-10-13 2:58 ` Ingi Kim
2015-10-13 8:53 ` Jacek Anaszewski
2015-10-16 6:09 ` Ingi Kim
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=1444655578-19806-1-git-send-email-ingi2.kim@samsung.com \
--to=ingi2.kim@samsung.com \
--cc=beomho.seo@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=inki.dae@samsung.com \
--cc=j.anaszewski@samsung.com \
--cc=lee.jones@linaro.org \
--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=sameo@linux.intel.com \
--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
all inboxes | Powered by JetHome®