From: Jason Cooper <jason@lakedaemon.net>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Mike Turquette <mturquette@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.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-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: [PATCHv3 0/7] cpufreq support for Marvell Armada XP
Date: Sun, 13 Jul 2014 18:33:21 -0400 [thread overview]
Message-ID: <20140713223321.GI13108@titan.lakedaemon.net> (raw)
In-Reply-To: <1404920715-19834-1-git-send-email-thomas.petazzoni@free-electrons.com>
Mike,
On Wed, Jul 09, 2014 at 05:45:08PM +0200, Thomas Petazzoni wrote:
> Mike, Viresh, Rafael, Jason, Gregory, Andrew, Sebastian,
>
> Here is the third version of the patches adding cpufreq support for
> the Marvell Armada XP processor.
>
> Changes since v2
> ================
>
> - As suggested by Stephen Boyd, instead of using a new clock notifier
> that somewhat "hides" the dependency of the clk-cpu clock driver on
> the PMSU, use a direct call from the clk-cpu driver to the PMSU
> driver.
>
> - Add a comment that explains why the OPP are not removed on failure
> in the PMSU code initializing the cpufreq logic, in answer to the
> review from Ezequiel Garcia.
>
> Changes since v1
> ================
>
> - Rework the patch series to use the generalized cpufreq-cpu0
> (renamed cpufreq-generic) driver instead of having an Armada XP
> specific cpufreq driver. This was suggested by Viresh
> Kumar. Basically, it only involved adding a "clock-latency"
> property in the DT, and changing the PMSU code to register the two
> OPPs supported by each CPU, and registering the "cpufreq-generic"
> platform device instead of the "armadaxp-cpufreq" one.
>
> Jason, this patch series is based on 3.16-rc3, but it applies fine
> even with mvebu/fixes and mvebu/soc merged (which contain some PMSU
> changes), so I haven't based the patch series on those branches. To
> _work_, the code needs the new cpufreq-generic driver which is pending
> in Viresh Kumar's tree for 3.17, but there is no build dependency.
>
> Thanks,
>
> Thomas
>
> Thomas Petazzoni (7):
> ARM: mvebu: ensure CPU clocks are enabled
> ARM: mvebu: extend PMSU code to support dynamic frequency scaling
> clk: mvebu: extend clk-cpu for dynamic frequency scaling
> ARM: mvebu: update Armada XP DT for dynamic frequency scaling
> ARM: mvebu: allow enabling of cpufreq on Armada XP
> ARM: mvebu: update mvebu_v7_defconfig with cpufreq support
> ARM: configs: add cpufreq-generic in multi_v7_defconfig
>
> .../devicetree/bindings/clock/mvebu-cpu-clock.txt | 5 +-
> arch/arm/boot/dts/armada-xp-mv78230.dtsi | 2 +
> arch/arm/boot/dts/armada-xp-mv78260.dtsi | 2 +
> arch/arm/boot/dts/armada-xp-mv78460.dtsi | 4 +
> arch/arm/boot/dts/armada-xp.dtsi | 2 +-
> arch/arm/configs/multi_v7_defconfig | 1 +
> arch/arm/configs/mvebu_v7_defconfig | 2 +
> arch/arm/mach-mvebu/Kconfig | 1 +
> arch/arm/mach-mvebu/platsmp.c | 1 +
> arch/arm/mach-mvebu/pmsu.c | 162 +++++++++++++++++++++
> drivers/clk/mvebu/clk-cpu.c | 80 +++++++++-
> include/linux/mvebu-pmsu.h | 20 +++
> 12 files changed, 274 insertions(+), 8 deletions(-)
> create mode 100644 include/linux/mvebu-pmsu.h
Creating a clock branch for you to pull makes this series an unwieldy
knot of dependencies. :( Mind giving me an Ack to take it through the
mvebu tree?
thx,
Jason.
next prev parent reply other threads:[~2014-07-13 22:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 15:45 [PATCHv3 0/7] cpufreq support for Marvell Armada XP Thomas Petazzoni
2014-07-09 15:45 ` [PATCHv3 1/7] ARM: mvebu: ensure CPU clocks are enabled Thomas Petazzoni
2014-07-16 13:02 ` Jason Cooper
2014-07-09 15:45 ` [PATCHv3 2/7] ARM: mvebu: extend PMSU code to support dynamic frequency scaling Thomas Petazzoni
2014-07-23 23:50 ` Mike Turquette
2014-07-24 6:29 ` Thomas Petazzoni
2014-07-24 11:11 ` Jason Cooper
2014-07-09 15:45 ` [PATCHv3 3/7] clk: mvebu: extend clk-cpu for " Thomas Petazzoni
2014-07-09 15:45 ` [PATCHv3 4/7] ARM: mvebu: update Armada XP DT " Thomas Petazzoni
2014-07-16 12:55 ` Jason Cooper
2014-07-09 15:45 ` [PATCHv3 5/7] ARM: mvebu: allow enabling of cpufreq on Armada XP Thomas Petazzoni
2014-07-09 15:45 ` [PATCHv3 6/7] ARM: mvebu: update mvebu_v7_defconfig with cpufreq support Thomas Petazzoni
2014-07-16 12:52 ` Jason Cooper
2014-07-09 15:45 ` [PATCHv3 7/7] ARM: configs: add cpufreq-generic in multi_v7_defconfig Thomas Petazzoni
2014-07-16 12:49 ` Jason Cooper
2014-07-13 22:33 ` Jason Cooper [this message]
2014-07-23 11:19 ` [PATCHv3 0/7] cpufreq support for Marvell Armada XP Thomas Petazzoni
2014-07-23 11:39 ` Jason Cooper
2014-07-23 11:53 ` Thomas Petazzoni
2014-07-23 16:52 ` Viresh Kumar
2014-07-23 23:53 ` [PATCHv3 3/7] clk: mvebu: extend clk-cpu for dynamic frequency scaling Thomas Petazzoni
2014-07-24 6:33 ` Thomas Petazzoni
2014-07-24 17:52 ` Mike Turquette
2014-07-24 18:24 ` 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=20140713223321.GI13108@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--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=thomas.petazzoni@free-electrons.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