Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935850AbdGTKDq (ORCPT ); Thu, 20 Jul 2017 06:03:46 -0400 Received: from mail-io0-f195.google.com ([209.85.223.195]:36655 "EHLO mail-io0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933887AbdGTKDm (ORCPT ); Thu, 20 Jul 2017 06:03:42 -0400 MIME-Version: 1.0 In-Reply-To: <20170720081038.GD13103@amd> References: <20170717212811.25374-1-enric.balletbo@collabora.com> <20170717212811.25374-5-enric.balletbo@collabora.com> <20170720081038.GD13103@amd> From: Enric Balletbo Serra Date: Thu, 20 Jul 2017 12:03:40 +0200 Message-ID: Subject: Re: [PATCH v3 5/5] ARM: dts: rockchip: set PWM delay backlight settings for Minnie To: Pavel Machek Cc: Enric Balletbo i Serra , Thierry Reding , Lee Jones , Daniel Thompson , Jingoo Han , Bartlomiej Zolnierkiewicz , Rob Herring , Richard Purdie , Jacek Anaszewski , Heiko Stuebner , Linux PWM List , linux-fbdev@vger.kernel.org, linux-kernel , Guenter Roeck , "open list:ARM/Rockchip SoC..." Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1533 Lines: 47 Pavel, 2017-07-20 10:10 GMT+02:00 Pavel Machek : > On Mon 2017-07-17 23:28:11, Enric Balletbo i Serra wrote: >> The minnie devices comes with an AUO B101EAN01 panel which is different >> from default veyron devices, thus the power on/off timing sequence is >> slightly different. The datasheet specifies a pwm delay of 200 ms, so >> update the PMW delay proprieties accordingly. > > Wait a wait a moment! > >> --- a/arch/arm/boot/dts/rk3288-veyron-minnie.dts >> +++ b/arch/arm/boot/dts/rk3288-veyron-minnie.dts >> @@ -123,6 +123,8 @@ >> 240 241 242 243 244 245 246 247 >> 248 249 250 251 252 253 254 255>; >> power-supply = <&backlight_regulator>; >> + post-pwm-on-delay-us = <20000>; > > -us = <20 000>; > > This is not 200 msec. > Oops, good catch. > Plus, it is quite anti-social to do udelay(200 000). > > Plus, it is very anti-socifal to use udelay_range(200msec, > 400msec). > > Whoever told you udelay_range is good thing to use -- it is not, and > it is certainly not worth making user wait 200msec more! > Checked again some datasheets and seems that or not require a delay or the delays are 10ms+, so according to [1] I'll use msleep instead. [1] https://www.kernel.org/doc/Documentation/timers/timers-howto.txt Thanks, Enric > Pavel > -- > (english) http://www.livejournal.com/~pavelmachek > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html