linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-leds@vger.kernel.org,
	jacek.anaszewski@gmail.com, andriy.shevchenko@linux.intel.com,
	baolin.wang@linaro.org, dmurphy@ti.com, lhenriques@suse.com,
	oleg@kaa.org.ua, weiyongjun1@huawei.com
Subject: [GIT PULL] LED updates for 4.18-rc1
Date: Mon,  4 Jun 2018 22:50:09 +0200	[thread overview]
Message-ID: <1528145409-4978-1-git-send-email-jacek.anaszewski@gmail.com> (raw)

Hi Linus,

Please pull LED updates for 4.18-rc1. It was quite fruitful cycle, taking
into account usual traffic on linux-leds list, as we managed to merge
three new LED class drivers.

New LED class drivers with related DT bindings:
	- add LED driver for CR0014114 board
	- add Spreadtrum SC27xx breathing light controller driver
	- introduce the lm3601x LED driver

LED class fix:
	- ensure workqueue is initialized before setting brightness

Improvements and fixes to existing LED class drivers:
	- fix return value check in sc27xx_led_probe()
	- use sysfs_match_string() helper in wm831x_status_src_store()


This is my first pull request signed with use of a subkey exported to
Nitrokey, so please let me know if something is not as expected.


The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:

  Linux 4.17-rc1 (2018-04-15 18:24:20 -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_4.18-rc1

for you to fetch changes up to 6d71021ab3b0bd6ff98270343353b03dfae5d550:

  leds: class: ensure workqueue is initialized before setting brightness (2018-05-24 22:08:26 +0200)

Best regards,
Jacek Anaszewski

----------------------------------------------------------------
LED updates for 4.18-rc1
----------------------------------------------------------------
Andy Shevchenko (1):
      leds: wm831x-status: Use sysfs_match_string() helper

Baolin Wang (2):
      dt-bindings: leds: Add SC27xx breathing light controller documentation
      leds: Add Spreadtrum SC27xx breathing light controller driver

Dan Murphy (2):
      dt: bindings: lm3601x: Introduce the lm3601x driver
      leds: lm3601x: Introduce the lm3601x LED driver

Luis Henriques (1):
      leds: class: ensure workqueue is initialized before setting brightness

Oleh Kravchenko (2):
      dt-bindings: Add vendor prefix and docs for CR0014114
      leds: add LED driver for CR0014114 board

Wei Yongjun (1):
      leds: sc27xx: Fix return value check in sc27xx_led_probe()

 .../devicetree/bindings/leds/leds-cr0014114.txt    |  54 +++
 .../devicetree/bindings/leds/leds-lm3601x.txt      |  45 ++
 .../devicetree/bindings/leds/leds-sc27xx-bltc.txt  |  41 ++
 .../devicetree/bindings/vendor-prefixes.txt        |   1 +
 drivers/leds/Kconfig                               |  33 ++
 drivers/leds/Makefile                              |   3 +
 drivers/leds/led-class.c                           |  10 +-
 drivers/leds/leds-cr0014114.c                      | 315 +++++++++++++
 drivers/leds/leds-lm3601x.c                        | 487 +++++++++++++++++++++
 drivers/leds/leds-sc27xx-bltc.c                    | 244 +++++++++++
 drivers/leds/leds-wm831x-status.c                  |  22 +-
 11 files changed, 1237 insertions(+), 18 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/leds/leds-cr0014114.txt
 create mode 100644 Documentation/devicetree/bindings/leds/leds-lm3601x.txt
 create mode 100644 Documentation/devicetree/bindings/leds/leds-sc27xx-bltc.txt
 create mode 100644 drivers/leds/leds-cr0014114.c
 create mode 100644 drivers/leds/leds-lm3601x.c
 create mode 100644 drivers/leds/leds-sc27xx-bltc.c

                 reply	other threads:[~2018-06-04 20:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1528145409-4978-1-git-send-email-jacek.anaszewski@gmail.com \
    --to=jacek.anaszewski@gmail.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=baolin.wang@linaro.org \
    --cc=dmurphy@ti.com \
    --cc=lhenriques@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=oleg@kaa.org.ua \
    --cc=torvalds@linux-foundation.org \
    --cc=weiyongjun1@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;
as well as URLs for NNTP newsgroup(s).