public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood add cpus definition needed by cpufreq driver to dtsi
Date: Mon, 3 Jun 2013 07:05:50 +0200	[thread overview]
Message-ID: <20130603050550.GB10843@lunn.ch> (raw)
In-Reply-To: <51ABC056.5000804@baker-net.org.uk>

On Sun, Jun 02, 2013 at 10:59:50PM +0100, Adam Baker wrote:
> The Kirkwood CPU Freq driver needs a CPU definition in order for the probe
> routine to activate it. Add a suitable definition to kirkwood.dtsi
> 
> This definition is only correct for single core SoCs. There is a dual core
> SoC in the kirkwood family (88F632X) but the rest of the Kirkwood drivers in
> the kernel don't currently support it. If they ever do the cpus definition
> would need to be duplicated in each of the SoC specific include files.
> 
> Signed-off-by: Adam Baker <linux@baker-net.org.uk>

Tested-by: Andrew Lunn <andrew@lunn.ch>

	   Andrew
> 
> 
> --- a/arch/arm/boot/dts/kirkwood.dtsi	2013-05-19 22:57:07.000000000 +0100
> +++ b/arch/arm/boot/dts/kirkwood.dtsi	2013-05-30 23:32:18.000000000 +0100
> @@ -4,6 +4,18 @@
>  	compatible = "marvell,kirkwood";
>  	interrupt-parent = <&intc>;
>  
> +        cpus {
> +		#address-cells = <1>;
> +		#size-cells = <0>;
> +
> +		cpu at 0 {
> +		      device_type = "cpu";
> +		      compatible = "marvell,feroceon";
> +		      clocks = <&core_clk 1>, <&core_clk 3>, <&gate_clk 11>;
> +		      clock-names = "cpu_clk", "ddrclk", "powersave";
> +		};
> +	};
> +
>  	aliases {
>  	       gpio0 = &gpio0;
>  	       gpio1 = &gpio1;

  reply	other threads:[~2013-06-03  5:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02 21:59 [PATCH] ARM: Kirkwood add cpus definition needed by cpufreq driver to dtsi Adam Baker
2013-06-03  5:05 ` Andrew Lunn [this message]
2013-06-03 16:25 ` Jason Cooper

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=20130603050550.GB10843@lunn.ch \
    --to=andrew@lunn.ch \
    --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