From mboxrd@z Thu Jan 1 00:00:00 1970 From: Georgi Djakov Subject: Re: [PATCH v3 1/3] clk: Add safe switch hook Date: Thu, 10 Sep 2015 19:34:41 +0300 Message-ID: <55F1B121.5040600@linaro.org> References: <1439387673-13015-1-git-send-email-georgi.djakov@linaro.org> <1439387673-13015-2-git-send-email-georgi.djakov@linaro.org> <20150909225230.GX15099@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: Received: from mail-wi0-f176.google.com ([209.85.212.176]:35725 "EHLO mail-wi0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753573AbbIJQen (ORCPT ); Thu, 10 Sep 2015 12:34:43 -0400 Received: by wicge5 with SMTP id ge5so32238726wic.0 for ; Thu, 10 Sep 2015 09:34:42 -0700 (PDT) In-Reply-To: <20150909225230.GX15099@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Stephen Boyd Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org On 09/10/2015 01:52 AM, Stephen Boyd wrote: > On 08/12, Georgi Djakov wrote: >> From: Stephen Boyd >> >> Sometimes clocks can't accept their parent source turning off >> while the source is reprogrammed to a different rate. Most >> notably CPU clocks require a way to switch away from the current >> PLL they're running on, reprogram that PLL to a new rate, and >> then switch back to the PLL with the new rate once they're done. >> Add a hook that drivers can implement allowing them to return a >> 'safe parent' and 'safe frequency' that they can switch their >> parent to while the upstream source is reprogrammed to support >> this. >> >> Signed-off-by: Stephen Boyd >> Signed-off-by: Georgi Djakov > > Weird to be reviewing my own patch... > > Anyway, Mike tells me that coordinated clock rates are going to > be on the list this month. We should use those patches instead of > this safe parent/rate stuff. If the patches don't appear soon, we > can look into having the clock provider handle the parent/rate > switch itself. That isn't any worse that what we've been doing in > other providers. > Ok, thanks for the information! I will start moving this into the clock provider and when the coordinated clock rates are posted will try using them.