From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751639Ab2H2F4s (ORCPT ); Wed, 29 Aug 2012 01:56:48 -0400 Received: from cassarossa.samfundet.no ([129.241.93.19]:35397 "EHLO cassarossa.samfundet.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750850Ab2H2F4r (ORCPT ); Wed, 29 Aug 2012 01:56:47 -0400 Date: Wed, 29 Aug 2012 07:56:25 +0200 From: Hans-Christian Egtvedt To: Mark Brown Cc: Arnd Bergmann , Russell King , Haavard Skinnemoen , Ralf Baechle , Benjamin Herrenschmidt , Paul Mackerras , Guan Xuetao , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org Subject: Re: [PATCH] clk: Make the generic clock API available by default Message-ID: <20120829055625.GA17753@samfundet.no> References: <1346186104-4083-1-git-send-email-broonie@opensource.wolfsonmicro.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1346186104-4083-1-git-send-email-broonie@opensource.wolfsonmicro.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Around Tue 28 Aug 2012 13:35:04 -0700 or thereabout, 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. > > Signed-off-by: Mark Brown > --- > > This depends on having one of the patches I've sent adding a generic > clkdev.h added merged - Arnd was expecting to merge one of those, there > was just the lack of clarity about the most practical Kbuild hookup. > > arch/arm/Kconfig | 12 ++++++++++++ > arch/avr32/Kconfig | 1 + For the AVR32 related changes Acked-by: Hans-Christian Egtvedt -- mvh Hans-Christian Egtvedt