From: Samuel Ortiz <sameo@linux.intel.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Magnus Damm <damm@opensource.se>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Julia Lawall <julia@diku.dk>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] t7l66xb: properly free clk32k clock source
Date: Fri, 2 Jul 2010 17:16:40 +0200 [thread overview]
Message-ID: <20100702151639.GB2960@sortiz-mobl> (raw)
In-Reply-To: <1277977430.9342.5.camel@mola>
Hi Alex,
On Thu, Jul 01, 2010 at 05:43:50PM +0800, Axel Lin wrote:
> This patch includes below fixes to properly free clk32k clock source:
> 1. remove a redundant clk_put in t7l66xb_probe error path
> 2. add missing clk_disable(t7l66xb->clk32k) and clk_put(t7l66xb->clk32k)
> to properly free the clock source.
Patch applied to my for-next branch. This almost looks like 2.6.35 material
though.
Cheers,
Samuel.
> Signed-off-by: Axel Lin <axel.lin@gmail.com>
> ---
> drivers/mfd/t7l66xb.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/mfd/t7l66xb.c b/drivers/mfd/t7l66xb.c
> index 5041d33..006c121 100644
> --- a/drivers/mfd/t7l66xb.c
> +++ b/drivers/mfd/t7l66xb.c
> @@ -350,7 +350,6 @@ static int t7l66xb_probe(struct platform_device *dev)
> t7l66xb->clk48m = clk_get(&dev->dev, "CLK_CK48M");
> if (IS_ERR(t7l66xb->clk48m)) {
> ret = PTR_ERR(t7l66xb->clk48m);
> - clk_put(t7l66xb->clk32k);
> goto err_clk48m_get;
> }
>
> @@ -425,6 +424,8 @@ static int t7l66xb_remove(struct platform_device *dev)
> ret = pdata->disable(dev);
> clk_disable(t7l66xb->clk48m);
> clk_put(t7l66xb->clk48m);
> + clk_disable(t7l66xb->clk32k);
> + clk_put(t7l66xb->clk32k);
> t7l66xb_detach_irq(dev);
> iounmap(t7l66xb->scr);
> release_resource(&t7l66xb->rscr);
> --
> 1.5.4.3
>
>
>
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2010-07-02 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 9:43 [PATCH] t7l66xb: properly free clk32k clock source Axel Lin
2010-07-02 15:16 ` Samuel Ortiz [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=20100702151639.GB2960@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=axel.lin@gmail.com \
--cc=damm@opensource.se \
--cc=hsweeten@visionengravers.com \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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