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>,
	Daniel Thompson <danielt@kernel.org>
Subject: [GIT PULL] Backlight for v6.16
Date: Tue, 3 Jun 2025 11:02:34 +0100	[thread overview]
Message-ID: <20250603100234.GE7758@google.com> (raw)

Good morning Linus,

The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:

  Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git backlight-next-6.16

for you to fetch changes up to e12d3e1624a02706cdd3628bbf5668827214fa33:

  backlight: pm8941: Add NULL check in wled_configure() (2025-04-15 18:27:38 +0100)

----------------------------------------------------------------
Backlight for v6.16

  * Framebuffer Subsystem (fbdev):
    * The display's blanking status is now tracked in `struct fb_info`
    * `framebuffer_alloc()` initializes the blank state to `FB_BLANK_UNBLANK`
    * `register_framebuffer()` sets the state to `FB_BLANK_POWERDOWN` if an `fb_blank`
      callback exists, ensuring `FB_EVENT_BLANK` listeners correctly see the display
      being turned on during the first modeset
    * The `FB_EVENT_BLANK` event data now includes both the new and the old blank states
  * Qualcomm WLED Backlight:
    * Added a NULL check after `devm_kasprintf()` in `wled_configure()` to prevent a
      potential NULL pointer dereference if memory allocation fails

  * Framebuffer Subsystem (fbdev):
    * `fb_blank()` has been reworked to return early on errors, without functional
      changes, in preparation for further state tracking improvements
    * Fbdev now calls dedicated functions in the backlight subsystems to notify them
      of blank state changes, instead of relying on fbdev event notifiers
    * For LCDs, fbdev also calls a dedicated function to notify of mode changes
  * Backlight Subsystem:
    * Implemented fbdev blank state tracking using the (newly enhanced) blank state
      information provided directly by `FB_EVENT_BLANK`
    * Removed internal blank state tracking fields (`fb_bl_on`) from
      `struct backlight_device`
    * Moved the handling of blank-state updates into a separate internal helper
      function, `backlight_notify_blank()`
    * Removed support for fbdev events and replaced it with a dedicated function call
      interface (`backlight_notify_blank()` and `backlight_notify_blank_all()`) for
      display drivers to update backlight status
  * LCD Subsystem:
    * Moved the handling of display updates (blank events and mode changes) from
      fbdev event notifiers to separate internal helper functions (`lcd_notify_blank`,
      `lcd_notify_mode_change`)
    * Removed support for fbdev events and replaced it with dedicated function call
      interfaces (`lcd_notify_blank_all()`, `lcd_notify_mode_change_all()`)
    * The LCD subsystem now maintains its own internal list of LCD devices instead of
      relying on fbdev notifiers
  * LED Backlight Trigger:
    * Moved the handling of blank-state updates into a separate internal helper,
      `ledtrig_backlight_notify_blank()`
    * Removed support for fbdev events and replaced it with a dedicated function call,
      `ledtrig_backlight_blank()`, for fbdev to notify trigger of blank state changes
    * The LED backlight trigger now maintains its own internal list of triggers
      instead of relying on fbdev notifiers

  * Framebuffer Subsystem (fbdev):
    * Removed the definitions for the unused fbdev event constants
      `FB_EVENT_MODE_CHANGE` and `FB_EVENT_BLANK` from the header file

----------------------------------------------------------------
Henry Martin (1):
      backlight: pm8941: Add NULL check in wled_configure()

Thomas Zimmermann (11):
      fbdev: Rework fb_blank()
      fbdev: Track display blanking state
      fbdev: Send old blank state in FB_EVENT_BLANK
      backlight: Implement fbdev tracking with blank state from event
      backlight: Move blank-state handling into helper
      backlight: Replace fb events with a dedicated function call
      backlight: lcd: Move event handling into helpers
      backlight: lcd: Replace fb events with a dedicated function call
      leds: backlight trigger: Move blank-state handling into helper
      leds: backlight trigger: Replace fb events with a dedicated function call
      fbdev: Remove constants of unused events

 drivers/leds/trigger/ledtrig-backlight.c |  48 +++++++-------
 drivers/video/backlight/backlight.c      |  93 ++++++--------------------
 drivers/video/backlight/lcd.c            | 108 ++++++++++++-------------------
 drivers/video/backlight/qcom-wled.c      |   6 +-
 drivers/video/fbdev/core/fb_backlight.c  |  12 ++++
 drivers/video/fbdev/core/fb_info.c       |   1 +
 drivers/video/fbdev/core/fbmem.c         |  82 +++++++++++++++++++----
 drivers/video/fbdev/core/fbsysfs.c       |   8 +--
 include/linux/backlight.h                |  32 ++++-----
 include/linux/fb.h                       |  12 ++--
 include/linux/lcd.h                      |  21 +++++-
 include/linux/leds.h                     |   6 ++
 12 files changed, 219 insertions(+), 210 deletions(-)

-- 
Lee Jones [李琼斯]

             reply	other threads:[~2025-06-03 10:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 10:02 Lee Jones [this message]
2025-06-03 20:09 ` [GIT PULL] Backlight for v6.16 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=20250603100234.GE7758@google.com \
    --to=lee@kernel.org \
    --cc=danielt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.