# Re: \[PATCH\] backlight: pwm\_bl: disable PWM when 'duty\_cycle' is zero

- From: Tomi Valkeinen \<hidden\>
- Date: 2016-06-06 12:02:40 
- List: linux-fbdev
- Page: https://ratatoskr.run/linux-fbdev/2016/06/4765982
- Thread: https://ratatoskr.run/linux-fbdev/2016/06/4765908/t.md

```text
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 mean that the PWM output
> will be inactive.
> Check for 'duty_cycle == 0' rather than 'brightness == 0' to decide
> whether to disable the PWM.

The binding doc does say:

  - brightness-levels: Array of distinct brightness levels. Typically these
      are in the range from 0 to 255, but any range starting at 0 will do.
      The actual brightness level (PWM duty cycle) will be interpolated
      from these values. 0 means a 0% duty cycle (darkest/off), while the
      last value in the array represents a 100% duty cycle (brightest).

 Tomi

```

## Attachments

- [signature.asc](https://ratatoskr.run/linux-fbdev/2016/06/4765982/attachment/0) (application/pgp-signature, 819 bytes)
