Linux LED subsystem development
 help / color / mirror / Atom feed
From: Daniel Thompson <danielt@kernel.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: lee@kernel.org, pavel@ucw.cz, 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 04/11] backlight: Implement fbdev tracking with blank state from event
Date: Tue, 18 Mar 2025 09:05:39 +0000	[thread overview]
Message-ID: <Z9k3YxOy26OyFnbS@aspen.lan> (raw)
In-Reply-To: <20250306140947.580324-5-tzimmermann@suse.de>

On Thu, Mar 06, 2025 at 03:05:46PM +0100, Thomas Zimmermann wrote:
> Look at the blank state provided by FB_EVENT_BLANK to determine
> whether to enable or disable a backlight. Remove the tracking fields
> from struct backlight_device.
>
> Tracking requires three variables, fb_on, prev_fb_on and the
> backlight's use_count. If fb_on is true, the display has been
> unblanked. The backlight needs to be enabled if the display was
> blanked before (i.e., prev_fb_on is false) or if use_count is still
> at 0. If fb_on is false, the display has been blanked. In this case,
> the backlight has to be disabled was unblanked before and the
> backlight's use_count is greater than 0.
>
> This change removes fbdev state tracking from blacklight. All the
> backlight requires it its own use counter and information about
> changes to the display. Removing fbdev internals makes  backlight
> drivers easier to integrate into other display drivers, such as DRM.
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>

Reviewed-by: Daniel Thompson (RISCstar) <danielt@kernel.org>


Daniel.

  reply	other threads:[~2025-03-18  9:05 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 [this message]
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
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=Z9k3YxOy26OyFnbS@aspen.lan \
    --to=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