From: Keerthy <a0393675@ti.com>
To: Paul Walmsley <paul@pwsan.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Keerthy <j-keerthy@ti.com>
Cc: <tony@atomide.com>, <linux-omap@vger.kernel.org>,
<pawel.moll@arm.com>, <galak@codeaurora.org>,
<akpm@linux-foundation.org>, <johan@kernel.org>,
<grygorii.strashko@ti.com>, <rtc-linux@googlegroups.com>,
<bcousson@baylibre.com>, <nm@ti.com>,
<devicetree@vger.kernel.org>, <t-kristo@ti.com>
Subject: [rtc-linux] Re: [PATCH v2 2/6] rtc: omap: Add external clock enabling support
Date: Fri, 14 Aug 2015 10:25:11 +0530 [thread overview]
Message-ID: <55CD74AF.4020803@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1508131822510.1009@utopia.booyaka.com>
On Friday 14 August 2015 01:47 AM, Paul Walmsley wrote:
> Hi guys
>
> On Wed, 12 Aug 2015, Alexandre Belloni wrote:
>
>> On 13/08/2015 at 00:38:50 +0530, Keerthy wrote :
>>> The intent here is to switch to a higher precision clock which is the
>>> internal clock when available.
>>>
>>> Alexandre,
>>>
>>> Is dynamic switching preferred over sticking to external clock always if
>>> present?
>>
>> I'd say that I don't really care. I'd say the best would be to make a
>> decision based on clock-accuracy but maybe that is an information you
>> don't have yet. Anyway, this could be added at a later date.
>
> Either the clock mux logic is glitchless, in which case the RTC is likely
> to lose at least 31 microseconds per switch; or it's not glitchless, in
> which case it's unsafe to switch the RTC clock source while the clock
> isn't gated. Keerthy, before submitting this patch for merging, I'd
> suggest consulting your hardware folks to figure out which case it is.
Paul,
Thanks. Yes so i am doing the static way first. Keeping external clock
always if available. Switching dynamically can be done later with more
clarifications.
Thanks,
Keerthy
>
>
> - Paul
>
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2015-08-14 4:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 9:28 [rtc-linux] [PATCH v2 0/6] ARM: AM4372: Enable RTC Keerthy
2015-08-10 9:28 ` [rtc-linux] [PATCH v2 1/6] ARM: dts: AM43XX: Add clk_32k_rtc node Keerthy
2015-08-10 9:28 ` [rtc-linux] [PATCH v2 2/6] rtc: omap: Add external clock enabling support Keerthy
2015-08-11 14:00 ` [rtc-linux] " Alexandre Belloni
2015-08-12 14:27 ` Paul Walmsley
2015-08-12 19:08 ` Keerthy
2015-08-12 20:16 ` Alexandre Belloni
2015-08-13 20:17 ` Paul Walmsley
2015-08-14 4:55 ` Keerthy [this message]
2015-08-14 8:29 ` Alexandre Belloni
2015-08-10 9:28 ` [rtc-linux] [PATCH v2 3/6] ARM: AM43xx: Introduce a separate soc_is function for am438x series of SoCs Keerthy
2015-08-11 12:55 ` [rtc-linux] " Tony Lindgren
2015-08-11 17:54 ` Keerthy
2015-08-12 8:37 ` Tony Lindgren
2015-08-13 6:59 ` Keerthy
2015-08-13 9:04 ` Keerthy
2015-08-13 9:59 ` Tony Lindgren
2015-08-10 9:28 ` [rtc-linux] [PATCH v2 4/6] ARM: dts: am43x-epos-evm: Add the am438 compatible string Keerthy
2015-08-10 9:28 ` [rtc-linux] [PATCH v2 5/6] ARM: AM43XX: HWMOD: Add rtc hwmod Keerthy
2015-08-12 14:39 ` [rtc-linux] " Paul Walmsley
2015-08-13 6:39 ` Tero Kristo
2015-08-10 9:28 ` [rtc-linux] [PATCH v2 6/6] ARM: dts: AM437X-GP-EVM: Enable rtc Keerthy
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=55CD74AF.4020803@ti.com \
--to=a0393675@ti.com \
--cc=akpm@linux-foundation.org \
--cc=alexandre.belloni@free-electrons.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grygorii.strashko@ti.com \
--cc=j-keerthy@ti.com \
--cc=johan@kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=pawel.moll@arm.com \
--cc=rtc-linux@googlegroups.com \
--cc=t-kristo@ti.com \
--cc=tony@atomide.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