From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] ARM: berlin/dt: add cpupll and syspll support to BG2Q
Date: Fri, 21 Mar 2014 13:11:29 +0100 [thread overview]
Message-ID: <532C2C71.4010703@gmail.com> (raw)
In-Reply-To: <1395402220-23503-4-git-send-email-alexandre.belloni@free-electrons.com>
On 03/21/2014 12:43 PM, Alexandre Belloni wrote:
Alexandre,
Thanks for starting this! I'll start with the most obvious
things first and have a closer look on it later.
Missing commit description here.
> Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> ---
> arch/arm/boot/dts/berlin2q.dtsi | 20 ++++++++++++++++++--
> 1 file changed, 18 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/berlin2q.dtsi b/arch/arm/boot/dts/berlin2q.dtsi
> index 07452a7483fa..19d2c82b0664 100644
> --- a/arch/arm/boot/dts/berlin2q.dtsi
> +++ b/arch/arm/boot/dts/berlin2q.dtsi
> @@ -59,10 +59,26 @@
> clock-frequency = <100000000>;
> };
>
> + syspll: syspll {
syspll: pll at ea0030 {
and sort it in between other SoC nodes below. This will
most likely break clocks in v3.14 but v3.15 will receive
proper clock init ordering.
> + compatible = "marvell,berlin2q-pll";
> + clocks = <&smclk>;
> + #clock-cells = <0>;
> + reg = <0xf7ea0030 8>;
> + };
> +
> + cpupll: cpupll {
dito.
> + compatible = "marvell,berlin2q-pll";
> + clocks = <&smclk>;
> + #clock-cells = <0>;
> + reg = <0xf7dd0170 8>;
> + };
> +
> cpuclk: cpu-clock {
> - compatible = "fixed-clock";
> + compatible = "fixed-factor-clock";
> + clocks = <&cpupll>;
> #clock-cells = <0>;
> - clock-frequency = <1200000000>;
> + clock-div = <1>;
> + clock-mult = <1>;
Hmm, you probably know better than me, but if cpuclk == cpupll
is always true we don't need another clk layer here. If you
can scale down cpuclk from cpupll and we just have no driver
for it, I am fine with it.
Sebastian
> };
>
> twdclk: twdclk {
>
next prev parent reply other threads:[~2014-03-21 12:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 11:43 [PATCH 0/5] berlin: initial support for the clocks Alexandre Belloni
2014-03-21 11:43 ` [PATCH 1/5] clk: berlin: add support for berlin plls Alexandre Belloni
2014-03-21 12:49 ` Sebastian Hesselbarth
2014-03-21 15:45 ` Alexandre Belloni
2014-03-21 15:58 ` Alexandre Belloni
2014-03-21 16:03 ` Sebastian Hesselbarth
2014-03-21 16:01 ` Alexandre Belloni
2014-03-21 15:56 ` Alexandre Belloni
2014-03-21 16:04 ` Sebastian Hesselbarth
2014-03-21 11:43 ` [PATCH 2/5] clk: berlin: add berlin clocks DT bindings documentation Alexandre Belloni
2014-03-21 11:53 ` Mark Rutland
2014-03-21 12:16 ` Sebastian Hesselbarth
2014-03-21 11:43 ` [PATCH 3/5] ARM: berlin/dt: add cpupll and syspll support to BG2Q Alexandre Belloni
2014-03-21 12:11 ` Sebastian Hesselbarth [this message]
2014-03-21 12:17 ` Alexandre Belloni
2014-03-21 12:29 ` Sebastian Hesselbarth
2014-03-21 14:54 ` Alexandre Belloni
2014-03-21 11:43 ` [PATCH 4/5] ARM: berlin/dt: add cpupll and syspll support to BG2CD Alexandre Belloni
2014-03-21 12:13 ` Sebastian Hesselbarth
2014-03-21 11:43 ` [PATCH 5/5] ARM: berlin/dt: add cpupll and syspll support to BG2 Alexandre Belloni
2014-03-21 12:13 ` Sebastian Hesselbarth
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=532C2C71.4010703@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).