From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: imx: Disable imx-cpufreq when cpufreq-cpu0 used
Date: Sun, 10 Mar 2013 23:51:59 +0100 [thread overview]
Message-ID: <20130310225159.GS1906@pengutronix.de> (raw)
In-Reply-To: <1362934407-29030-3-git-send-email-mpa@pengutronix.de>
On Sun, Mar 10, 2013 at 05:53:27PM +0100, Markus Pargmann wrote:
> cpufreq-cpu0 has DT support. So if imx27 or imx51 is booted with DT
> support, it should not use the old imx-cpufreq driver. Instead the
> operating-points should be defined in the appropriate DT files.
>
> Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> ---
> arch/arm/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
> index 5b71469..1247fe5 100644
> --- a/arch/arm/Kconfig
> +++ b/arch/arm/Kconfig
> @@ -2156,6 +2156,7 @@ source "drivers/cpufreq/Kconfig"
> config CPU_FREQ_IMX
> tristate "CPUfreq driver for i.MX CPUs"
> depends on ARCH_MXC && CPU_FREQ
> + depends on (!GENERIC_CPUFREQ_CPU0 || (!MACH_IMX51_DT && !MACH_IMX27_DT))
Does this driver work with multiplatform anyway? I mean it registers
a cpufreq driver without knowing that the kernel even runs on i.MX.
Maybe removing it is the better option?
Sascha
> select CPU_FREQ_TABLE
> help
> This enables the CPUfreq driver for i.MX CPUs.
> --
> 1.8.1.5
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-03-10 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 16:53 [PATCH 0/2] ARM: imx: kconfig changes for cpufreq-cpu0 Markus Pargmann
2013-03-10 16:53 ` [PATCH 1/2] ARM: imx27, imx5: Add kconfig selects " Markus Pargmann
2013-03-10 16:53 ` [PATCH 2/2] ARM: imx: Disable imx-cpufreq when cpufreq-cpu0 used Markus Pargmann
2013-03-10 22:51 ` Sascha Hauer [this message]
2013-03-11 6:36 ` Shawn Guo
2013-03-11 18:44 ` Markus Pargmann
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=20130310225159.GS1906@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).