All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>
Subject: [GIT PULL] LEDs for v6.18
Date: Wed, 1 Oct 2025 15:01:09 +0100	[thread overview]
Message-ID: <20251001140109.GV8757@google.com> (raw)

Good afternoon Linus,

The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:

  Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git leds-next-6.18

for you to fetch changes up to 64826db1e2e177b58dcbc7cf1e1379527be2185a:

  dt-bindings: leds: as3645: Convert to DT schema (2025-09-25 13:01:32 +0100)

----------------------------------------------------------------
LEDs for v6.18

This submission is a mix of new features, a number of fixes, some clean-up/refactoring and a
few Device Tree binding updates.  The most significant changes include new device support for
the IS31FL3236A and QNAP's status LEDs, a number of fixes for the Qualcomm flash, LP55xx,
MAX77705 and QNAP MCU drivers, along with some generic LED consumer binding documentation and
unification.

New Support & Features
- Add support for the IS31FL3236A LED driver, including an optional 22kHz PWM frequency setting.
- Add support for the red and green status LEDs on QNAP MCU devices.

Improvements & Fixes
- Fix an issue in the MAX77705 driver where an error value was assigned but not returned.
- Correctly update the torch current clamp setting in the Qualcomm flash LED driver to prevent
  unexpected clamping.
- Add a separate register map for the PMI8998 to the Qualcomm flash LED driver to handle its
  unique register layout.
- Fix the state numbering for the USB LED in the QNAP MCU driver to avoid command conflicts.
- Correct the memory programming address calculation for non-paged devices like the LP5562 in
  the LP55xx driver.
- Add Device Tree support to the generic led_get() function, allowing LEDs to be looked up by
  name.

Cleanups & Refactoring
- Fix a spelling mistake in the Kconfig help text for the BD2606MVV driver.
- Use devm_mutex_init() in the IS31FL319x driver to simplify code.

Device Tree Bindings Updates
- Drop the redundant '-db' suffix from the IS31FL319x binding.
- Introduce generic LED consumer bindings for referencing LEDs via phandles.
- Unify the 'leds' property across several bindings to use the new generic consumer binding.
- Convert the AMS AS3645A LED controller binding to the DT schema format.

----------------------------------------------------------------
Aleksandrs Vinarskis (2):
      dt-bindings: leds: Add generic LED consumer documentation
      dt-bindings: leds: Unify 'leds' property

Andrei Lalaev (1):
      leds: leds-lp55xx: Use correct address for memory programming

Christophe JAILLET (1):
      leds: is31fl319x: Use devm_mutex_init()

Colin Ian King (1):
      leds: Kconfig: Fix spelling mistake "limitiation" -> "limitation"

Fenglin Wu (2):
      leds: flash: leds-qcom-flash: Update torch current clamp setting
      leds: flash: leds-qcom-flash: Add a separate register map for PMI8998

Hans de Goede (1):
      leds: led-class: Add Device Tree support to led_get()

Harrison Carter (1):
      dt-bindings: leds: as3645: Convert to DT schema

Heiko Stuebner (2):
      leds: qnap-mcu: Fix state numbering for USB LED
      leds: qnap-mcu: Add support for the red and green status LEDs

Krzysztof Kozlowski (1):
      dt-bindings: leds: issi,is31fl319x: Drop 'db' suffix duplicating dtschema

Len Bao (1):
      leds: max77705: Function return instead of variable assignment

Pawel Zalewski (1):
      leds: leds-is31fl32xx: Add support for is31fl3236a

 .../devicetree/bindings/leds/ams,as3645a.txt       |  85 ----------
 .../devicetree/bindings/leds/ams,as3645a.yaml      | 130 +++++++++++++++
 .../bindings/leds/backlight/led-backlight.yaml     |   6 +-
 .../devicetree/bindings/leds/issi,is31fl319x.yaml  |   1 -
 .../devicetree/bindings/leds/leds-consumer.yaml    |  67 ++++++++
 .../bindings/leds/leds-group-multicolor.yaml       |   5 +-
 .../bindings/media/video-interface-devices.yaml    |   8 +
 drivers/leds/Kconfig                               |   2 +-
 drivers/leds/flash/leds-qcom-flash.c               |  87 ++++++----
 drivers/leds/led-class.c                           |  17 +-
 drivers/leds/leds-is31fl319x.c                     |   8 +-
 drivers/leds/leds-is31fl32xx.c                     |  47 +++++-
 drivers/leds/leds-lp55xx-common.c                  |   2 +-
 drivers/leds/leds-max77705.c                       |   2 +-
 drivers/leds/leds-qnap-mcu.c                       | 175 ++++++++++++++++++++-
 15 files changed, 497 insertions(+), 145 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/leds/ams,as3645a.txt
 create mode 100644 Documentation/devicetree/bindings/leds/ams,as3645a.yaml
 create mode 100644 Documentation/devicetree/bindings/leds/leds-consumer.yaml

-- 
Lee Jones [李琼斯]

             reply	other threads:[~2025-10-01 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-01 14:01 Lee Jones [this message]
2025-10-01 19:51 ` [GIT PULL] LEDs for v6.18 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=20251001140109.GV8757@google.com \
    --to=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.