From: John Tobias <john.tobias.ph@gmail.com>
To: rjw@rjwysocki.net, viresh.kumar@linaro.org,
cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@pengutronix.de,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
shawn.guo@linaro.org, festevam@gmail.com
Cc: John Tobias <john.tobias.ph@gmail.com>
Subject: [PATCH v4 2/2] cpufreq: imx6q-cpufreq driver depends on SOC_IMX6Q/SOC_IMX6SL
Date: Thu, 9 Jan 2014 18:39:52 -0800 [thread overview]
Message-ID: <1389321592-33220-2-git-send-email-john.tobias.ph@gmail.com> (raw)
In-Reply-To: <1389321592-33220-1-git-send-email-john.tobias.ph@gmail.com>
The ARCH_HAS_CPUFREQ, HAVE_IMX_ANATOP and PM_OPP are moved up to ARCH_MCX.
The driver should show if the SOC_IMX6Q and/or SOC_IMX6SL is/are selected.
Signed-off-by: John Tobias <john.tobias.ph@gmail.com>
---
drivers/cpufreq/Kconfig.arm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
index 3ba5dcc..230c663 100644
--- a/drivers/cpufreq/Kconfig.arm
+++ b/drivers/cpufreq/Kconfig.arm
@@ -80,7 +80,7 @@ config ARM_HIGHBANK_CPUFREQ
config ARM_IMX6Q_CPUFREQ
tristate "Freescale i.MX6 cpufreq support"
- depends on ARCH_MXC
+ depends on SOC_IMX6Q || SOC_IMX6SL
depends on REGULATOR_ANATOP
help
This adds cpufreq driver support for Freescale i.MX6 series SoCs.
--
1.8.3.2
next prev parent reply other threads:[~2014-01-10 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 2:39 [PATCH v4 1/2] ARM: imx: add select on ARCH_MXC for cpufreq support John Tobias
2014-01-10 2:39 ` John Tobias [this message]
2014-01-13 3:26 ` [PATCH v4 2/2] cpufreq: imx6q-cpufreq driver depends on SOC_IMX6Q/SOC_IMX6SL Shawn Guo
2014-01-13 4:55 ` John Tobias
2014-01-13 3:20 ` [PATCH v4 1/2] ARM: imx: add select on ARCH_MXC for cpufreq support Shawn Guo
2014-01-13 4:54 ` John Tobias
2014-01-13 6:01 ` Shawn Guo
2014-01-14 21:37 ` John Tobias
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=1389321592-33220-2-git-send-email-john.tobias.ph@gmail.com \
--to=john.tobias.ph@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rjw@rjwysocki.net \
--cc=shawn.guo@linaro.org \
--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
all inboxes | Powered by JetHome®