From: Kukjin Kim <kgene.kim@samsung.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: 'Vivek Gautam' <gautam.vivek@samsung.com>,
'Andrew Morton' <akpm@linuxfoundation.org>,
'Sylwester Nawrocki' <s.nawrocki@samsung.com>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org, a.zummo@towertech.it,
kgene.kim@samsung.com, thomas.ab@samsung.com,
dianders@chromium.org,
'Thomas Abraham' <thomas.abraham@linaro.org>
Subject: Re: [PATCH] rtc: rtc-s3c: use clk_prepare_enable and clk_disable_unprepare
Date: Tue, 23 Apr 2013 02:10:25 +0900 [thread overview]
Message-ID: <51756F01.20408@samsung.com> (raw)
In-Reply-To: <002e01ce366a$4c9f1390$e5dd3ab0$%han@samsung.com>
On 04/11/13 13:09, Jingoo Han wrote:
> On Wednesday, April 10, 2013 6:50 PM, Sylwester Nawrocki wrote:
>> On 04/09/2013 04:27 PM, Vivek Gautam wrote:
>>> From: Thomas Abraham<thomas.abraham@linaro.org>
>>>
>>> Convert clk_enable/clk_disable to clk_prepare_enable/clk_disable_unprepare
>>> calls as required by common clock framework.
>>>
>>> Signed-off-by: Thomas Abraham<thomas.abraham@linaro.org>
>>> Signed-off-by: Vivek Gautam<gautam.vivek@samsung.com>
Acked-by: Kukjin Kim <kgene.kim@samsung.com>
>>
>> Thanks Vivek.
>>
>> Reviewed-by: Sylwester Nawrocki<s.nawrocki@samsung.com>
>
> CC'ed Andrew Morton
>
> It looks good.
> Reviewed-by: Jingoo Han<jg1.han@samsung.com>
>
>>
>>> ---
>>>
>>> The v1 of this patch is pretty old, but the change needs to be merged to
>>> avoid getting those needless WARN_ON() dumps on console.
>>>
>>> Changes from v1:
>>> - Not using clk_disable_unprepare() at the end of s3c_rtc_probe(), since
>>> this will unprepare the rtc clock which is again getting used in other
>>> funtions later.
>>> - Using clk_unprepare() at the remove() instead to fix things up.
>>>
>>> drivers/rtc/rtc-s3c.c | 5 +++--
>>> 1 files changed, 3 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/rtc/rtc-s3c.c b/drivers/rtc/rtc-s3c.c
>>> index fb994e9..e3528c9 100644
>>> --- a/drivers/rtc/rtc-s3c.c
>>> +++ b/drivers/rtc/rtc-s3c.c
>>> @@ -430,6 +430,7 @@ static int s3c_rtc_remove(struct platform_device *dev)
>>>
>>> s3c_rtc_setaie(&dev->dev, 0);
>>>
>>> + clk_unprepare(rtc_clk);
>>> rtc_clk = NULL;
>>>
>>> return 0;
>>> @@ -498,7 +499,7 @@ static int s3c_rtc_probe(struct platform_device *pdev)
>>> return ret;
>>> }
>>>
>>> - clk_enable(rtc_clk);
>>> + clk_prepare_enable(rtc_clk);
>>>
>>> /* check to see if everything is setup correctly */
>>>
>>> @@ -578,7 +579,7 @@ static int s3c_rtc_probe(struct platform_device *pdev)
>>>
>>> err_nortc:
>>> s3c_rtc_enable(pdev, 0);
>>> - clk_disable(rtc_clk);
>>> + clk_disable_unprepare(rtc_clk);
>>>
>>> return ret;
>>> }
next prev parent reply other threads:[~2013-04-22 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 14:27 [PATCH] rtc: rtc-s3c: use clk_prepare_enable and clk_disable_unprepare Vivek Gautam
2013-04-10 9:50 ` Sylwester Nawrocki
2013-04-10 11:39 ` Vivek Gautam
2013-04-11 4:09 ` Jingoo Han
2013-04-22 17:10 ` Kukjin Kim [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-02 23:33 Thomas Abraham
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=51756F01.20408@samsung.com \
--to=kgene.kim@samsung.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linuxfoundation.org \
--cc=dianders@chromium.org \
--cc=gautam.vivek@samsung.com \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=s.nawrocki@samsung.com \
--cc=thomas.ab@samsung.com \
--cc=thomas.abraham@linaro.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 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.