linux-kernel - Re: [PATCH v4 2/2] leds: rt5033: Add RT5033 Flash led device driver

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-prev] [day] [month] [year] [list]

Date:	Thu, 12 Nov 2015 19:07:33 +0900
From:	Ingi Kim <ingi2.kim@...sung.com>
To:	Jacek Anaszewski <jacek.anaszewski@...il.com>,
	Jacek Anaszewski <j.anaszewski@...sung.com>
Cc:	robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	sameo@...ux.intel.com, lee.jones@...aro.org, rpurdie@...ys.net,
	inki.dae@...sung.com, sw0312.kim@...sung.com,
	beomho.seo@...sung.com, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-leds@...r.kernel.org
Subject: Re: [PATCH v4 2/2] leds: rt5033: Add RT5033 Flash led device driver

Hi Jacek,

On 2015년 11월 12일 18:21, Jacek Anaszewski wrote:
> Hi Ingi,
> 
> On 11/12/2015 08:57 AM, Ingi Kim wrote:
> [...]
>>>> +        regmap_write(led->regmap, RT5033_REG_FLED_FUNCTION1, val);
>>>> +    } else {
>>>> +        regmap_update_bits(led->regmap, RT5033_REG_FLED_FUNCTION1,
>>>> +                   RT5033_FLED_FUNC1_MASK, RT5033_FLED_PINCTRL |
>>>> +                   rt5033_fled_used(led, fled_id));
>>>> +        regmap_update_bits(led->regmap,    RT5033_REG_FLED_CTRL1,
>>>> +                   RT5033_FLED_CTRL1_MASK,
>>>> +                   (brightness - 1) << 4);
>>>> +        regmap_update_bits(led->regmap, RT5033_REG_FLED_FUNCTION2,
>>>> +                   RT5033_FLED_FUNC2_MASK, RT5033_FLED_ENFLED);
>>>> +    }
>>>
>>> How are you distinguishing between setting brightness for iout_joint
>>> case and for individual LEDs? Have you tested this use case?
>>> Even if you don't have a board with two separate LEDs,
>>> you should be able to test two LED class devices with a single
>>> connected LED.
>>>
>>
>> Thanks, I missed a iout_joint case :(
>> I have tested a board with integrated single LED,
>> It looks fine and all feature works well even if it has limitation.
> 
> Please also test two separate LEDs case, by defining two child
> nodes in DT, and in a result you will get two LED class devices.
> After that you can set brightness separately for each LED class
> device, and you'll be able to verify that the driver works properly
> by observing the single LED connected to both outputs.
> In order to make the testing even more valuable, you can
> set triggers for both LEDs
> 

Oh, I ask of you, please do not misconstrue.
I'm sorry if my expression is rather misleading.

I have verified this driver works properly.
It already tested with two child nodes and observed single LED
that is connected to both outputs.

I just wanted to say that it works properly as you said.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/