From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Boyd Subject: Re: [PATCH 1/2] clk: qcom: common: Add API to register board clocks backwards compatibly Date: Tue, 27 Oct 2015 16:01:55 -0700 Message-ID: <20151027230155.GQ19782@codeaurora.org> References: <1445908827-31015-1-git-send-email-sboyd@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from smtp.codeaurora.org ([198.145.29.96]:58428 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752928AbbJ0XB4 (ORCPT ); Tue, 27 Oct 2015 19:01:56 -0400 Content-Disposition: inline In-Reply-To: <1445908827-31015-1-git-send-email-sboyd@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Mike Turquette Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, linux-arm-msm@vger.kernel.org, Georgi Djakov On 10/26, Stephen Boyd wrote: > We want to put the XO board clocks into the dt files. Add an API > to do this generically. This also makes a place for us to handle > the case where the RPM driver is enabled or disabled. > > Cc: Georgi Djakov > Signed-off-by: Stephen Boyd > --- > > I'm also thinking that maybe we should register the board clock if it > isn't there in DT and then we'll either register the pass through or > we'll skip it depending on if the RPM driver is enabled. That > way the RPM driver doesn't need to know anything, just register the > clock with parent as the board clock. That seems like a better idea. v2 coming with that change and a sleep_clk specific API, plus all the armv7 platforms converted. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project