From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Herring Subject: Re: [PATCHv2] backlight: pwm_bl: disable PWM when 'duty_cycle' is zero Date: Wed, 8 Jun 2016 15:06:43 -0500 Message-ID: <20160608200643.GA13510@rob-hp-laptop> References: <1465294429-8570-1-git-send-email-LW@KARO-electronics.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: <1465294429-8570-1-git-send-email-LW@KARO-electronics.de> Sender: linux-kernel-owner@vger.kernel.org To: Lothar =?iso-8859-1?Q?Wa=DFmann?= Cc: Jean-Christophe Plagniol-Villard , Jingoo Han , Lee Jones , Thierry Reding , Tomi Valkeinen , linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org, Marcel Ziswiler , Ian Campbell , Kumar Gala , Mark Rutland , Pawel Moll , devicetree@vger.kernel.org List-Id: devicetree@vger.kernel.org On Tue, Jun 07, 2016 at 12:13:49PM +0200, Lothar Wa=DFmann 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-lif= e > examples). > Thus brightness =3D=3D 0 does not necessarily mean that the PWM outpu= t > will be inactive. > Check for 'duty_cycle =3D=3D 0' rather than 'brightness =3D=3D 0' to = decide > whether to disable the PWM. >=20 > Signed-off-by: Lothar Wa=DFmann > --- > Changes wrt. v1: > - update binding docs to reflect the change >=20 > .../devicetree/bindings/leds/backlight/pwm-backlight.txt | 9= ++++++--- > drivers/video/backlight/pwm_bl.c | 4= ++-- > 2 files changed, 8 insertions(+), 5 deletions(-) Acked-by: Rob Herring