Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754204AbdL1W5O (ORCPT ); Thu, 28 Dec 2017 17:57:14 -0500 Received: from smtp.codeaurora.org ([198.145.29.96]:57624 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751169AbdL1W5N (ORCPT ); Thu, 28 Dec 2017 17:57:13 -0500 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 7E2E5607E8 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=sboyd@codeaurora.org Date: Thu, 28 Dec 2017 14:57:11 -0800 From: Stephen Boyd To: Lori Hikichi Cc: Michael Turquette , Ray Jui , Scott Branden , Jon Mason , bcm-kernel-feedback-list@broadcom.com, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Simran Rai Subject: Re: [PATCH v1 1/4] clk: iproc: Allow iproc pll to runtime calculate vco parameters Message-ID: <20171228225711.GT7997@codeaurora.org> References: <1502737241-2040-1-git-send-email-lori.hikichi@broadcom.com> <1502737241-2040-2-git-send-email-lori.hikichi@broadcom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1502737241-2040-2-git-send-email-lori.hikichi@broadcom.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1078 Lines: 24 On 08/14, Lori Hikichi wrote: > Add the ability for the iproc pll to calculate the pll parameters at > runtime instead of only using predefined tables. This ability allows > the clock users to select from the full range of vco frequencies. > The old method of table based programming is retained so that existing > users will retain expected behavior. The flag IPROC_CLK_PLL_CALC_PARAM > will need to be set to enable the new runtime calculation method. > Currently, this is only being enabled for the audio pll. > > This feature also revealed a problem with the driver using the > round_rate api. The round_rate api does not allow for frequencies larger > than 2^31 to be returned. Those large frequencies are interpreted as an > error code. Therefore, we are moving to the determine_rate api which > solves this problem. > > Signed-off-by: Simran Rai > Signed-off-by: Lori Hikichi > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project