From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Thu, 8 Oct 2015 14:58:40 -0700 From: Stephen Boyd To: Heiko =?iso-8859-1?Q?St=FCbner?= Cc: mturquette@baylibre.com, linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, sjoerd.simons@collabora.co.uk Subject: Re: [PATCH 1/3] clk: add flag for clocks that need to be enabled on rate changes Message-ID: <20151008215840.GJ26883@codeaurora.org> References: <1929669.AsgMSusdJb@phil> <3137165.kmu68gRS44@diego> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 In-Reply-To: <3137165.kmu68gRS44@diego> List-ID: On 10/02, Heiko Stübner wrote: > Hi, > > any comment on these 3 patches? > Dong has a similar problem, but those patches conflate this with enabling parent clocks during clk_disable_unused() which makes no sense to me. So I'm ok with the requirement that we turn clocks on to change rates, but I wonder if in this case we need to turn on the clock that's changing rates itself, or if we just need to turn on the parent and/or future parent of the clock during the rate switch. Care to elaborate on that? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project