From: rjw@sisk.pl (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: add helper function cpufreq_set_target()
Date: Tue, 11 Sep 2012 22:35:38 +0200 [thread overview]
Message-ID: <201209112235.38246.rjw@sisk.pl> (raw)
In-Reply-To: <20120911013405.GB13721@S2101-09.ap.freescale.net>
On Tuesday, September 11, 2012, Shawn Guo wrote:
> On Mon, Sep 10, 2012 at 10:22:44PM +0200, Rafael J. Wysocki wrote:
> > Hmm. Who's going to use the cpufreq-cpu0 driver, then? Is OMAP going to be
> > the only user?
> >
> Any platform that supports device tree (DT) will be able to use the
> driver. Right now, I have seen imx6q, AM35xx and highbank start using
> the driver.
OK, that would be sufficient.
> > I'm concerned about the copy-pasting, but if that copy-pasting is going to
> > go away when you move OMAP to the new driver, then I agree that adding more
> > complexity just to avoid it is probably not a good idea.
> >
> > What's the planned time frame for the OMAP conversion?
> >
> That depends on when OMAP gets fully converted to DT. OMAP is in the
> middle of the DT transition right now. There are in-tree users of
> omap-cpufreq driver that does not support DT (board files). Before
> the DT conversion is fully done (all those non-DT board files gets
> removed), the omap-cpufreq driver still needs to be for a while.
I see.
Well, then I'll push the driver to Linus for v3.7 as is and we'll see who
and when starts to use it.
Thanks,
Rafael
prev parent reply other threads:[~2012-09-11 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 1:33 [PATCH] cpufreq: add helper function cpufreq_set_target() Shawn Guo
2012-09-07 19:31 ` Rafael J. Wysocki
2012-09-10 3:13 ` Shawn Guo
2012-09-10 20:22 ` Rafael J. Wysocki
2012-09-11 1:34 ` Shawn Guo
2012-09-11 20:35 ` Rafael J. Wysocki [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=201209112235.38246.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-arm-kernel@lists.infradead.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).