From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: lee.jones@linaro.org, tony@atomide.com
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
jacek.anaszewski@gmail.com
Subject: [GIT PULL] LM3532 backlight support improvements and relocation
Date: Sun, 7 Apr 2019 20:25:13 +0200 [thread overview]
Message-ID: <20190407182514.15427-1-jacek.anaszewski@gmail.com> (raw)
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git tags/lm3532-driver-improvements
for you to fetch changes up to b3e9d18dc4a5e4d329dea32b59bdde5e012ae64a:
leds: lm3532: Introduce the lm3532 LED driver (2019-04-06 21:06:07 +0200)
Thanks,
Jacek Anaszewski
----------------------------------------------------------------
LM3532 backlight driver improvements and relocation.
----------------------------------------------------------------
Dan Murphy (4):
dt: lm3532: Add lm3532 dt doc and update ti_lmu doc
ARM: dts: omap4-droid4: Update backlight dt properties
mfd: ti-lmu: Remove LM3532 backlight driver references
leds: lm3532: Introduce the lm3532 LED driver
.../devicetree/bindings/leds/leds-lm3532.txt | 101 +++
Documentation/devicetree/bindings/mfd/ti-lmu.txt | 20 -
arch/arm/boot/dts/omap4-droid4-xt894.dts | 27 +-
drivers/leds/Kconfig | 10 +
drivers/leds/Makefile | 1 +
drivers/leds/leds-lm3532.c | 683 +++++++++++++++++++++
drivers/mfd/ti-lmu.c | 11 -
include/linux/mfd/ti-lmu-register.h | 44 --
include/linux/mfd/ti-lmu.h | 1 -
9 files changed, 813 insertions(+), 85 deletions(-)
create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3532.txt
create mode 100644 drivers/leds/leds-lm3532.c
next reply other threads:[~2019-04-07 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 18:25 Jacek Anaszewski [this message]
2019-04-07 18:25 ` [GIT PULL] LM3532 backlight support improvements and relocation Jacek Anaszewski
2019-05-08 8:04 ` Lee Jones
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=20190407182514.15427-1-jacek.anaszewski@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=tony@atomide.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).