Re: [PATCH] backlight: pwm_bl: disable PWM when 'duty_cycle' is zero

2016-06-07 Thread Tomi Valkeinen
On 07/06/16 09:49, Lothar Waßmann wrote: > Hi, > > On Mon, 6 Jun 2016 15:02:21 +0300 Tomi Valkeinen wrote: >> Hi, >> >> On 06/06/16 13:44, Lothar Waßmann wrote: >>> 'brightness' is usually an index into a table of duty_cycle values, >>> where the value at index 0 may well be non-zero >>> (tegra30-

Re: [PATCH] backlight: pwm_bl: disable PWM when 'duty_cycle' is zero

2016-06-06 Thread Lothar Waßmann
Hi, On Mon, 6 Jun 2016 15:02:21 +0300 Tomi Valkeinen wrote: > Hi, > > On 06/06/16 13:44, Lothar Waßmann wrote: > > 'brightness' is usually an index into a table of duty_cycle values, > > where the value at index 0 may well be non-zero > > (tegra30-apalis-eval.dts and tegra30-colibri-eval-v3.dts a

Re: [PATCH] backlight: pwm_bl: disable PWM when 'duty_cycle' is zero

2016-06-06 Thread Tomi Valkeinen
Hi, On 06/06/16 13:44, Lothar Waßmann wrote: > 'brightness' is usually an index into a table of duty_cycle values, > where the value at index 0 may well be non-zero > (tegra30-apalis-eval.dts and tegra30-colibri-eval-v3.dts are real-life > examples). > Thus brightness == 0 does not necessarily mea

[PATCH] backlight: pwm_bl: disable PWM when 'duty_cycle' is zero

2016-06-06 Thread Lothar Waßmann
'brightness' is usually an index into a table of duty_cycle values, where the value at index 0 may well be non-zero (tegra30-apalis-eval.dts and tegra30-colibri-eval-v3.dts are real-life examples). Thus brightness == 0 does not necessarily mean that the PWM output will be inactive. Check for 'duty_