From: Alim Akhtar <alim.akhtar@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org
Cc: alexandre.belloni@free-electrons.com, javier@osg.samsung.com,
pankaj.dubey@samsung.com
Subject: Re: [RFC PATCH 1/2] rtc: s3c: Remove unnecessary call to disable already disabled clock
Date: Tue, 05 Jul 2016 14:16:54 +0530 [thread overview]
Message-ID: <577B73FE.1020509@samsung.com> (raw)
In-Reply-To: <577B5F28.1010905@samsung.com>
Hi Krzsztof,
On 07/05/2016 12:48 PM, Krzysztof Kozlowski wrote:
> On 07/04/2016 01:03 PM, Alim Akhtar wrote:
>> At the end of s3c_rtc_probe(), s3c_rtc_disable_clk() being called with rtc
>> clock already disabled, which looks extra and unnecessary call.
>> Lets clean it up.
>
> Does not look right. Till that place, the clocks are enabled. Then
> s3c_rtc_setaie() is called which expects that clocks are disabled...
> otherwise counters get mixed.
>
The clock is always disabled when it reach s3c_rtc_setfreq() in probe(),
because s3c_rtc_gettime() will always disable the clock.
As far as s3c_rtc_setaie() is concern, it enables clock while entering
and disables it while leaving the function. And in
s3c_rtc_{enable,disable}_clk() there is check info->clk_disabled flag
which will make sure clock balancing.
> So overall this looks like wrong approach unless I am missing something?
>
> Best regards,
> Krzysztof
>
>>
>> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
>> ---
>> drivers/rtc/rtc-s3c.c | 2 --
>> 1 file changed, 2 deletions(-)
>>
>> diff --git a/drivers/rtc/rtc-s3c.c b/drivers/rtc/rtc-s3c.c
>> index d01ad7e..b083840 100644
>> --- a/drivers/rtc/rtc-s3c.c
>> +++ b/drivers/rtc/rtc-s3c.c
>> @@ -577,8 +577,6 @@ static int s3c_rtc_probe(struct platform_device *pdev)
>>
>> s3c_rtc_setfreq(info, 1);
>>
>> - s3c_rtc_disable_clk(info);
>> -
>> return 0;
>>
>> err_nortc:
>
>
next prev parent reply other threads:[~2016-07-05 8:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 11:03 [RFC PATCH 1/2] rtc: s3c: Remove unnecessary call to disable already disabled clock Alim Akhtar
2016-07-04 11:03 ` [RFC PATCH 2/2] rtc: s3c: Add s3c_rtc_{enable/disable}_clk in s3c_rtc_setfreq() Alim Akhtar
2016-07-05 8:16 ` Krzysztof Kozlowski
2016-07-05 8:52 ` Alim Akhtar
2016-07-05 8:56 ` Krzysztof Kozlowski
2016-07-05 9:43 ` pankaj.dubey
2016-07-05 9:44 ` pankaj.dubey
2016-07-05 7:18 ` [RFC PATCH 1/2] rtc: s3c: Remove unnecessary call to disable already disabled clock Krzysztof Kozlowski
2016-07-05 8:46 ` Alim Akhtar [this message]
2016-07-05 8:50 ` Krzysztof Kozlowski
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=577B73FE.1020509@samsung.com \
--to=alim.akhtar@samsung.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=javier@osg.samsung.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.dubey@samsung.com \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox