Linux Power Management development
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	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: Fri, 4 Jul 2014 15:25:28 +0200	[thread overview]
Message-ID: <20140704132528.GD7773@lunn.ch> (raw)
In-Reply-To: <20140704131247.2c8ecde2@free-electrons.com>

> This doesn't work very well with the idea of having the OPP table
> statically encoded in to the Device Tree. Options are:
> 
>  - Improve the cpufreq-cpu0 driver so that the OPP table can be passed
>    through platform_data, and therefore built dynamically by the
>    platform code and passed when registering the cpufreq
>    platform_device.
> 
>  - Dynamically build/update the OPP table in the Device Tree.
> 
> Which option do you think is appropriate here?

It should also be noted that that applies to many Marvell SoCs.
Kirkwood and Dove are the same.

	 Andrew

  reply	other threads:[~2014-07-04 13:30 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 [this message]
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
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=20140704132528.GD7773@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=alior@marvell.com \
    --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=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