From: Robin Murphy <robin.murphy@arm.com>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>, linux-kernel@vger.kernel.org
Cc: Chen-Yu Tsai <wens@csie.org>, Rob Herring <robh@kernel.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2] panfrost: Properly undo pm_runtime_enable when deferring a probe
Date: Wed, 23 Oct 2019 13:49:59 +0100 [thread overview]
Message-ID: <6952956c-ba58-71de-05c9-fa39333484d9@arm.com> (raw)
In-Reply-To: <20191023122157.32067-1-tomeu.vizoso@collabora.com>
On 2019-10-23 1:21 pm, Tomeu Vizoso wrote:
> When deferring the probe because of a missing regulator, we were calling
> pm_runtime_disable even if pm_runtime_enable wasn't called.
>
> Move the call to pm_runtime_disable to the right place.
>
> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> Reported-by: Chen-Yu Tsai <wens@csie.org>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Fixes: f4a3c6a44b35 ("drm/panfrost: Disable PM on probe failure")
I think that commit was right at the time, but actually we missed
reordering the cleanup path to match the change in 635430797d3f.
Otherwise, though,
Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> ---
> drivers/gpu/drm/panfrost/panfrost_drv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/panfrost/panfrost_drv.c b/drivers/gpu/drm/panfrost/panfrost_drv.c
> index bc2ddeb55f5d..f21bc8a7ee3a 100644
> --- a/drivers/gpu/drm/panfrost/panfrost_drv.c
> +++ b/drivers/gpu/drm/panfrost/panfrost_drv.c
> @@ -556,11 +556,11 @@ static int panfrost_probe(struct platform_device *pdev)
> return 0;
>
> err_out2:
> + pm_runtime_disable(pfdev->dev);
> panfrost_devfreq_fini(pfdev);
> err_out1:
> panfrost_device_fini(pfdev);
> err_out0:
> - pm_runtime_disable(pfdev->dev);
> drm_dev_put(ddev);
> return err;
> }
>
next prev parent reply other threads:[~2019-10-23 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 12:09 [PATCH] " Tomeu Vizoso
2019-10-23 12:21 ` [PATCH v2] " Tomeu Vizoso
2019-10-23 12:49 ` Robin Murphy [this message]
2019-10-23 15:49 ` Steven Price
2019-10-23 17:58 ` Rob Herring
2019-10-24 3:51 ` Chen-Yu Tsai
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=6952956c-ba58-71de-05c9-fa39333484d9@arm.com \
--to=robin.murphy@arm.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tomeu.vizoso@collabora.com \
--cc=wens@csie.org \
/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
all inboxes | Powered by JetHome®