Linux LED subsystem development
 help / color / mirror / Atom feed
From: Simona Vetter <simona.vetter@ffwll.ch>
To: Lee Jones <lee@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
	pavel@ucw.cz, danielt@kernel.org, jingoohan1@gmail.com,
	deller@gmx.de, simona@ffwll.ch, linux-leds@vger.kernel.org,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH v3 00/11] backlight, lcd, led: Remove fbdev dependencies
Date: Fri, 14 Mar 2025 09:39:59 +0100	[thread overview]
Message-ID: <Z9PrX6Qz4io3M9xs@phenom.ffwll.local> (raw)
In-Reply-To: <20250313165151.GE3645863@google.com>

On Thu, Mar 13, 2025 at 04:51:51PM +0000, Lee Jones wrote:
> On Thu, 06 Mar 2025, Thomas Zimmermann wrote:
> 
> > 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.
> > 
> > v3:
> > - export several symbols
> > - static-inline declare empty placeholders
> > v2:
> > - avoid IS_REACHABLE() in source file (Lee)
> > - simplify several interfaces and helpers
> > - use lock guards
> > - initialize global lists and mutices
> > 
> > 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/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, 205 insertions(+), 208 deletions(-)
> 
> No immediately obvious issues from the LEDs side.
> 
> Still needs reviews from Backlight and fbdev.

I looked throught the series and it's a small step, but I think it's the
right direction for where we want backlight/fbdev/drm-kms to head towards
long-term. So on the series:

Acked-by: Simona Vetter <simona.vetter@ffwll.ch>

Cheers, Sima

> 
> -- 
> Lee Jones [李琼斯]

-- 
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2025-03-14  8:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 14:05 [PATCH v3 00/11] backlight, lcd, led: Remove fbdev dependencies Thomas Zimmermann
2025-03-06 14:05 ` [PATCH v3 01/11] fbdev: Rework fb_blank() Thomas Zimmermann
2025-03-06 14:05 ` [PATCH v3 02/11] fbdev: Track display blanking state Thomas Zimmermann
2025-03-06 14:05 ` [PATCH v3 03/11] fbdev: Send old blank state in FB_EVENT_BLANK Thomas Zimmermann
2025-03-06 14:05 ` [PATCH v3 04/11] backlight: Implement fbdev tracking with blank state from event Thomas Zimmermann
2025-03-18  9:05   ` Daniel Thompson
2025-03-06 14:05 ` [PATCH v3 05/11] backlight: Move blank-state handling into helper Thomas Zimmermann
2025-03-18  9:07   ` Daniel Thompson
2025-03-06 14:05 ` [PATCH v3 06/11] backlight: Replace fb events with a dedicated function call Thomas Zimmermann
2025-03-08 11:31   ` kernel test robot
2025-03-08 11:31   ` kernel test robot
2025-03-18  9:23   ` Daniel Thompson
2025-03-21  8:13     ` Thomas Zimmermann
2025-03-06 14:05 ` [PATCH v3 07/11] backlight: lcd: Move event handling into helpers Thomas Zimmermann
2025-03-18  9:25   ` Daniel Thompson
2025-03-06 14:05 ` [PATCH v3 08/11] backlight: lcd: Replace fb events with a dedicated function call Thomas Zimmermann
2025-03-18  9:40   ` Daniel Thompson
2025-03-21  8:16     ` Thomas Zimmermann
2025-03-06 14:05 ` [PATCH v3 09/11] leds: backlight trigger: Move blank-state handling into helper Thomas Zimmermann
2025-03-06 14:05 ` [PATCH v3 10/11] leds: backlight trigger: Replace fb events with a dedicated function call Thomas Zimmermann
2025-03-06 14:05 ` [PATCH v3 11/11] fbdev: Remove constants of unused events Thomas Zimmermann
2025-03-13 16:51 ` [PATCH v3 00/11] backlight, lcd, led: Remove fbdev dependencies Lee Jones
2025-03-14  8:39   ` Simona Vetter [this message]
2025-03-17  8:42   ` Thomas Zimmermann
2025-03-17 17:14     ` Daniel Thompson

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=Z9PrX6Qz4io3M9xs@phenom.ffwll.local \
    --to=simona.vetter@ffwll.ch \
    --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 \
    --cc=tzimmermann@suse.de \
    /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