On Mon, Jan 23, 2017 at 11:41:49AM +0100, Maxime Ripard wrote: > The RTC controls the input source of the main 32kHz oscillator in the > system, feeding it to the clock unit too. > > By default, this is using an internal, very inaccurate (+/- 30%) > oscillator with a divider to make it roughly around 32kHz. This is however > quite impractical for the RTC, since our time will not be tracked properly. > > Since this oscillator is an input of the main clock unit, and since that > clock unit will be probed using CLK_OF_DECLARE, we have to use it as well, > leading to a two stage probe: one to enable the clock, the other one to > enable the RTC. > > There is also a slight change in the binding that is required (and should > have been from the beginning), since we'll need a phandle to the external > oscillator used on that board. We support the old binding by not allowing > to switch to the external oscillator and only using the internal one (which > was the previous behaviour) in the case where we're missing that phandle. > > Signed-off-by: Maxime Ripard <[email protected]> > --- > Documentation/devicetree/bindings/rtc/sun6i-rtc.txt | 10 +-
Acked-by: Rob Herring <[email protected]> > drivers/rtc/rtc-sun6i.c | 146 +++++++++++-- > 2 files changed, 143 insertions(+), 13 deletions(-) -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
