From: Daniel Thompson <daniel.thompson@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
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 13:18:02 +0000 [thread overview]
Message-ID: <20191017131802.defwuzrgq4ai4mud@holly.lan> (raw)
In-Reply-To: <20191017121945.cmcvaffmbd7zydrm@pengutronix.de>
On Thu, Oct 17, 2019 at 02:19:45PM +0200, Uwe Kleine-König wrote:
> 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.
Maybe.
Whether this patch is a workaround or simply an improvement to pwm-bl
does need to be clear since it affects whether Lee steers it towards
v5.4-rcX or linux-next .
Daniel.
next prev parent reply other threads:[~2019-10-17 13:18 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
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 [this message]
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=20191017131802.defwuzrgq4ai4mud@holly.lan \
--to=daniel.thompson@linaro.org \
--cc=aford173@gmail.com \
--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 \
--cc=u.kleine-koenig@pengutronix.de \
/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