linux-kernel - [RFC PATCH 0/1] leds: backlight: Register with class backlight

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <cover.1574692624.git.agx@sigxcpu.org>
Date:   Mon, 25 Nov 2019 15:47:57 +0100
From:   Guido Günther <agx@...xcpu.org>
To:     Jacek Anaszewski <jacek.anaszewski@...il.com>,
        Pavel Machek <pavel@....cz>, Dan Murphy <dmurphy@...com>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Enrico Weigelt <info@...ux.net>,
        Allison Randal <allison@...utok.net>,
        linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [RFC PATCH 0/1] leds: backlight: Register with class backlight

When using current LCD drivers as ledtrig backlight they're
not registered with the backlight device class. This has
two problems: they're usually not found by userspace since
these tools usually look in /sys/class/backlight and they
can't be used as backlight phandles in device tree for
e.g. LCD panels.

This is an RFC if this is worthwhile at all? A current problem
is that changing the LED brightness does currently not notify
the class backlight so they can get out of sync but i could
look into that if the approach makes sense.

Guido Günther (1):
  leds: backlight: register with class backlight too

 drivers/leds/trigger/ledtrig-backlight.c | 54 ++++++++++++++++++++++++
 1 file changed, 54 insertions(+)

-- 
2.23.0