Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751928Ab3FHJVq (ORCPT ); Sat, 8 Jun 2013 05:21:46 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:39507 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751571Ab3FHJVp (ORCPT ); Sat, 8 Jun 2013 05:21:45 -0400 Date: Sat, 8 Jun 2013 10:21:33 +0100 From: Russell King - ARM Linux To: Jonathan Cameron Cc: LKML , linux-arm-kernel , "Hennerich, Michael" , Lars-Peter Clausen Subject: Re: Arm sub architectures missing clk_round_rate() Message-ID: <20130608092133.GI18614@n2100.arm.linux.org.uk> References: <51B2F1ED.2090801@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51B2F1ED.2090801@kernel.org> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1166 Lines: 25 On Sat, Jun 08, 2013 at 09:57:17AM +0100, Jonathan Cameron wrote: > At least one Arm subarch (pxa) does no provide an implementation of this > function. As far as I can see there is no way for a driver wishing to use > it to detect it's absence. This is marked in clk.h as being optional > for 'Machine Class support'. Obvious solutions to this are: > > 1) It is effectively only usable by platform specific drivers as no > more generic driver can know it is available. Perhaps even a stub that > returns an appropriate error would be acceptable. > > 2) It is not as optional as the header implies and should always be implemented > if the rest of the clk framework is. > > 3) There should be some means of detecting its absense so that drivers can > be dependant on its presene. > > Which is the correct one? The right answer is (2) now that we have things like the clk framework and soo many users. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/