linux-kernel - Re: [PATCH v2] ARM: imx: select ARCH_HAS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 8 Jan 2014 22:40:57 +0800
From:	Shawn Guo <shawn.guo@...aro.org>
To:	John Tobias <john.tobias.ph@...il.com>
CC:	<kernel@...gutronix.de>, <linux@....linux.org.uk>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] ARM: imx: select ARCH_HAS_CPUFREQ for iMX6SL

On Tue, Jan 07, 2014 at 06:29:23PM -0800, John Tobias wrote:
> iMX6SL now supports the cpufreq scaling by re-using the imx6q-cpufreq driver.
> By adding it, the user has the capability to select the said driver without
> depending it to SOC_IMX6Q.
> 
> Signed-off-by: John Tobias <john.tobias.ph@...il.com>
> ---
> Changes since v1:
> - Fix typo in commit log
> - Added Shawn Guo on Cc
> 
>  arch/arm/mach-imx/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
> index 7a6e6f7..704e5ae 100644
> --- a/arch/arm/mach-imx/Kconfig
> +++ b/arch/arm/mach-imx/Kconfig
> @@ -808,6 +808,7 @@ config SOC_IMX6Q
>  
>  config SOC_IMX6SL
>  	bool "i.MX6 SoloLite support"
> +	select ARCH_HAS_CPUFREQ

Since we will eventually enable CPUFREQ and OPP for most of the
platforms, maybe we should just move selection of ARCH_HAS_CPUFREQ,
ARCH_HAS_OPP and PM_OPP into 'config ARCH_MXC'?

Shawn

>  	select ARM_ERRATA_754322
>  	select ARM_ERRATA_775420
>  	select ARM_GIC
> -- 
> 1.8.3.2
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/