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 X-Spam-Level: X-Spam-Status: No, score=-11.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0DB64C4320E for ; Wed, 1 Sep 2021 05:35:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DF5F061059 for ; Wed, 1 Sep 2021 05:35:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242025AbhIAFgy (ORCPT ); Wed, 1 Sep 2021 01:36:54 -0400 Received: from mail.kernel.org ([198.145.29.99]:36394 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233857AbhIAFgx (ORCPT ); Wed, 1 Sep 2021 01:36:53 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 7A69260F3A; Wed, 1 Sep 2021 05:35:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1630474557; bh=ksxPtNuYubbYJ6aEkWBWuzz8xHMdSYMscQIeT1im6IA=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=Ty0GJFSIcWgaBeKRXN4/6uAX4nYak0fxSLv9YsiCxQrOq79+KbqEd0zoNVkXvrZKS JHMUw+A2yt9SQuGiKpyKsZsfmXtWCPSolx5ojWtH2vkpV41ivnNuLOXPQBKdu6mMJk ctQFh2ju314ODOaTNG8f/rA20CAvCg55lT/BiD/wQiSX1GUJBX2vbT8HF1duftd5uV p9Od94iKZ66AHJ5UlKSWx+d5oRkSMiRiJcMsgV1pRMIkWS0jiGoHE5B5R5lpDFRKGw Hkcv8Ct2redDoA3wyGoP/1zbLDd/Yar5oewZM4lzlyOekLtVrhsdbP9mp50h7KzKL+ 9ZpRfmlhFXuWQ== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20210830182445.167527-3-marijn.suijten@somainline.org> References: <20210830182445.167527-1-marijn.suijten@somainline.org> <20210830182445.167527-3-marijn.suijten@somainline.org> Subject: Re: [PATCH v2 2/2] clk: qcom: gcc-sdm660: Remove transient global "xo" clock From: Stephen Boyd Cc: ~postmarketos/upstreaming@lists.sr.ht, AngeloGioacchino Del Regno , Konrad Dybcio , Martin Botka , Jami Kettunen , Pavel Dubrova , Marijn Suijten , Andy Gross , Michael Turquette , Rob Clark , Sean Paul , David Airlie , Daniel Vetter , Dmitry Baryshkov , Abhinav Kumar , Jonathan Marek , Matthias Kaehlcke , Douglas Anderson , linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org To: Bjorn Andersson , Marijn Suijten , linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org Date: Tue, 31 Aug 2021 22:35:56 -0700 Message-ID: <163047455623.42057.15513441659841056105@swboyd.mtv.corp.google.com> User-Agent: alot/0.9.1 Precedence: bulk List-ID: X-Mailing-List: phone-devel@vger.kernel.org Quoting Marijn Suijten (2021-08-30 11:24:45) > The DSI PHY/PLL was relying on a global "xo" clock to be found, but the > real clock is named "xo_board" in the DT. The standard nowadays is to > never use global clock names anymore but require the firmware (DT) to > provide every clock binding explicitly with .fw_name. The DSI PLLs have > since been converted to this mechanism (specifically 14nm for SDM660) > and this transient clock can now be removed. >=20 > This issue was originally discovered in: > https://lore.kernel.org/linux-arm-msm/386db1a6-a1cd-3c7d-a88e-dc83f8a1be9= 6@somainline.org/ > and prevented the removal of "xo" at that time. >=20 > Signed-off-by: Marijn Suijten > --- Presumably this wants to go with the first one. Acked-by: Stephen Boyd