From: Paul Bolle <pebolle@tiscali.nl>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v3] ARM: shmobile: Mark all SoCs in shmobile as CPUFreq, capable
Date: Thu, 19 Jun 2014 07:49:35 +0000 [thread overview]
Message-ID: <1403164175.23136.13.camel@x220> (raw)
In-Reply-To: <538FE8D8.3050602@bp.renesas.com>
On Thu, 2014-06-05 at 12:49 +0900, Gaku Inami wrote:
> From: Benoit Cousson <bcousson@baylibre.com>
>
> Mark all SoCs in shmobile as CPUFreq capable
> on multiplatform build only.
>
> Signed-off-by: Benoit Cousson <bcousson@baylibre.com>
> [gaku.inami.xw@bp.renesas.com: Move the definition of cpufreq capable]
> Signed-off-by: Gaku Inami <gaku.inami.xw@bp.renesas.com>
> ---
This patch landed in next-20140619.
> Changes since version 1:
> - changed "Signed-off-by" and "From" correctly.
> - fixed typo.
>
> Changes since version 2:
> - moved the definition of cpufreq capable for shmobile.
> - reworked based on renesas-devel-v3.15-rc8-20140605.
>
> arch/arm/mach-shmobile/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/mach-shmobile/Kconfig b/arch/arm/mach-shmobile/Kconfig
> index 2a7712b..3b28bd8 100644
> --- a/arch/arm/mach-shmobile/Kconfig
> +++ b/arch/arm/mach-shmobile/Kconfig
> @@ -13,6 +13,8 @@ config ARCH_SHMOBILE_MULTI
> select NO_IOPORT_MAP
> select PINCTRL
> select ARCH_REQUIRE_GPIOLIB
> + select ARCH_HAS_CPUFREQ
The symbol ARCH_HAS_CPUFREQ was just removed in next-20140616, see
commit e49d9b375628 ("ARM: Remove ARCH_HAS_CPUFREQ config option"). So
selecting that became a nop.
Is the trivial patch to drop this select statement queued somewhere?
(Grepping for CPU_FREQ and CPUFREQ in arch/arm/mach-shmobile suggests
that this trivial patch is all that is needed at this point.)
> + select ARCH_HAS_OPP
>
> if ARCH_SHMOBILE_MULTI
>
Paul Bolle
next prev parent reply other threads:[~2014-06-19 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 3:49 [PATCH v3] ARM: shmobile: Mark all SoCs in shmobile as CPUFreq, capable Gaku Inami
2014-06-05 4:09 ` Simon Horman
2014-06-19 7:49 ` Paul Bolle [this message]
2014-06-19 8:09 ` Simon Horman
2014-06-19 9:16 ` Gaku Inami
2014-06-20 1:18 ` Simon Horman
2014-06-20 4:40 ` Gaku Inami
2014-06-20 5:04 ` Simon Horman
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=1403164175.23136.13.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-sh@vger.kernel.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).