From: Thomas Zimmermann <tzimmermann@suse.de>
To: lee@kernel.org, pavel@ucw.cz, danielt@kernel.org,
jingoohan1@gmail.com, deller@gmx.de, simona@ffwll.ch
Cc: linux-leds@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: [PATCH v2 00/11] backlight, lcd, led: Remove fbdev dependencies
Date: Wed, 26 Feb 2025 10:31:49 +0100 [thread overview]
Message-ID: <20250226093456.147402-1-tzimmermann@suse.de> (raw)
This series removes the remaining dependencies on fbdev from the
backlight, lcd and led subsystems. Each depends on fbdev events to
track display state. Make fbdev inform each subsystem via a dedicated
interface instead.
Patches 1 to 3 make fbdev track blank state for each display, so that
backlight code doesn't have to.
Patches 4 to 6 remove fbdev event handling from backlight code. Patches
7 and 8 remove fbdev event handling from lcd code and patches 9 and 10
do the same for led's backlight trigger.
The final patch removes the event constants from fbdev.
With the series applied, the three subsystems do no longer depend on
fbdev. It's also a clean up for fbdev. Fbdev used to send out a large
number of events. That mechanism has been deprecated for some time and
converted call to dedicated functions instead.
Testing is very welcome, as I don't have the hardware to test this
series.
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 | 47 +++++-----
drivers/video/backlight/backlight.c | 93 +++++---------------
drivers/video/backlight/lcd.c | 107 +++++++++--------------
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 | 22 ++---
include/linux/fb.h | 12 +--
include/linux/lcd.h | 21 ++++-
include/linux/leds.h | 6 ++
11 files changed, 203 insertions(+), 208 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-26 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 9:31 Thomas Zimmermann [this message]
2025-02-26 9:31 ` [PATCH v2 01/11] fbdev: Rework fb_blank() Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 02/11] fbdev: Track display blanking state Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 03/11] fbdev: Send old blank state in FB_EVENT_BLANK Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 04/11] backlight: Implement fbdev tracking with blank state from event Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 05/11] backlight: Move blank-state handling into helper Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 06/11] backlight: Replace fb events with a dedicated function call Thomas Zimmermann
2025-02-27 11:42 ` kernel test robot
2025-02-27 12:46 ` kernel test robot
2025-02-26 9:31 ` [PATCH v2 07/11] backlight: lcd: Move event handling into helpers Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 08/11] backlight: lcd: Replace fb events with a dedicated function call Thomas Zimmermann
2025-02-27 15:07 ` kernel test robot
2025-02-26 9:31 ` [PATCH v2 09/11] leds: backlight trigger: Move blank-state handling into helper Thomas Zimmermann
2025-02-26 9:31 ` [PATCH v2 10/11] leds: backlight trigger: Replace fb events with a dedicated function call Thomas Zimmermann
2025-02-26 9:32 ` [PATCH v2 11/11] fbdev: Remove constants of unused events Thomas Zimmermann
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=20250226093456.147402-1-tzimmermann@suse.de \
--to=tzimmermann@suse.de \
--cc=danielt@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=lee@kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=simona@ffwll.ch \
/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