On 29/09/2013 12:12, Bo Shen wrote:
> Hi Alexandre,
>
> On 9/28/2013 04:10, Alexandre Belloni wrote:
>> I found that disabling a pwm while it is at a low level will actually
>> put it
>> back at a high level. The main symptom is that leds-pwm is calling
>> pwm_disable()
>> after setting the duty
Hi Alexandre,
On 9/28/2013 04:10, Alexandre Belloni wrote:
I found that disabling a pwm while it is at a low level will actually put it
back at a high level. The main symptom is that leds-pwm is calling pwm_disable()
after setting the duty cycle to 0. Hence, instead of getting a switched off
Hi Alexandre,
On 9/28/2013 04:10, Alexandre Belloni wrote:
I found that disabling a pwm while it is at a low level will actually put it
back at a high level. The main symptom is that leds-pwm is calling pwm_disable()
after setting the duty cycle to 0. Hence, instead of getting a switched off
On 29/09/2013 12:12, Bo Shen wrote:
Hi Alexandre,
On 9/28/2013 04:10, Alexandre Belloni wrote:
I found that disabling a pwm while it is at a low level will actually
put it
back at a high level. The main symptom is that leds-pwm is calling
pwm_disable()
after setting the duty cycle to 0.
I found that disabling a pwm while it is at a low level will actually put it
back at a high level. The main symptom is that leds-pwm is calling pwm_disable()
after setting the duty cycle to 0. Hence, instead of getting a switched off LED,
you get an LED lit up at full brightness.
Solve that by
I found that disabling a pwm while it is at a low level will actually put it
back at a high level. The main symptom is that leds-pwm is calling pwm_disable()
after setting the duty cycle to 0. Hence, instead of getting a switched off LED,
you get an LED lit up at full brightness.
Solve that by
6 matches
Mail list logo
