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 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 0F67FC433FE for ; Tue, 14 Sep 2021 21:42:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id DA84661216 for ; Tue, 14 Sep 2021 21:42:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234814AbhINVn2 (ORCPT ); Tue, 14 Sep 2021 17:43:28 -0400 Received: from mail.kernel.org ([198.145.29.99]:46052 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235254AbhINVnW (ORCPT ); Tue, 14 Sep 2021 17:43:22 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id B8BAA60698; Tue, 14 Sep 2021 21:42:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1631655724; bh=/9zvCYmhpKsjctl8Uei7H0W4BGaIwrqgfEUwdmMavg4=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=esuDjulOQAI6+OJIRR70mHUlM3rsGQEg6/u2hRdjFtFSCNQycZ/FGI95rx03YXRv9 tsD4wyeGjsHcUiFhBMpI18fElWt0QDvvaMdBB9DuZyL7qYGZNnNix9tHqvlubxHaAm V5/yDtsz6cFdfVSHUKHdEq1Ib7Vkezy936BiCkKbgPZ3sCUHl7erfnCMs7tyg/2zJD uggodyEOWsPUzfNCcigs3mX4E5scNOOMajcRlmsTcm4lExoEQT39f4i+d2FIcYpg8S RVRW93w7ICOSchjeG6Om1H6G+JJByZC6FfuT3fUs3sukmfC52Kk5PcsewTbeYjDvgk mO1AKbo/kDiww== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20210911121340.261920-4-marijn.suijten@somainline.org> References: <20210911121340.261920-1-marijn.suijten@somainline.org> <20210911121340.261920-4-marijn.suijten@somainline.org> Subject: Re: [PATCH 3/8] clk: qcom: gcc-msm8998: Remove transient global "xo" clock From: Stephen Boyd Cc: ~postmarketos/upstreaming@lists.sr.ht, AngeloGioacchino Del Regno , Konrad Dybcio , Martin Botka , Jami Kettunen , Marijn Suijten , Andy Gross , Bjorn Andersson , Michael Turquette , Rob Herring , Taniya Das , linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org To: Marijn Suijten , phone-devel@vger.kernel.org Date: Tue, 14 Sep 2021 14:42:03 -0700 Message-ID: <163165572360.763609.9790931243080849652@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-09-11 05:13:35) > Now that all clock controllers and the DSI PLL clocks rely on "xo" being > passed in DT as phandle instead of looking it up by the global "xo" name > this transient clock can be removed, leaving only the fixed-factor > "xo_board" clock in DT. >=20 > Reviewed-by: AngeloGioacchino Del Regno > Signed-off-by: Marijn Suijten > --- Applied to clk-next