From: "Heiko Stübner" <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Simon South <simon@simonsouth.net>
Cc: Simon South <simon@simonsouth.net>
Subject: Re: [PATCH] pwm: rockchip: Keep enabled PWMs running while probing
Date: Sat, 19 Sep 2020 10:35:20 +0200 [thread overview]
Message-ID: <5907731.26MhtTZbrF@diego> (raw)
In-Reply-To: <20200918204825.4744-1-simon@simonsouth.net>
Hi Simon,
Am Freitag, 18. September 2020, 22:48:25 CEST schrieb Simon South:
> Following commit cfc4c189bc70 ("pwm: Read initial hardware state at
> request time") the Rockchip PWM driver can no longer assume a device's
> pwm_state structure has been populated after a call to pwmchip_add().
> Consequently, the test in rockchip_pwm_probe() intended to prevent the
> driver from stopping PWM devices already enabled by the bootloader no
> longer functions reliably and this can lead to the kernel hanging
> during startup, particularly on devices like the Pinebook Pro that use
> a PWM-controlled backlight for their display.
>
> Avoid this by querying the device directly at probe time to determine
> whether or not it is enabled.
>
> Signed-off-by: Simon South <simon@simonsouth.net>
On first glance this looks like a good catch but there is a bit of
housekeeping missing.
The patch should get a fixes tag like
Fixes: cfc4c189bc70 ("pwm: Read initial hardware state at request time")
Can you resend the patch and include relevant other parties like you get
from 'scripts/get_maintainer.pl -f drivers/pwm/pwm-rockchip.c' like
Thierry Reding <thierry.reding@gmail.com> (maintainer:PWM SUBSYSTEM)
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de> (reviewer:PWM SUBSYSTEM)
Lee Jones <lee.jones@linaro.org> (maintainer:PWM SUBSYSTEM)
linux-pwm@vger.kernel.org (open list:PWM SUBSYSTEM)
Thanks
Heiko
> ---
> drivers/pwm/pwm-rockchip.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pwm/pwm-rockchip.c b/drivers/pwm/pwm-rockchip.c
> index eb8c9cb645a6..098e94335cb5 100644
> --- a/drivers/pwm/pwm-rockchip.c
> +++ b/drivers/pwm/pwm-rockchip.c
> @@ -288,6 +288,7 @@ static int rockchip_pwm_probe(struct platform_device *pdev)
> const struct of_device_id *id;
> struct rockchip_pwm_chip *pc;
> struct resource *r;
> + u32 enable_conf, ctrl;
> int ret, count;
>
> id = of_match_device(rockchip_pwm_dt_ids, &pdev->dev);
> @@ -362,7 +363,9 @@ static int rockchip_pwm_probe(struct platform_device *pdev)
> }
>
> /* Keep the PWM clk enabled if the PWM appears to be up and running. */
> - if (!pwm_is_enabled(pc->chip.pwms))
> + enable_conf = pc->data->enable_conf;
> + ctrl = readl_relaxed(pc->base + pc->data->regs.ctrl);
> + if ((ctrl & enable_conf) != enable_conf)
> clk_disable(pc->clk);
>
> return 0;
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-19 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 20:48 [PATCH] pwm: rockchip: Keep enabled PWMs running while probing Simon South
2020-09-19 8:35 ` Heiko Stübner [this message]
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=5907731.26MhtTZbrF@diego \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=simon@simonsouth.net \
/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).