From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm64: Enable OPP
Date: Fri, 9 May 2014 17:40:29 +0100 [thread overview]
Message-ID: <1399653631-4938-1-git-send-email-broonie@kernel.org> (raw)
From: Mark Brown <broonie@linaro.org>
Some of the generic drivers used on ARM class systems use OPP so allow it
to be selected in Kconfig. No code is required for this, it is not clear
to me why there is config for this option.
Signed-off-by: Mark Brown <broonie@linaro.org>
---
arch/arm64/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 8ccdd2646ae3..8256d6d09d33 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -2,6 +2,7 @@ config ARM64
def_bool y
select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE
select ARCH_USE_CMPXCHG_LOCKREF
+ select ARCH_HAS_OPP
select ARCH_HAS_SG_CHAIN
select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST
select ARCH_WANT_OPTIONAL_GPIOLIB
--
2.0.0.rc2
next reply other threads:[~2014-05-09 16:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 16:40 Mark Brown [this message]
2014-05-09 16:40 ` [PATCH 2/3] arm64: Add big.LITTLE switcher stub Mark Brown
2014-05-09 17:05 ` Sudeep Holla
2014-05-09 17:50 ` Mark Brown
2014-05-09 18:57 ` Sudeep Holla
2014-05-09 19:29 ` Mark Brown
2014-05-12 8:34 ` Sudeep Holla
2014-05-12 12:17 ` Mark Brown
2014-05-12 14:09 ` Mark Hambleton
2014-05-09 17:47 ` Catalin Marinas
2014-05-09 18:01 ` Mark Brown
2014-05-11 3:29 ` Nicolas Pitre
2014-05-09 16:40 ` [PATCH 3/3] cpufreq: Enable big.LITTLE cpufreq driver on arm64 Mark Brown
2014-05-12 4:16 ` Viresh Kumar
2014-05-19 23:19 ` Rafael J. Wysocki
2014-05-19 23:07 ` Mark Brown
2014-05-19 23:36 ` Rafael J. Wysocki
2014-06-05 10:04 ` Catalin Marinas
2014-06-05 12:10 ` Rafael J. Wysocki
2014-05-09 17:02 ` [PATCH 1/3] arm64: Enable OPP menon.nishanth at gmail.com
2014-05-09 17:11 ` Mark Brown
2014-05-09 17:17 ` menon.nishanth at gmail.com
2014-05-09 18:18 ` Mark Brown
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=1399653631-4938-1-git-send-email-broonie@kernel.org \
--to=broonie@kernel.org \
--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).