Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754138AbaAIOo3 (ORCPT ); Thu, 9 Jan 2014 09:44:29 -0500 Received: from mail-oa0-f48.google.com ([209.85.219.48]:35898 "EHLO mail-oa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751137AbaAIOoU (ORCPT ); Thu, 9 Jan 2014 09:44:20 -0500 MIME-Version: 1.0 In-Reply-To: <20140109113300.GA27432@n2100.arm.linux.org.uk> References: <20140109113300.GA27432@n2100.arm.linux.org.uk> Date: Thu, 9 Jan 2014 20:14:19 +0530 Message-ID: Subject: Re: [PATCH V3 Resend] cpufreq: create cpufreq_generic_get() routine From: Viresh Kumar To: Russell King - ARM Linux Cc: Olof Johansson , "linux-arm-kernel@lists.infradead.org" , Fengguang Wu , "Rafael J. Wysocki" , "linaro-kernel@lists.linaro.org" , Patch Tracking , "cpufreq@vger.kernel.org" , "linux-pm@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9 January 2014 17:03, Russell King - ARM Linux wrote: > No, it implements only what it's clk API implementation requires. I understand that platform specific parts/drivers aren't using anything outside of the clk API's currently implemented. But then there are generic parts of kernel which are free to use this routine. They may or may not call it on that particular platform, which is currently happening for SA1100. And so I feel that we need to have dummy APIs like clk.h in there, as they wouldn't harm at all or break any existing stuff. > I've no idea at the moment, and I don't have time to look at this. Okay. I will go ahead with dummy implementations for now. See if you can give that a short review. Thanks. -- 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/