From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: linux-leds@vger.kernel.org
Subject: Re: [PATCH v4 1/4] leds: core: add generic support for RGB Color LED's
Date: Fri, 26 Feb 2016 21:58:51 +0100 [thread overview]
Message-ID: <56D0BC8B.6010205@gmail.com> (raw)
In-Reply-To: <56D02F35.4000008@samsung.com>
Am 26.02.2016 um 11:55 schrieb Jacek Anaszewski:
> On 02/26/2016 11:20 AM, Heiner Kallweit wrote:
>> On Fri, Feb 26, 2016 at 11:03 AM, Jacek Anaszewski
>> <j.anaszewski@samsung.com> wrote:
>>> Hi Heiner,
>>>
>>> I don't see [PATCH v4 2/4]. Have you sent it?
>>>
>> Patch 2 of series wasn't changed since v3. Therefore I didn't resend it.
>> Do you prefer to always get the full series even if particular patches
>> weren't changed?
>
> You set the total number of patches in the patch set to 4,
> so not having one of the patches in the middle looks odd.
> Yes, for better readability and consistency I prefer to include
> all patches to the set even if there are no difference in
> comparison to the previous version.
>
> Of course, if only one of e.g. five patches is to be modified
> then sending the only one suffices, let's just use common sense.
>
> Note, that I don't expect that you sent the missing one now.
>
OK, thanks for explaining.
During further testing I figured out that there is a need to send a v4
of patch 2. I was wrong in how the printf format string is interpreted.
To display 6 digits I need to set precision instead of width.
>>> On 02/25/2016 11:11 PM, Heiner Kallweit wrote:
>>>>
>>>> Add generic support for RGB Color LED's.
>>>>
>>>> Basic idea is to use enum led_brightness also for the hue and saturation
>>>> color components.This allows to implement the color extension w/o
>>>> changes to struct led_classdev.
>>>>
>>>> Select LEDS_RGB to enable building drivers using the RGB extension.
>>>>
>>>> Flag LED_SET_HUE_SAT 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 hex notation can be used)
>>>>
>>>> 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)
>>>>
>>>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>
>
>
next prev parent reply other threads:[~2016-02-26 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 22:11 [PATCH v4 1/4] leds: core: add generic support for RGB Color LED's Heiner Kallweit
2016-02-26 10:03 ` Jacek Anaszewski
2016-02-26 10:20 ` Heiner Kallweit
2016-02-26 10:55 ` Jacek Anaszewski
2016-02-26 20:58 ` Heiner Kallweit [this message]
2016-02-29 16:12 ` Jacek Anaszewski
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=56D0BC8B.6010205@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).