[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150703135453.GI13481@lunn.ch>
Date: Fri, 3 Jul 2015 15:54:53 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Gregory CLEMENT <gregory.clement@...e-electrons.com>
Cc: Jason Cooper <jason@...edaemon.net>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org,
Mike Turquette <mturquette@...libre.com>,
Stephen Boyd <sboyd@...eaurora.org>, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org,
Daniel Lezcano <daniel.lezcano@...aro.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>, linux-pm@...r.kernel.org,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Boris BREZILLON <boris.brezillon@...e-electrons.com>,
Lior Amsalem <alior@...vell.com>,
Tawfik Bayouk <tawfik@...vell.com>,
Nadav Haklai <nadavh@...vell.com>
Subject: Re: [PATCH RFC 1/5] clk: mvebu: Add Armada 38x support for clk-cpu
On Fri, Jul 03, 2015 at 08:11:53AM +0200, Gregory CLEMENT wrote:
> This patch first shortens the registers definition and also introduces
> difference between Armada XP value and Armada 38x value.
>
> Then it adds specific functions for Armada 38x in order to support cpu
> freq on these SoCs.
Hi Gregory
I would suggest splitting this into two. Because of the #define
changes, it is not easy to see the new functions from #define changes.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@...e-electrons.com>
> ---
> .../devicetree/bindings/clock/mvebu-cpu-clock.txt | 27 ++-
> drivers/clk/mvebu/clk-cpu.c | 220 ++++++++++++++++-----
> 2 files changed, 201 insertions(+), 46 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/clock/mvebu-cpu-clock.txt b/Documentation/devicetree/bindings/clock/mvebu-cpu-clock.txt
> index 99c214660bdc..9272b3464ab1 100644
> --- a/Documentation/devicetree/bindings/clock/mvebu-cpu-clock.txt
> +++ b/Documentation/devicetree/bindings/clock/mvebu-cpu-clock.txt
> @@ -1,10 +1,13 @@
> Device Tree Clock bindings for cpu clock of Marvell EBU platforms
Maybe i'm reading the following hunk wrong, but....
> Required properties:
> -- compatible : shall be one of the following:
> +- compatible : shall be the following:
"one of the following" is grammatically better.
> "marvell,armada-xp-cpu-clock" - cpu clocks for Armada XP
> + "marvell,armada-38x-cpu-clock", "marvell,armada-xp-cpu-clock" - cpu
> + clocks for Armada 38x
and don't we now have marvell,armada-xp-cpu-clock twice?
> - reg : Address and length of the clock complex register set, followed
> - by address and length of the PMU DFS registers
> + by address and length of the PMU DFS registers, for Armada 38x
> + a third register set must be addeed: DFX server.
> - #clock-cells : should be set to 1.
> - clocks : shall be the input parent clock phandle for the clock.
>
> @@ -20,3 +23,23 @@ cpu@0 {
> reg = <0>;
> clocks = <&cpuclk 0>;
> };
> +
> +or for Armada38x
> +
> +cpuclk: clock-complex@...00 {
> + compatible = "marvell,armada-380-cpu-clock",
> + "marvell,armada-xp-cpu-clock";
> + reg = <0x18700 0xA0>, <0x1c054 0x40>,
> + <0xe4260 0x8>;
Maybe this third address property could be better indented?
Andrew
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists