On 12/04/2012 06:34 PM, Bryan Wu wrote:
> What's best thing I can do is I can merge these patchset into my
> -devel branch, after 3.8 merge window close I will move this -devel
> branch to my for-next branch for 3.9 merge window.
>
> Does this make sense to you?
Not sure if I can get changes rela
On Tue, Dec 4, 2012 at 12:11 AM, Peter Ujfalusi wrote:
> Hi Bryan,
>
> On 12/03/2012 07:32 PM, Bryan Wu wrote:
>> On Mon, Dec 3, 2012 at 6:13 AM, Peter Ujfalusi wrote:
>> Actually, I'm waiting for some feedback from DT maintainers about this
>> new binding. But it looks find to me.
>
> Would it b
Hi Bryan,
On 12/03/2012 07:32 PM, Bryan Wu wrote:
> On Mon, Dec 3, 2012 at 6:13 AM, Peter Ujfalusi wrote:
> Actually, I'm waiting for some feedback from DT maintainers about this
> new binding. But it looks find to me.
Would it be possible to have the first (or even better the first two) patch
g
On Mon, Dec 3, 2012 at 6:13 AM, Peter Ujfalusi wrote:
> Hi Bryan,
>
> On 11/14/2012 02:14 AM, Bryan Wu wrote:
>> On Mon, Nov 12, 2012 at 6:41 AM, Peter Ujfalusi
>> wrote:
>>> Update the driver to use the new API for requesting pwm so we can take
>>> advantage of the pwm_lookup table to find the
Hi Bryan,
On 11/14/2012 02:14 AM, Bryan Wu wrote:
> On Mon, Nov 12, 2012 at 6:41 AM, Peter Ujfalusi wrote:
>> Update the driver to use the new API for requesting pwm so we can take
>> advantage of the pwm_lookup table to find the correct pwm to be used for the
>> LED functionality.
>> If the devm
On Mon, Nov 12, 2012 at 6:41 AM, Peter Ujfalusi wrote:
> Update the driver to use the new API for requesting pwm so we can take
> advantage of the pwm_lookup table to find the correct pwm to be used for the
> LED functionality.
> If the devm_get_pwm fails we fall back to legacy mode to try to get
Hi Bryan,
On 11/14/2012 02:14 AM, Bryan Wu wrote:
>> diff --git a/include/linux/leds_pwm.h b/include/linux/leds_pwm.h
>> index 33a0711..a65e964 100644
>> --- a/include/linux/leds_pwm.h
>> +++ b/include/linux/leds_pwm.h
>> @@ -7,7 +7,7 @@
>> struct led_pwm {
>> const char *name;
>>
Update the driver to use the new API for requesting pwm so we can take
advantage of the pwm_lookup table to find the correct pwm to be used for the
LED functionality.
If the devm_get_pwm fails we fall back to legacy mode to try to get the pwm.
Signed-off-by: Peter Ujfalusi
---
drivers/leds/leds-