From: "Pali Rohár" <pali.rohar@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Pavel Machek <pavel@ucw.cz>, Darren Hart <dvhart@infradead.org>,
Henrique de Moraes Holschuh <ibm-acpi@hmh.eng.br>,
linux-leds@vger.kernel.org, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v6 1/4] leds: class: Add new optional brightness_hw_changed attribute
Date: Wed, 25 Jan 2017 17:49:36 +0100 [thread overview]
Message-ID: <20170125164936.GE7936@pali> (raw)
In-Reply-To: <20170125161130.5424-2-hdegoede@redhat.com>
On Wednesday 25 January 2017 17:11:27 Hans de Goede wrote:
> Some LEDs may have their brightness level changed autonomously
> (outside of kernel control) by hardware / firmware. This commit
> adds support for an optional brightness_hw_changed attribute to
> signal such changes to userspace (if a driver can detect them):
>
> What: /sys/class/leds/<led>/brightness_hw_changed
> Date: January 2017
> KernelVersion: 4.11
> Description:
> Last hardware set brightness level for this LED. Some LEDs
> may be changed autonomously by hardware/firmware. Only LEDs
> where this happens and the driver can detect this, will
> have this file.
>
> This file supports poll() to detect when the hardware
> changes the brightness.
>
> Reading this file will return the last brightness level set
> by the hardware, this may be different from the current
> brightness.
>
> Drivers which want to support this, simply add LED_BRIGHT_HW_CHANGED to
> their flags field and call led_classdev_notify_brightness_hw_changed()
> with the hardware set brightness when they detect a hardware / firmware
> triggered brightness change.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Just speculation: What about using name 'actual_brightness'? It provides
same output on read as actual_brightness from /sys/class/backlight/.
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2017-01-25 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 16:11 [PATCH v6 1/4] leds: class: Add new optional brightness_hw_changed Hans de Goede
2017-01-25 16:11 ` [PATCH v6 1/4] leds: class: Add new optional brightness_hw_changed attribute Hans de Goede
2017-01-25 16:49 ` Pali Rohár [this message]
2017-01-25 21:35 ` Jacek Anaszewski
2017-01-26 8:33 ` Pali Rohár
2017-01-26 19:51 ` Jacek Anaszewski
2017-01-26 20:04 ` Jacek Anaszewski
2017-01-27 7:38 ` Hans de Goede
2017-01-25 21:35 ` Jacek Anaszewski
2017-01-26 21:12 ` Pavel Machek
2017-01-27 7:40 ` Hans de Goede
2017-01-25 16:11 ` [PATCH v6 2/4] platform/x86/thinkpad: Call led_classdev_notify_brightness_hw_changed on kbd brightness change Hans de Goede
2017-01-28 13:36 ` Andy Shevchenko
2017-01-28 15:34 ` Hans de Goede
2017-01-25 16:11 ` [PATCH v6 3/4] platform/x86/dell-*: Add a generic dell-laptop notifier chain Hans de Goede
2017-01-25 16:11 ` [PATCH v6 4/4] platform/x86/dell-*: Call led_classdev_notify_brightness_hw_changed on kbd brightness change Hans de Goede
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=20170125164936.GE7936@pali \
--to=pali.rohar@gmail.com \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=ibm-acpi@hmh.eng.br \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=platform-driver-x86@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).