From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
andriy.shevchenko@linux.intel.com, colin.king@canonical.com,
daniel@zonque.org, dmurphy@ti.com, info@metux.net,
jacek.anaszewski@gmail.com, pavel@ucw.cz,
sakari.ailus@linux.intel.com, yuehaibing@huawei.com
Subject: [GIT PULL] LED updates for 5.2-rc1
Date: Tue, 7 May 2019 20:42:25 +0200 [thread overview]
Message-ID: <20190507184225.5309-1-jacek.anaszewski@gmail.com> (raw)
Hi Linus,
Please pull LED updates for 5.2-rc1.
At first, the things touching other subsystems:
Merge of immutable branch between LED, MFD and OMAP Device Tree:
lm3532 driver relocation from MFD to LED subsystem,
accompanied by various improvements and optimizations;
it entails also a change in omap4-droid4-xt894.dts:
- leds: lm3532: Introduce the lm3532 LED driver
- mfd: ti-lmu: Remove LM3532 backlight driver references
- ARM: dts: omap4-droid4: Update backlight dt properties
- dt: lm3532: Add lm3532 dt doc and update ti_lmu doc
LED related addition to ACPI documentation:
- document how to refer to LEDs from remote nodes
LED related fix to ALSA line6/toneport driver:
- avoid polluting led_* namespace
Besides that there are regular LED updates:
LED core fixes and improvements:
- avoid races with workqueue
- Kconfig: pedantic cleanup
- small fixes for Flash class description
leds-lt3593:
- remove unneeded assignment in lt3593_led_probe
- drop pdata handling code
leds-blinkm:
- clean up double assignment to data->i2c_addr
leds-pca955x, leds-pca963x:
- revert ACPI support, as it turned out that there is no evidence
of officially registered ACPI IDs for these devices.
- make use of device property API
leds-as3645a:
- switch to fwnode property API
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/leds-for-5.2-rc1
for you to fetch changes up to 0db37915d912e8dc6588f25da76d3ed36718d92f:
leds: avoid races with workqueue (2019-05-02 22:54:51 +0200)
Thanks,
Jacek Anaszewski
----------------------------------------------------------------
LED updates for 5.2-rc1.
----------------------------------------------------------------
Andy Shevchenko (4):
leds: pca963x: Revert "Add ACPI support"
leds: pca955x: Revert "Add ACPI support"
leds: pca955x: Make use of device property API
leds: pca963x: Make use of device property API
Colin Ian King (1):
leds: blinkm: clean up double assignment to data->i2c_addr
Dan Murphy (5):
leds: Small fixes for Flash class description
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
Daniel Mack (1):
leds: lt3593: drop pdata handling code
Enrico Weigelt, metux IT consult (1):
drivers: leds: Kconfig: pedantic cleanups
Jacek Anaszewski (2):
Merge tag 'lm3532-driver-improvements' into for-next
ALSA: line6: Avoid polluting led_* namespace
Pavel Machek (1):
leds: avoid races with workqueue
Sakari Ailus (2):
leds: as3645a: Switch to fwnode property API
ACPI: Document how to refer to LEDs from remote nodes
YueHaibing (1):
leds: lt3593: Remove unneeded assignment in lt3593_led_probe
Documentation/acpi/dsd/leds.txt | 99 +++
.../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 | 33 +-
drivers/leds/Makefile | 1 +
drivers/leds/led-class.c | 1 +
drivers/leds/led-core.c | 5 +
drivers/leds/leds-as3645a.c | 93 +--
drivers/leds/leds-blinkm.c | 1 -
drivers/leds/leds-lm3532.c | 683 +++++++++++++++++++++
drivers/leds/leds-lt3593.c | 64 +-
drivers/leds/leds-pca955x.c | 57 +-
drivers/leds/leds-pca963x.c | 66 +-
drivers/mfd/ti-lmu.c | 11 -
include/linux/mfd/ti-lmu-register.h | 44 --
include/linux/mfd/ti-lmu.h | 1 -
sound/usb/line6/toneport.c | 8 +-
18 files changed, 1023 insertions(+), 292 deletions(-)
create mode 100644 Documentation/acpi/dsd/leds.txt
create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3532.txt
create mode 100644 drivers/leds/leds-lm3532.c
next reply other threads:[~2019-05-07 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 18:42 Jacek Anaszewski [this message]
2019-05-08 2:40 ` pr-tracker-bot
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=20190507184225.5309-1-jacek.anaszewski@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=colin.king@canonical.com \
--cc=daniel@zonque.org \
--cc=dmurphy@ti.com \
--cc=info@metux.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sakari.ailus@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=yuehaibing@huawei.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®