From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C6F03C4332F for ; Fri, 15 Oct 2021 00:01:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id A012361152 for ; Fri, 15 Oct 2021 00:01:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234543AbhJOAED (ORCPT ); Thu, 14 Oct 2021 20:04:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:59960 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234521AbhJOAEC (ORCPT ); Thu, 14 Oct 2021 20:04:02 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id DB5B3601FA; Fri, 15 Oct 2021 00:01:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1634256117; bh=DaQPSl2wogcEKfQYg0cqX/7olwg80m3cW1DGsTWwlkU=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=KJMTaLLOD2lKZBlE6svvM5iL3VrAo1kVHp2PCnYkV2oUAQzaf4Zptbel8C95pvYTJ FUrcqhbVzFpXYH/J+U8iHeDDMre+5I8iDtZVhuoezOwzCaJQSOD1m2BAyM0On4eJ2L 9E/4mHCsvU+2++1lkqYX1XShm82UQzm8AkTJYxoHNEtpITy2itz4Wt5tHXy5KO3iwB yG2J24aaHShM77oFbBacjosWV4+oV9Wp/Sf7qEbFH9zRGogN7vEYVupJ/D54tRL7KC 9RMYnYG13Ymdf13UVvKBfbqjxkJYzm2kaoi5WiAB7L/FiIlNzHpQNPQPTKUmyYyjA7 MZ0K3aT85OlvQ== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <070b1b25-3718-5f3a-869b-a3954fdcc7c5@linaro.org> References: <20210829154757.784699-1-dmitry.baryshkov@linaro.org> <20210829154757.784699-8-dmitry.baryshkov@linaro.org> <4614587c-b87a-4375-cb6a-6af6f5462c6b@linaro.org> <163415465484.936110.9292145029740247591@swboyd.mtv.corp.google.com> <070b1b25-3718-5f3a-869b-a3954fdcc7c5@linaro.org> Subject: Re: [PATCH v7 7/8] clk: qcom: dispcc-sm8250: stop using mmcx regulator From: Stephen Boyd Cc: Andy Gross , Rob Herring , Taniya Das , Jonathan Marek , Michael Turquette , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org, Bryan O'Donoghue , Mark Brown , Ulf Hansson , linux-kernel@vger.kernel.org To: Bjorn Andersson , Dmitry Baryshkov Date: Thu, 14 Oct 2021 17:01:55 -0700 Message-ID: <163425611555.1688384.11653527408173081635@swboyd.mtv.corp.google.com> User-Agent: alot/0.9.1 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Dmitry Baryshkov (2021-10-14 02:53:41) > On 13/10/2021 22:50, Stephen Boyd wrote: > > Quoting Dmitry Baryshkov (2021-10-07 09:16:13) > >> On 07/10/2021 18:48, Bjorn Andersson wrote: > >>> On Sun 29 Aug 08:47 PDT 2021, Dmitry Baryshkov wrote: > >>> > >>>> Now as the common qcom clock controller code has been taught about p= ower > >>>> domains, stop mentioning mmcx supply as a way to power up the clock > >>>> controller's gdsc. > >>>> > >>>> Signed-off-by: Dmitry Baryshkov > >>>> Reviewed-by: Bjorn Andersson > >>> > >>> Once we merge these, I expect that the boards will start crashing if > >>> the kernel is booted using an existing DTB? > >>> > >>> Is it okay to just merge the first 6 patches in the series now and > >>> postpone these two until we've had the dts change sitting for a while? > >> > >> Sure it is. > >> > >=20 > > What's the merge strategy? It goes through arm-soc? >=20 > I think this should go through the clk tree. There is little chance of=20 > conflicts. >=20 >=20 Ok. So I take the first 6 through clk tree and then we wait for the last two?