From: Felipe Balbi <balbi@ti.com>
To: Julien CHAUVEAU <julien.chauveau@neo-technologies.fr>
Cc: David Airlie <airlied@linux.ie>, Rob Clark <robdclark@gmail.com>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/tilcdc: add missing clk_put in tilcdc_unload()
Date: Wed, 19 Nov 2014 08:32:59 -0600 [thread overview]
Message-ID: <20141119143259.GC4029@saruman> (raw)
In-Reply-To: <1416406400-10564-1-git-send-email-julien.chauveau@neo-technologies.fr>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
On Wed, Nov 19, 2014 at 03:13:20PM +0100, Julien CHAUVEAU wrote:
> We need to call clk_put on display clock, in the same way as functional clock.
>
> Signed-off-by: Julien CHAUVEAU <julien.chauveau@neo-technologies.fr>
> ---
> drivers/gpu/drm/tilcdc/tilcdc_drv.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.c b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> index 79a34cb..ccc1cdb 100644
> --- a/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> +++ b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
> @@ -136,6 +136,9 @@ static int tilcdc_unload(struct drm_device *dev)
> CPUFREQ_TRANSITION_NOTIFIER);
> #endif
>
> + if (priv->disp_clk)
> + clk_put(priv->disp_clk);
> +
> if (priv->clk)
> clk_put(priv->clk);
we should actually remove the priv->$clk check. clk_put() is safe
against NULL pointers.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-19 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 14:13 [PATCH] drm/tilcdc: add missing clk_put in tilcdc_unload() Julien CHAUVEAU
2014-11-19 14:13 ` Julien CHAUVEAU
2014-11-19 14:32 ` Felipe Balbi [this message]
2014-11-19 14:56 ` [PATCH v2] " Julien CHAUVEAU
2014-11-19 14:56 ` Julien CHAUVEAU
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=20141119143259.GC4029@saruman \
--to=balbi@ti.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=julien.chauveau@neo-technologies.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.