From: "G.Shark Jeong" <gshark.jeong@gmail.com>
To: Bryan Wu <bryan.wu@canonical.com>, Richard Purdie <rpurdie@rpsys.net>
Cc: Daniel Jeong <daniel.jeong@ti.com>,
<linux-kernel@vger.kernel.org>,
"G.Shark Jeong" <gshark.jeong@gmail.com>
Subject: [PATCH 0/1 v2] leds: Add new LED driver for lm355x chips
Date: Mon, 3 Sep 2012 16:29:07 +0900 [thread overview]
Message-ID: <1346657348-25282-1-git-send-email-gshark.jeong@gmail.com> (raw)
From: "G.Shark Jeong" <gshark.jeong@gmail.com>
LM3554 and LM3556 have similar functions but very different register map.
This driver is a general version for lm3554 and lm3556 both,led chips of TI.
lm3556 driver can be replaced by this driver.
LM3554 :
The LM3554 is a 2 MHz fixed-frequency synchronous boost
converter with 1.2A dual high side led drivers.
Datasheet: www.ti.com/lit/ds/symlink/lm3554.pdf
LM3556 :
The LM3556 is a 4 MHz fixed-frequency synchronous boost
converter plus 1.5A constant current driver for a high-current white LED.
Datasheet: www.national.com/ds/LM/LM3556.pdf
G.Shark Jeong (1):
leds: Add LED driver for lm355x chips
drivers/leds/Kconfig | 8 +-
drivers/leds/Makefile | 2 +-
drivers/leds/leds-lm3556.c | 512 -------------------------
drivers/leds/leds-lm355x.c | 574 +++++++++++++++++++++++++++++
include/linux/platform_data/leds-lm3556.h | 50 ---
include/linux/platform_data/leds-lm355x.h | 66 ++++
6 files changed, 645 insertions(+), 567 deletions(-)
delete mode 100644 drivers/leds/leds-lm3556.c
create mode 100644 drivers/leds/leds-lm355x.c
delete mode 100644 include/linux/platform_data/leds-lm3556.h
create mode 100644 include/linux/platform_data/leds-lm355x.h
--
1.7.5.4
next reply other threads:[~2012-09-03 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 7:29 G.Shark Jeong [this message]
2012-09-03 7:29 ` [PATCH 1/1 v2] leds: Add new LED driver for lm355x chips G.Shark Jeong
2012-09-04 8:39 ` Bryan Wu
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=1346657348-25282-1-git-send-email-gshark.jeong@gmail.com \
--to=gshark.jeong@gmail.com \
--cc=bryan.wu@canonical.com \
--cc=daniel.jeong@ti.com \
--cc=linux-kernel@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).