From: nm@ti.com (Nishanth Menon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: instantiate cpufreq-cpu0 as a platform_driver
Date: Mon, 28 Jan 2013 12:20:11 -0600 [thread overview]
Message-ID: <20130128182011.GA6704@kahuna> (raw)
In-Reply-To: <20130128083159.GD31689@S2101-09.ap.freescale.net>
On 16:32-20130128, Shawn Guo wrote:
> On Sat, Jan 26, 2013 at 11:21:27PM +0100, Rafael J. Wysocki wrote:
> > On Saturday, January 26, 2013 09:55:50 PM Shawn Guo wrote:
> > > As multiplatform build is being adopted by more and more ARM platforms,
> > > initcall function should be used very carefully. For example, when
> > > GENERIC_CPUFREQ_CPU0 is built in the kernel, cpu0_cpufreq_driver_init()
> > > will be called on all the platforms to initialize cpufreq-cpu0 driver.
> > >
> > > To eliminate this undesired the effect, the patch changes cpufreq-cpu0
> > > driver to have it instantiated as a platform_driver. Then it will only
> > > run on platforms that create the platform_device "cpufreq-cpu0".
> > >
> > > Along with the change, it also changes cpu_dev to be &pdev->dev,
> > > so that managed functions can start working, and module build gets
> > > supported too.
> > >
> > > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > > ---
> > > Rafael,
> > >
> > > The patch depends patch "power: export opp cpufreq functions".
> > > https://patchwork.kernel.org/patch/1847261/
> >
> > That one should use EXPORT_SYMBOL_GPL() for exporting symbols, though.
> >
> When commit 80126ce (PM / OPP: Export symbols for module usage.)
> already exported a few symbols with EXPORT_SYMBOL()?
I have split this out as a separate OPP series with a variant of
https://patchwork.kernel.org/patch/1847261/ added at last.
Will post this out in a few mins.
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-01-28 18:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 13:55 [PATCH] cpufreq: instantiate cpufreq-cpu0 as a platform_driver Shawn Guo
2013-01-26 22:21 ` Rafael J. Wysocki
2013-01-28 8:32 ` Shawn Guo
2013-01-28 12:29 ` Rafael J. Wysocki
2013-01-28 18:20 ` Nishanth Menon [this message]
2013-01-28 4:12 ` Viresh Kumar
2013-01-28 7:02 ` Shawn Guo
2013-01-28 7:20 ` Viresh Kumar
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=20130128182011.GA6704@kahuna \
--to=nm@ti.com \
--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).