public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Rob Herring <robherring2@gmail.com>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	Tony Lindgren <tony@atomide.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Shawn Guo <shawn.guo@linaro.org>,
	linux-pm@vger.kernel.org,
	Mark Langsdorf <mark.langsdorf@calxeda.com>
Subject: Re: omap cpufreq driver in multi-platform kernels
Date: Wed, 27 Mar 2013 13:02:49 -0500	[thread overview]
Message-ID: <20130327180248.GB32693@kahuna> (raw)
In-Reply-To: <alpine.DEB.2.00.1303271747210.17356@utopia.booyaka.com>

On 17:48-20130327, Paul Walmsley wrote:
> Hi
> 
> On Wed, 27 Mar 2013, Nishanth Menon wrote:
> 
> > We should deprecate usage on omap-cpufreq driver eventually, instead go
> > towards embracing the SoC generic implementation of cpufreq-cpu0 driver
> > IMHO.
> > http://marc.info/?l=linux-omap&m=136371580826031&w=2
> > is the series to support cpufreq_cpu0 driver in DT based boot.
> > Would you think this approach is sane? 
> 
> Haven't looked closely at the series, but the idea makes sense to me, as 
Thanks.
> long as OMAP doesn't need to do anything too exotic in the CPUFreq driver.
:) I wish that were the case, from an SoC entitlement point of view,
purely controlling frequency and regulator is not sufficent for
most OMAPs/AM variants. We do have to deal with ABB and AVS (now a
multitude of class variants to deal with) - part of the rationale for
switching to generic cpufreq as part of DT steps is to force ourselves to
adhere to common code and entitle required SoC feature set.

If you get a chance, it would be nice to hear your views on the intermediate
step(the patch series pointed above) as part of overall OMAP transition to DT.
-- 
Regards,
Nishanth Menon

      reply	other threads:[~2013-03-27 18:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27  1:49 omap cpufreq driver in multi-platform kernels Rob Herring
2013-03-27  2:23 ` Paul Walmsley
2013-03-27 13:32   ` Nishanth Menon
2013-03-27 16:38     ` Rob Herring
2013-03-27 17:02       ` Nishanth Menon
2013-03-27 17:53         ` Kevin Hilman
2013-03-27 17:56           ` Nishanth Menon
2013-03-30 22:21             ` Paul Walmsley
2013-04-01 17:20               ` Eduardo Valentin
2013-04-01 19:14                 ` Nishanth Menon
2013-04-01 19:27                 ` Paul Walmsley
2013-04-01 19:46               ` Rob Herring
2013-04-01 21:58                 ` Paul Walmsley
2013-03-27 17:48     ` Paul Walmsley
2013-03-27 18:02       ` Nishanth Menon [this message]

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=20130327180248.GB32693@kahuna \
    --to=nm@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mark.langsdorf@calxeda.com \
    --cc=paul@pwsan.com \
    --cc=robherring2@gmail.com \
    --cc=shawn.guo@linaro.org \
    --cc=tony@atomide.com \
    /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