linux-kernel - Re: [RFC] drivers/clk/Kconfig: Change COMMON

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]

Message-ID: <5581E4B5.9070607@freescale.com>
Date:	Wed, 17 Jun 2015 14:20:53 -0700
From:	York Sun <yorksun@...escale.com>
To:	<mturquette@...libre.com>
CC:	<linux-kernel@...r.kernel.org>, Paul Bolle <pebolle@...cali.nl>
Subject: Re: [RFC] drivers/clk/Kconfig: Change COMMON_CLK to tristate

Drop linux-i2c mailing list.

Michael/Paul,

Please review and tell me if this is a bad idea. I am working on a platform
COMMON_CLK is not enabled. The clock I need is on a PCIe card. I don't think
modify platform Kconfig is right. So modifying drivers/clk/Kconfig seems
reasonable to me.

York


On 06/17/2015 12:01 PM, York Sun wrote:
> COMMON_CLK has been a bool value, selected by the platforms who need
> common clock framework. If a CCF driver is needed on an add-on device
> such as PCIe card, COMMON_CLK can be selected individually as a
> tristate value.
> 
> Signed-off-by: York Sun <yorksun@...escale.com>
> CC: Paul Bolle <pebolle@...cali.nl>
> CC: Mike Turquette <mturquette@...libre.com>
> ---
>  drivers/clk/Kconfig |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 32b2219..07f0b2f 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -10,7 +10,7 @@ config HAVE_MACH_CLKDEV
>  	bool
>  
>  config COMMON_CLK
> -	bool
> +	tristate "Common Clock"
>  	select HAVE_CLK_PREPARE
>  	select CLKDEV_LOOKUP
>  	select SRCU
> 
--
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/