On 13/08/2015 at 20:17:23 +0000, Paul Walmsley wrote : > > 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. > Don't take me wrong, your point is perfectly valid. I was just saying that I didn't care what was done in the driver. Obviously, this has to match what is best from a hardware point of view. But since we agreed on the DT bindings, I'd say that we can still adjust the driver later. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- 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
