[Top] [All Lists]

Re: [PATCH] clk: Make the generic clock API available by default

To: Mark Brown <>
Subject: Re: [PATCH] clk: Make the generic clock API available by default
From: Stephen Warren <>
Date: Mon, 22 Oct 2012 09:56:54 -0600
Cc: Russell King <>, Mike Turquette <>, Guan Xuetao <>, Ralf Baechle <>,,,
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
References: <>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
On 10/22/2012 07:02 AM, Mark Brown wrote:
> Rather than requiring platforms to select the generic clock API to make
> it available make the API available as a user selectable option unless the
> user either selects HAVE_CUSTOM_CLK (if they have their own implementation)
> or selects COMMON_CLK (if they depend on the generic implementation).
> All current architectures that HAVE_CLK but don't use the common clock
> framework have selects of HAVE_CUSTOM_CLK added.
> This allows drivers to use the generic API on platforms which have no need
> for the clock API at platform level.

> diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig

> @@ -632,6 +634,7 @@ config ARCH_TEGRA
>       select GENERIC_GPIO
>       select HAVE_CLK
> +     select HAVE_CUSTOM_CLK
>       select HAVE_SMP
>       select MIGHT_HAVE_CACHE_L2X0
>       select SPARSE_IRQ

Since v3.7-rc1, Tegra uses common clock, so I don't think the change
above is right is it?

<Prev in Thread] Current Thread [Next in Thread>