linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: linux-leds@vger.kernel.org
Subject: [PATCH 0/2] leds: core: add support for color LED's
Date: Sun, 7 Feb 2016 01:37:48 +0100	[thread overview]
Message-ID: <56B691DC.3020906@gmail.com> (raw)

This patchset adds support for color LED's. In addition to RGB LED's
also LED's with native HSV are implicitely supported (although I know
no such devices).

Basic idea is to use enum led_brightness also for the hue and saturation
color component.
Flag LED_BRIGHTNESS_SET_COLOR BIT(24) allows to specify that hue / saturation
should be overridden even if the provided values are zero.

Some examples for writing values to /sys/class/leds/<xx>/brightness:
(now also values in hex notation can be provided)

255 -> set full brightness and keep existing color if set
0 -> switch LED off but keep existing color so that it can be restored if the
     LED is switched on again later
0x1000000 -> switch LED off and set also hue and saturation to 0
0x00ffff -> set full brightness, full saturation and set hue to 0 (red)

Heiner Kallweit (2):
  leds: core: add generic support for color LED's
  leds: core: add support for RGB LED's

 drivers/leds/led-class.c | 10 ++++--
 drivers/leds/led-core.c  | 89 +++++++++++++++++++++++++++++++++++++++++++-----
 include/linux/leds.h     |  5 +++
 3 files changed, 94 insertions(+), 10 deletions(-)

-- 
2.7.0

             reply	other threads:[~2016-02-07 10:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07  0:37 Heiner Kallweit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-02-07 10:05 [PATCH 0/2] leds: core: add support for color LED's Heiner Kallweit

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=56B691DC.3020906@gmail.com \
    --to=hkallweit1@gmail.com \
    --cc=j.anaszewski@samsung.com \
    --cc=linux-leds@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).