public inbox for linux-fbdev@vger.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: linux-pwm@vger.kernel.org, linux-fbdev@vger.kernel.org,
	Adam Ford <aford173@gmail.com>,
	dri-devel@lists.freedesktop.org,
	Thierry Reding <thierry.reding@gmail.com>,
	kernel@pengutronix.de, Jingoo Han <jingoohan1@gmail.com>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH] backlight: pwm_bl: configure pwm only once per backlight toggle
Date: Thu, 17 Oct 2019 12:19:45 +0000	[thread overview]
Message-ID: <20191017121945.cmcvaffmbd7zydrm@pengutronix.de> (raw)
In-Reply-To: <20191017114727.fy5tg2kgi6mr2sei@holly.lan>

On Thu, Oct 17, 2019 at 12:47:27PM +0100, Daniel Thompson wrote:
> On Thu, Oct 17, 2019 at 10:10:59AM +0200, Uwe Kleine-König wrote:
> > A previous change in the pwm core (namely 01ccf903edd6 ("pwm: Let
> > pwm_get_state() return the last implemented state")) changed the
> > semantic of pwm_get_state() and disclosed an (as it seems) common
> > problem in lowlevel PWM drivers. By not relying on the period and duty
> > cycle being retrievable from a disabled PWM this type of problem is
> > worked around.
> > 
> > Apart from this issue only calling the pwm_get_state/pwm_apply_state
> > combo once is also more effective.
> 
> I'm only interested in the second paragraph here.
> 
> There seems to be a reasonable consensus that the i.MX27 and cros-ec
> PWM drivers should be fixed for the benefit of other PWM clients.
> So we make this change because it makes the pwm-bl better... not to
> work around bugs ;-).

That's fine, still I think it's fair to explain the motivation of
creating this patch.

> > diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
> > index 746eebc411df..ddebd62b3978 100644
> > --- a/drivers/video/backlight/pwm_bl.c
> > +++ b/drivers/video/backlight/pwm_bl.c
> > @@ -67,40 +62,27 @@ static void pwm_backlight_power_on(struct pwm_bl_data *pb)
> >  
> >  static void pwm_backlight_power_off(struct pwm_bl_data *pb)
> >  {
> > -	struct pwm_state state;
> > -
> > -	pwm_get_state(pb->pwm, &state);
> > -	if (!pb->enabled)
> > -		return;
> > -
> 
> Why remove the pb->enabled check? I thought that was there to ensure we
> don't mess up the regular reference counts.

I havn't looked yet, but I guess I have to respin. Expect a v2 later
today.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2019-10-17 12:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17  8:10 [PATCH] backlight: pwm_bl: configure pwm only once per backlight toggle Uwe Kleine-König
2019-10-17  9:48 ` Michal Vokáč
2019-10-17 10:11   ` Uwe Kleine-König
2019-10-17 11:11     ` Thierry Reding
2019-10-17 12:09       ` Uwe Kleine-König
2019-10-17 12:59         ` Thierry Reding
2019-10-17 13:58           ` Michal Vokáč
2019-10-17 15:14             ` Thierry Reding
2019-10-17 17:07               ` Adam Ford
2019-10-17 17:13                 ` Thierry Reding
2019-10-17 17:44                   ` Adam Ford
2019-10-18  9:36                     ` Michal Vokáč
2019-10-23 14:16                       ` Adam Ford
2019-10-23 14:23                         ` Fabio Estevam
2019-10-23 15:05                           ` Uwe Kleine-König
2019-10-17 20:25               ` Uwe Kleine-König
2019-10-17 19:44           ` Uwe Kleine-König
2019-10-17 13:30       ` Adam Ford
2019-10-17 13:59         ` Adam Ford
2019-10-17 10:59   ` Michal Vokáč
2019-10-17 20:19     ` Uwe Kleine-König
2019-10-17 11:47 ` Daniel Thompson
2019-10-17 12:19   ` Uwe Kleine-König [this message]
2019-10-17 12:34     ` Adam Ford
2019-10-17 12:40       ` Adam Ford
2019-10-17 13:05         ` Thierry Reding
2019-10-17 13:09           ` Adam Ford
2019-10-17 13:18     ` Daniel Thompson
2019-10-17 18:28       ` Uwe Kleine-König
2019-10-17 12:53 ` Adam Ford
2019-10-17 14:51 ` Adam Ford

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=20191017121945.cmcvaffmbd7zydrm@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=aford173@gmail.com \
    --cc=daniel.thompson@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=enric.balletbo@collabora.com \
    --cc=jingoohan1@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=lee.jones@linaro.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-pwm@vger.kernel.org \
    --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