All of lore.kernel.org
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: <mturquette@baylibre.com>
Cc: <linux-kernel@vger.kernel.org>, Paul Bolle <pebolle@tiscali.nl>
Subject: Re: [RFC] drivers/clk/Kconfig: Change COMMON_CLK to tristate
Date: Wed, 17 Jun 2015 14:20:53 -0700	[thread overview]
Message-ID: <5581E4B5.9070607@freescale.com> (raw)
In-Reply-To: <1434567707-9352-1-git-send-email-yorksun@freescale.com>

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@freescale.com>
> CC: Paul Bolle <pebolle@tiscali.nl>
> CC: Mike Turquette <mturquette@baylibre.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
> 

  parent reply	other threads:[~2015-06-17 21:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17 19:01 [RFC] drivers/clk/Kconfig: Change COMMON_CLK to tristate York Sun
2015-06-17 19:01 ` York Sun
2015-06-17 19:05 ` Wolfram Sang
2015-06-17 19:15   ` York Sun
2015-06-17 19:15     ` York Sun
2015-06-17 21:20 ` York Sun [this message]
2015-06-18  9:18   ` Paul Bolle
2015-06-18 16:10     ` York Sun

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=5581E4B5.9070607@freescale.com \
    --to=yorksun@freescale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=pebolle@tiscali.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.