From: Mark Rutland <mark.rutland@arm.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
Jason Cooper <jason@lakedaemon.net>,
Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
linux ARM <linux-arm-kernel@lists.infradead.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v4 4/4] mvebu: Dove: Add clocks and DFS interrupt to cpu node in DT.
Date: Wed, 4 Dec 2013 14:39:21 +0000 [thread overview]
Message-ID: <20131204143921.GC29200@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1386166641-7567-5-git-send-email-andrew@lunn.ch>
On Wed, Dec 04, 2013 at 02:17:21PM +0000, Andrew Lunn wrote:
> The dove-cpufreq driver needs access to the DDR and CPU clock. There
> is also an interrupt generated when the DFS hardware completes a
> change of frequencey. Add these to the cpu node in DT.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> Tested-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
> ---
> arch/arm/boot/dts/dove.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/boot/dts/dove.dtsi b/arch/arm/boot/dts/dove.dtsi
> index 4c8028513133..3842ba02dddf 100644
> --- a/arch/arm/boot/dts/dove.dtsi
> +++ b/arch/arm/boot/dts/dove.dtsi
> @@ -22,6 +22,10 @@
> device_type = "cpu";
> next-level-cache = <&l2>;
> reg = <0>;
> + clocks = <&core_clk 1>, <&core_clk 3>;
> + clock-names = "cpu_clk", "ddrclk";
> + interrupt-parent = <&pmu_intc>;
> + interrupts = <0>;
Is this interrupt actually generated by the CPU, or by the power
management unit?
Is ddrclk actually fed into the CPU? Given that you seem to have an
external L2 I don't see why the CPU would need the DDR clock.
Thanks,
Mark.
next prev parent reply other threads:[~2013-12-04 14:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 14:17 [PATCH v4 0/4] Dove cpufreq driver Andrew Lunn
2013-12-04 14:17 ` [PATCH v4 1/4] cpufreq: Add a cpufreq driver for Marvell Dove Andrew Lunn
2013-12-04 14:33 ` Jason Cooper
2013-12-04 14:56 ` Andrew Lunn
2013-12-04 15:01 ` Jason Cooper
2013-12-04 14:54 ` Mark Rutland
2013-12-04 15:27 ` Andrew Lunn
2013-12-05 18:23 ` Mark Rutland
2013-12-17 21:41 ` [RFC PATCH v5 0/4] Dove Cpufreq driver Andrew Lunn
2013-12-17 21:41 ` [RFC PATCH v5 1/4] cpufreq: Add a cpufreq driver for Marvell Dove Andrew Lunn
2013-12-20 3:32 ` Jason Cooper
2013-12-21 16:26 ` Andrew Lunn
2013-12-21 19:25 ` Jason Cooper
2013-12-21 21:54 ` Andrew Lunn
2013-12-22 4:00 ` Jason Cooper
2013-12-17 21:41 ` [RFC PATCH v5 2/4] mvebu: Dove: Indicate the architecture supports cpufreq Andrew Lunn
2013-12-17 21:41 ` [RFC PATCH v5 3/4] mvebu: Dove: Enable cpufreq driver in defconfig Andrew Lunn
2013-12-17 21:41 ` [RFC PATCH v5 4/4] mvebu: Dove: Add PMU node for cpufreq driver Andrew Lunn
2013-12-16 8:40 ` [PATCH v4 1/4] cpufreq: Add a cpufreq driver for Marvell Dove Viresh Kumar
2013-12-17 22:06 ` Andrew Lunn
2013-12-04 14:17 ` [PATCH v4 2/4] mvebu: Dove: Instantiate cpufreq driver Andrew Lunn
2013-12-04 14:36 ` Mark Rutland
2013-12-04 15:02 ` Andrew Lunn
2013-12-05 17:54 ` Mark Rutland
2013-12-05 18:29 ` Andrew Lunn
2013-12-08 0:50 ` Jason Cooper
2013-12-04 14:17 ` [PATCH v4 3/4] mvebu: Dove: Enable cpufreq driver in defconfig Andrew Lunn
2013-12-04 14:17 ` [PATCH v4 4/4] mvebu: Dove: Add clocks and DFS interrupt to cpu node in DT Andrew Lunn
2013-12-04 14:39 ` Mark Rutland [this message]
2013-12-04 14:55 ` Mark Rutland
2013-12-04 14:43 ` 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=20131204143921.GC29200@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=andrew@lunn.ch \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sebastian.hesselbarth@googlemail.com \
--cc=viresh.kumar@linaro.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).