From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: linux-leds@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v7 4/5] leds: core: document ABI change for RGB extension
Date: Fri, 4 Mar 2016 22:14:42 +0100 [thread overview]
Message-ID: <56D9FAC2.8090703@gmail.com> (raw)
Document the ABI change in Documentation/ABI/testing/sysfs-class-led.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
v7:
- separated from patch 3
---
Documentation/ABI/testing/sysfs-class-led | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-class-led b/Documentation/ABI/testing/sysfs-class-led
index 3646ec8..20357d5 100644
--- a/Documentation/ABI/testing/sysfs-class-led
+++ b/Documentation/ABI/testing/sysfs-class-led
@@ -7,6 +7,17 @@ Description:
have hardware brightness support so will just be turned on for
non-zero brightness settings. The value is between 0 and
/sys/class/leds/<led>/max_brightness.
+ If a driver uses the RGB LED feature then this attribute is
+ interpreted as a HSV color model value:
+ <0000000F><HHHHHHHH><SSSSSSSS><VVVVVVVV>
+ Usage of the least byte is identical to monochrome mode.
+ Saturation can be 0-255 and hue 0-251 (Colour circle is mapped
+ to 0-252). If hue and saturation both are 0 the current colour
+ is preserved and only the brightness is set. This ensures
+ backwards compatibility with monochrome mode, e.g. for
+ led_set_brightness() calls from triggers.
+ Flag F enables setting hue and saturation even if both are 0.
+ For details and examples see Documentation/leds/leds-class.txt
What: /sys/class/leds/<led>/max_brightness
Date: March 2006
--
2.7.1
reply other threads:[~2016-03-04 21:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56D9FAC2.8090703@gmail.com \
--to=hkallweit1@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-usb@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).