Linux RTC
 help / color / mirror / Atom feed
From: Stephan Roslen <stephan@roslen.de>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: a.zummo@towertech.it, alexandre.belloni@free-electrons.com,
	wens@csie.org, rtc-linux@googlegroups.com
Subject: [rtc-linux] Re: [PATCH] rtc: sunxi: use external oscillator
Date: Thu, 7 Jul 2016 07:11:39 +0200	[thread overview]
Message-ID: <577DE48B.2020009@roslen.de> (raw)
In-Reply-To: <577DDF8C.6060404@roslen.de>



On 07.07.2016 06:50, Stephan Roslen wrote:
> On 06.07.2016 22:20, Maxime Ripard wrote:
>> The issue is actually worse than that.
>>
>> That register controls the losc source for the whole clock tree, so it
>> will affect every clock in the system.
>>
>> In order to have that correctly propagated, you should register a new
>> mux here in the clock framework, and have all the other clocks using
>> that mux as a parent.
>=20
> I agree. Checking the diagram in subsection 1.5.2 of the A20 manual it se=
ems, that LOSC can be a source for clocks like CPU and some SoC busses. So =
my patch could indeed mess with the whole clock tree.

Sorry for the addition. The mess of course is not that huge, for the mux se=
lects between a 32KHz Oscillator with +- 20% tolerance, thus ranging from 2=
5.6 to 38.4 KHz and the 32.768KHz external oscillator. Hence muxing to 32.7=
68KHz should be no problem for any clk, that was fine with the internal osc=
illator as clk source. Though still you're absolutely right, that this shou=
ld be handled in code correctly.

Stephan

--=20
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.
---=20
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 e=
mail to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

      parent reply	other threads:[~2016-07-07  5:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06  8:43 [rtc-linux] [PATCH] rtc: sunxi: use external oscillator Stephan Roslen
2016-07-06 20:20 ` [rtc-linux] " Maxime Ripard
2016-07-07  4:50   ` Stephan Roslen
2016-07-07  4:53     ` Chen-Yu Tsai
2016-07-07  6:12       ` Stephan Roslen
2016-07-07  7:08         ` Maxime Ripard
2016-07-07  6:42       ` Maxime Ripard
2016-07-07  5:11     ` Stephan Roslen [this message]

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=577DE48B.2020009@roslen.de \
    --to=stephan@roslen.de \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=rtc-linux@googlegroups.com \
    --cc=wens@csie.org \
    /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