From: "maxime.ripard" <maxime.ripard@free-electrons.com>
To: "kevin.z.m" <kevin.z.m.zh@gmail.com>
Cc: "Emilio Lopez" <emilio@elopez.com.ar>,
"Mike Turquette" <mturquette@linaro.org>,
孙彦邦 <sunny@allwinnertech.com>, 吴书耕 <shuge@allwinnertech.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Re: [PATCH 4/4] ARM: sun6i: Enable clock support in the DTSI
Date: Thu, 1 Aug 2013 11:53:13 +0200 [thread overview]
Message-ID: <20130801095313.GK2911@lukather> (raw)
In-Reply-To: <2013080108343040654547@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]
Hi Kevin,
On Thu, Aug 01, 2013 at 08:34:35AM +0800, kevin.z.m wrote:
> > Ok, just so that we're on the same page, we have two oscillators running
> > at 32kHz, the internal being always there, and the external that could
> > or could not be there, and it's each different hardware block that can
> > be wired to one, the other or both?
> The selection of internal or external is a global setting for system.
> Hardware blocks (such as cpu、twi for ex.) just see a 32kHz clock
> source, but they don't care where the 32kHz clock
> from.
Ok.
> > There's no global mux that could use either one of the two 32k to
> > provide the only 32kHz source in the system, right?
> There is a global mux to select internal or external, but no mux for
> every hardware blocks. I think that the mux need not be managed in the
> clock driver. It should be set earlier in the boot loader.
> And the selection is keeping either system is power-on or power-off,
> when there is a power supply with battery or DC. Because the mux is in
> RTC power domain.
Yes, in that case, we mostly don't care for now. Maybe we will at some
point if we need to add power management features, but we'd better
consider a fixed-rate clock for now and not worry too much about it.
Thanks for your help!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-08-01 9:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 14:44 [PATCH 0/4] Add support for the Allwinner A31 clocks Maxime Ripard
2013-07-30 14:44 ` [PATCH 1/4] clk: sunxi: Rename the structure to prepare the addition of sun6i Maxime Ripard
2013-07-31 0:14 ` Emilio López
2013-07-31 9:20 ` Maxime Ripard
2013-07-30 14:44 ` [PATCH 2/4] clk: sunxi: Allow to specify the divider width from the dividers data Maxime Ripard
2013-07-31 0:27 ` Emilio López
2013-07-30 14:44 ` [PATCH 3/4] clk: sunxi: Add A31 clocks support Maxime Ripard
2013-07-31 1:01 ` Emilio López
2013-07-31 10:14 ` Maxime Ripard
2013-08-12 12:53 ` Mark Rutland
2013-08-12 13:01 ` Emilio López
2013-08-12 13:54 ` Mark Rutland
2013-07-30 14:44 ` [PATCH 4/4] ARM: sun6i: Enable clock support in the DTSI Maxime Ripard
2013-07-31 1:36 ` Emilio López
2013-07-31 7:37 ` Maxime Ripard
[not found] ` <2013073116110750016327@gmail.com>
2013-07-31 11:37 ` Emilio López
2013-07-31 11:49 ` maxime.ripard
[not found] ` <2013073120102496855035@gmail.com>
2013-07-31 15:49 ` maxime.ripard
[not found] ` <2013080108343040654547@gmail.com>
2013-08-01 9:53 ` maxime.ripard [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=20130801095313.GK2911@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=emilio@elopez.com.ar \
--cc=kevin.z.m.zh@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=shuge@allwinnertech.com \
--cc=sunny@allwinnertech.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