From: Pavel Machek <pavel@ucw.cz>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Lee Jones <lee.jones@linaro.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <jacek.anaszewski@gmail.com>,
Heiko Stuebner <heiko@sntech.de>,
linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org, groeck@chromium.org,
linux-rockchip@lists.infradead.org, huang lin <hl@rock-chips.com>
Subject: Re: [PATCH v2 2/4] pwm-backlight: add support for pwm-delay-us property
Date: Thu, 06 Jul 2017 09:12:31 +0000 [thread overview]
Message-ID: <20170706091231.GA6741@amd> (raw)
In-Reply-To: <20170706080132.GL16144@ulmo.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 4228 bytes --]
On Thu 2017-07-06 10:01:32, Thierry Reding wrote:
> On Fri, Jun 30, 2017 at 01:21:07PM +0200, Enric Balletbo i Serra wrote:
> > From: huang lin <hl@rock-chips.com>
> >
> > Some panels (i.e. N116BGE-L41), in their power sequence specifications,
> > request a delay between set the PWM signal and enable the backlight and
> > between clear the PWM signal and disable the backlight. Add support for
> > the new pwm-delay-us property to meet the timing.
> >
> > Note that this patch inverts current sequence. Before this patch the
> > enable signal was set before the PWM signal and vice-versa on power off.
> >
> > I assumed that this sequence was wrong, at least it is on different panel
> > datasheets that I checked, so I inverted the sequence to follow:
> >
> > On power on, set the PWM signal, wait, and set the LED_EN signal.
> > On power off, clear the LED_EN signal, wait, and stop the PWM signal.
>
> I think this should be two separate patches to make it easier to revert
> the inverted sequence should it prove to regress on other panels.
Don't make this overly complex. This is trivial. No need to split it
into more patches.
> Two more comments below.
>
> > Signed-off-by: huang lin <hl@rock-chips.com>
> > Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> > ---
> > Changes since v1:
> > - As suggested by Daniel Thompson
> > - Do not assume power-on delay and power-off delay will be the same
> > - Move the check of dt property to the parse dt function.
> >
> > v1: https://lkml.org/lkml/2017/6/28/219
> >
> > drivers/video/backlight/pwm_bl.c | 24 ++++++++++++++++++++----
> > include/linux/pwm_backlight.h | 1 +
> > 2 files changed, 21 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
> > index 002f1ce..0f5470e 100644
> > --- a/drivers/video/backlight/pwm_bl.c
> > +++ b/drivers/video/backlight/pwm_bl.c
> > @@ -10,6 +10,7 @@
> > * published by the Free Software Foundation.
> > */
> >
> > +#include <linux/delay.h>
> > #include <linux/gpio/consumer.h>
> > #include <linux/gpio.h>
> > #include <linux/module.h>
> > @@ -35,6 +36,7 @@ struct pwm_bl_data {
> > struct gpio_desc *enable_gpio;
> > unsigned int scale;
> > bool legacy;
> > + unsigned int pwm_delay[2];
> > int (*notify)(struct device *,
> > int brightness);
> > void (*notify_after)(struct device *,
> > @@ -54,10 +56,14 @@ static void pwm_backlight_power_on(struct pwm_bl_data *pb, int brightness)
> > if (err < 0)
> > dev_err(pb->dev, "failed to enable power supply\n");
> >
> > + pwm_enable(pb->pwm);
> > +
> > + if (pb->pwm_delay[0])
> > + usleep_range(pb->pwm_delay[0], pb->pwm_delay[0] + 2000);
>
> 2000 us is kind of arbitrary. What if pwm_delay[0] is on the order of 20
> us? Making the delay 2 ms longer (in the worst case) seems somewhat
> excessive. Why not something like:
>
> usleep_range(pb->pwm_delay[0], pb->pwm_delay[0] * 2);
>
> ?
>
> > +
> > if (pb->enable_gpio)
> > gpiod_set_value_cansleep(pb->enable_gpio, 1);
> >
> > - pwm_enable(pb->pwm);
> > pb->enabled = true;
> > }
> >
> > @@ -66,12 +72,15 @@ static void pwm_backlight_power_off(struct pwm_bl_data *pb)
> > if (!pb->enabled)
> > return;
> >
> > - pwm_config(pb->pwm, 0, pb->period);
> > - pwm_disable(pb->pwm);
> > -
> > if (pb->enable_gpio)
> > gpiod_set_value_cansleep(pb->enable_gpio, 0);
> >
> > + if (pb->pwm_delay[1])
> > + usleep_range(pb->pwm_delay[1], pb->pwm_delay[1] + 2000);
> > +
> > + pwm_config(pb->pwm, 0, pb->period);
> > + pwm_disable(pb->pwm);
> > +
> > regulator_disable(pb->power_supply);
> > pb->enabled = false;
> > }
> > @@ -174,6 +183,12 @@ static int pwm_backlight_parse_dt(struct device *dev,
> > data->max_brightness--;
> > }
> >
> > + /* read pwm to enable pre/post delays from DT property */
>
> This comment is confusing. This isn't reading anything from the PWM.
>
> Thierry
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-07-06 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 11:21 [PATCH v2 1/4] dt-bindings: pwm-backlight: add pwm-delay-us property Enric Balletbo i Serra
[not found] ` <20170630112109.13785-1-enric.balletbo-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-06-30 11:21 ` [PATCH v2 2/4] pwm-backlight: add support for " Enric Balletbo i Serra
2017-07-06 8:01 ` Thierry Reding
2017-07-06 9:12 ` Pavel Machek [this message]
2017-07-06 9:17 ` Daniel Thompson
2017-07-06 9:24 ` Thierry Reding
2017-07-06 9:55 ` Pavel Machek
2017-07-06 9:57 ` Daniel Thompson
[not found] ` <20170630112109.13785-2-enric.balletbo-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2017-07-06 8:13 ` Thierry Reding
2017-07-06 8:26 ` Enric Balletbo Serra
2017-06-30 11:21 ` [PATCH v2 3/4] ARM: dts: rockchip: set pre/post " Enric Balletbo i Serra
2017-06-30 11:21 ` [PATCH v2 4/4] ARM: dts: rockchip: add pwm-delay-us backlight setting Enric Balletbo i Serra
2017-06-30 11:25 ` [PATCH v2 1/4] dt-bindings: pwm-backlight: add pwm-delay-us property Pavel Machek
2017-07-06 17:07 ` Rob Herring
2017-07-06 18:23 ` Enric Balletbo Serra
2017-07-13 7:22 ` Enric Balletbo Serra
2017-07-13 7:39 ` Pavel Machek
2017-07-13 7:49 ` Enric Balletbo Serra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170706091231.GA6741@amd \
--to=pavel@ucw.cz \
--cc=b.zolnierkie@samsung.com \
--cc=daniel.thompson@linaro.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=heiko@sntech.de \
--cc=hl@rock-chips.com \
--cc=jacek.anaszewski@gmail.com \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=rpurdie@rpsys.net \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).