Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933546AbbGUSF7 (ORCPT ); Tue, 21 Jul 2015 14:05:59 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:52157 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755541AbbGUSF5 (ORCPT ); Tue, 21 Jul 2015 14:05:57 -0400 Message-ID: <55AE8A02.9070801@codeaurora.org> Date: Tue, 21 Jul 2015 11:05:54 -0700 From: Stephen Boyd User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5 MIME-Version: 1.0 To: Sudeep Holla CC: "linux-kernel@vger.kernel.org" , "linux-pm@vger.kernel.org" , "linux-clk@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Liviu Dudau , Lorenzo Pieralisi , "Jon Medhurst (Tixy)" , Arnd Bergmann , Kevin Hilman , Olof Johansson , Mike Turquette Subject: Re: [PATCH v4 3/8] clk: add support for clocks provided by SCP(System Control Processor) References: <1433760002-24120-1-git-send-email-sudeep.holla@arm.com> <1433760002-24120-4-git-send-email-sudeep.holla@arm.com> <20150702172310.GF4301@codeaurora.org> <5596A1B6.8020307@arm.com> <559ADC94.4080505@codeaurora.org> <559BF858.1020301@arm.com> <20150708014606.GH30412@codeaurora.org> <55A7D79B.3080305@arm.com> <20150716193114.GA17952@codeaurora.org> <55A8E434.2010709@arm.com> <55A945DF.3@codeaurora.org> <55ACB733.2080609@arm.com> In-Reply-To: <55ACB733.2080609@arm.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1443 Lines: 39 On 07/20/2015 01:54 AM, Sudeep Holla wrote: > > > On 17/07/15 19:13, Stephen Boyd wrote: >> On 07/17/2015 04:17 AM, Sudeep Holla wrote: > > [...] > >>> >>> determine_rate change shouldn't affect SCPI clock driver but I remember >>> seeing round_rate change too on the list which returns value using the >>> argument from Boris. Is that planned for v4.3 ? I would need the stable >>> branch from this clk_hw_set_rate_range if you decide to push. Let me >>> know your preferences. I will post the updated version of the patch >>> accordingly. >>> >> >> We're not going to change round_rate() so it sounds like you don't need >> a stable branch. But you would need this new consumer API. So you still >> need a branch right? >> > > I am fine either way. If no one else need the stable branch to be shared > with arm-soc, I prefer to use clock consumer API for now to avoid all > the troubles to you guys and switch to provider API later. I will post > it once the both this driver and that provider API is merged, if that's > fine with you ? Ok. Sounds fine as long as we don't forget. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- 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/