From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Mike Turquette <mturquette@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Tawfik Bayouk <tawfik@marvell.com>,
Nadav Haklai <nadavh@marvell.com>,
Lior Amsalem <alior@marvell.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Subject: Re: [PATCH 2/8] cpufreq: add driver for Armada XP
Date: Wed, 16 Jul 2014 17:47:41 +0200 [thread overview]
Message-ID: <20140716174741.0399e9f8@free-electrons.com> (raw)
In-Reply-To: <CAKohpok6-_7aQ1RxSJKLo1idc777LHWLVM=tjtTLOzZjeAUpjw@mail.gmail.com>
Dear Viresh Kumar,
On Wed, 16 Jul 2014 21:02:29 +0530, Viresh Kumar wrote:
> > Would be good to have this soon, since the 3.17 merge window is
> > approaching. You asked me to use this cpufreq-generic driver instead of
> > a custom cpufreq driver, and I did the work to do that. So now I clearly
> > hope that cpufreq-generic will be merged in 3.17.
>
> Yeah, I have already pinged Rafael few days back on this. He came back
> from holidays last week and this is what he told me:
>
> Jul 11 19:58:34 <vireshk> rafael, when are you going to pick stuff for 3.17?
> Jul 11 19:59:11 <rafael> vireshk: next week i suppose
Ok.
> Do you depend on this patch btw?
>
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg675398.html
>
> Actually there had been some objections to comparing clocks this way and
> we *might* hold this off, unless the bindings are finalized. Will get all other
> patches merged though.
I'm not sure to fully understand what this patch is doing, but I
believe I depend on it. My system has one clock for each CPU, and
therefore each CPU has a separately controllable frequency. See
http://git.infradead.org/linux-mvebu.git/blob/3843607838cc5436d02a6771e661969a54c2fee0:/arch/arm/boot/dts/armada-xp-mv78460.dtsi#l30
for the Device Tree part describing the CPUs. So the existing
cpufreq-cpu0 (as of 3.16) doesn't work because it assumes there is one
single clock controlling the frequency.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-16 15:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 9:44 [PATCH 0/8] cpufreq support for Marvell Armada XP Thomas Petazzoni
2014-07-04 9:44 ` [PATCH 1/8] clk: add an APPLY_RATE_CHANGE notifier event during clk_set_rate() Thomas Petazzoni
2014-07-04 9:44 ` [PATCH 2/8] cpufreq: add driver for Armada XP Thomas Petazzoni
2014-07-04 9:55 ` Viresh Kumar
2014-07-04 11:12 ` Thomas Petazzoni
2014-07-04 13:25 ` Andrew Lunn
2014-07-04 13:52 ` Lucas Stach
2014-07-04 14:15 ` Andrew Lunn
2014-07-04 16:12 ` Viresh Kumar
2014-07-16 14:02 ` Thomas Petazzoni
2014-07-16 15:25 ` Viresh Kumar
2014-07-16 15:28 ` Thomas Petazzoni
2014-07-16 15:32 ` Viresh Kumar
2014-07-16 15:47 ` Thomas Petazzoni [this message]
2014-07-16 16:03 ` Viresh Kumar
2014-07-04 9:44 ` [PATCH 3/8] clk: mvebu: extend clk-cpu for dynamic frequency scaling Thomas Petazzoni
2014-07-04 9:44 ` [PATCH 4/8] ARM: mvebu: ensure CPU clocks are enabled Thomas Petazzoni
2014-07-04 9:45 ` [PATCH 5/8] ARM: mvebu: extend PMSU code to support dynamic frequency scaling Thomas Petazzoni
2014-07-04 9:45 ` [PATCH 6/8] ARM: mvebu: update Armada XP DT for " Thomas Petazzoni
2014-07-04 9:45 ` [PATCH 7/8] ARM: mvebu: allow enabling of cpufreq on Armada XP Thomas Petazzoni
2014-07-04 9:45 ` [PATCH 8/8] ARM: mvebu: update mvebu_v7_defconfig with cpufreq support Thomas Petazzoni
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=20140716174741.0399e9f8@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=nadavh@marvell.com \
--cc=rjw@rjwysocki.net \
--cc=sebastian.hesselbarth@gmail.com \
--cc=tawfik@marvell.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