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
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
