From: Scott Wood <scottwood@freescale.com>
To: Yuantian Tang <Yuantian.Tang@freescale.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] cpufreq: qoriq: Make the driver usable on all QorIQ platforms
Date: Tue, 11 Nov 2014 13:09:40 -0600 [thread overview]
Message-ID: <1415732980.15957.33.camel@freescale.com> (raw)
In-Reply-To: <6aaa50ef5f234fe2896f1c66eb646dfb@DM2PR03MB574.namprd03.prod.outlook.com>
On Tue, 2014-10-21 at 08:59 +0000, Yuantian Tang wrote:
> > > -config PPC_CORENET_CPUFREQ
> > > - tristate "CPU frequency scaling driver for Freescale E500MC SoCs"
> > > - depends on PPC_E500MC && OF && COMMON_CLK
> > > +config QORIQ_CPUFREQ
> > > + tristate "CPU frequency scaling driver for Freescale QorIQ SoCs"
> > > + depends on OF && COMMON_CLK
> > > select CLK_PPC_CORENET
> > > help
> > > - This adds the CPUFreq driver support for Freescale e500mc,
> > > - e5500 and e6500 series SoCs which are capable of changing
> > > - the CPU's frequency dynamically.
> > > + This adds the CPUFreq driver support for Freescale QorIQ SoCs
> > > + which are capable of changing the CPU's frequency dynamically.
> > >
> > > config CPU_FREQ_PMAC
> > > bool "Support for Apple PowerBooks"
> >
> > Don't need this duplication at all. Just move this to Kconfig instead of .arm and
> > ppc.
> >
> If I do so, menuconfig will display like this(on PPC):
> PowerPC CPU frequency scaling drivers ----
> QorIQ CPU Frequency scaling --->
> <*> CPU frequency scaling driver for Freescale QorIQ SoCs
> On ARM, there should be a similar problem.
> Isn't weird?
What purpose do those "<arch> CPU frequency scaling drivers" submenus
serve, versus just including the options in the main cpufreq menu? It's
not as if more than one arch would be visible at once (and when a
situation with multiple visible menus popped up, it was considered a
bug).
-Scott
next prev parent reply other threads:[~2014-11-11 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 3:13 [PATCH] cpufreq: qoriq: Make the driver usable on all QorIQ platforms B29983
2014-10-17 8:03 ` Kumar Gala
2014-10-20 2:20 ` Yuantian Tang
2014-10-21 8:25 ` Yuantian Tang
2014-10-17 8:08 ` Viresh Kumar
2014-10-20 6:10 ` Yuantian Tang
2014-10-21 8:59 ` Yuantian Tang
2014-10-21 9:03 ` Viresh Kumar
2014-10-27 3:39 ` Yuantian Tang
2014-11-10 4:56 ` Viresh Kumar
2014-11-11 19:09 ` Scott Wood [this message]
2014-11-12 3:41 ` 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=1415732980.15957.33.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Yuantian.Tang@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).