From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PM / OPP: Remove ARCH_HAS_OPP
Date: Fri, 6 Jun 2014 21:50:06 +0900 [thread overview]
Message-ID: <20140606125003.GA13332@verge.net.au> (raw)
In-Reply-To: <CANqRtoTy_LwSiZgRFEw5Ly4ojfinoCichxrX7cO6m2XB9JGoww@mail.gmail.com>
On Fri, Jun 06, 2014 at 09:14:01PM +0900, Magnus Damm wrote:
> On Fri, Jun 6, 2014 at 8:14 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Fri, Jun 06, 2014 at 11:36:56AM +0100, Mark Brown wrote:
> >> From: Mark Brown <broonie@linaro.org>
> >>
> >> Since the OPP layer is a kernel library which has been converted to be
> >> directly selectable by its callers rather than user selectable and
> >> requiring architectures to enable it explicitly the ARCH_HAS_OPP symbol
> >> has become redundant and can be removed. Do so.
> >>
> >> Signed-off-by: Mark Brown <broonie@linaro.org>
> >> ---
> >> Documentation/power/opp.txt | 3 ---
> >> arch/arm/mach-exynos/Kconfig | 1 -
> >> arch/arm/mach-highbank/Kconfig | 1 -
> >> arch/arm/mach-imx/Kconfig | 1 -
> >> arch/arm/mach-omap2/Kconfig | 1 -
> >> arch/arm/mach-shmobile/Kconfig | 2 --
> >> arch/arm/mach-vexpress/Kconfig | 1 -
> >> arch/arm/mach-zynq/Kconfig | 1 -
> >> drivers/devfreq/Kconfig | 1 -
> >> kernel/power/Kconfig | 3 ---
> >> 10 files changed, 15 deletions(-)
> >
> > shmobile portion:
> >
> > Acked-by: Simon Horman <horms+renesas@verge.net.au>
>
> Hi Simon, Mark,
>
> Nice to see cleanups in this area. Reducing the number of Kconfig
> symbols must be a good thing.
>
> I'm not sure about the expected merge order for this kind of change vs
> queued up stuff in the renesas git tree, but I believe the following
> patch selects ARCH_HAS_OPP:
>
> [PATCH v3] ARM: shmobile: Mark all SoCs in shmobile as CPUFreq, capable
I propose that we fix that up by adding an incremental patch to
mach-shmobile via my renesas tree once the dependency (assuming there is
one) is in Linus's tree.
next prev parent reply other threads:[~2014-06-06 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 10:36 [PATCH] PM / OPP: Remove ARCH_HAS_OPP Mark Brown
2014-06-06 11:14 ` Simon Horman
2014-06-06 12:14 ` Magnus Damm
2014-06-06 12:50 ` Simon Horman [this message]
2014-06-06 13:01 ` Magnus Damm
2014-06-06 13:08 ` Mark Brown
2014-06-06 21:15 ` Rafael J. Wysocki
2014-06-09 19:49 ` Mark Brown
2014-06-09 22:22 ` Rafael J. Wysocki
2014-06-09 22:51 ` Mark Brown
2014-06-10 0:15 ` Rafael J. Wysocki
2014-06-06 13:45 ` Rob Herring
2014-06-06 14:33 ` Nishanth Menon
2014-06-09 1:56 ` Shawn Guo
2014-06-09 4:49 ` Viresh Kumar
2014-07-22 14:43 Mark Brown
2014-07-22 23:51 ` Rafael J. Wysocki
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=20140606125003.GA13332@verge.net.au \
--to=horms@verge.net.au \
--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).