Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp3909630imw; Mon, 18 Jul 2022 17:15:37 -0700 (PDT) X-Google-Smtp-Source: AGRyM1s3s1ZjPI7vuKsfoPE17kNmQC13A1udIcB4DgACDLISTuWdnZ53sU5sn7NvFxU70xZV76RC X-Received: by 2002:a17:907:7e87:b0:72b:4af3:bf57 with SMTP id qb7-20020a1709077e8700b0072b4af3bf57mr28417763ejc.9.1658189737636; Mon, 18 Jul 2022 17:15:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658189737; cv=none; d=google.com; s=arc-20160816; b=UWn+oX+Z6fTn4MYWmyYX5SIdYJYYXZ07Yu2pChdS6TEKmk1Q08VJKVh9lzMApVkiOg rhJJlwtI01DS5SfBqi42Xk/N51xlHuemeQrq0+fJmu11qWuiJiHb66Pyippuuz1i/0n6 Cz6N+0ar6RWEydpaae3SOHKmJ9dRmBy5S1yOElgu1cQTkujsaOKCwozASsn2pOAzxogE evekgJD1KBFv0we9gZ0uvK5QBHhoMRrUHL/NGG7eyFMNlaGvkAjsKJylAV4byMVE9kJr mr3NlouL+Nv9ZBkfHK80Gvg6aHPsSgpR5jffKHAQwCUPDd8E3i8sIsFOrkYXwKboYjk5 a0ag== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=pCnOpb/tAWKWPuLC7zFzL9Qy3rXC3raHyDODfytTBvo=; b=0UPGPoBKOtb1PAOe1B+COxoJUgLzCmEzNwFtu2RhO+mGsaD4z6HMkNMMkxaV9ldJXO vENN9LsaZP0CtwI7h8WXmQnbxm+Cj4sVwQAF+DOOCtmLvheKt0jYV3X+X2tFcpInpcgo KD40CuN4QxMAaceQjE4Hi4f10AfsrSUQcJbdFek8rPskMn8YVACNJ6SUgB58Df1gqB8z iJyQ1T2S+26bz+ezdUIXv9onuLHkneWuIZHXmWInhqGxkR+8mQqtqDnR7umu50K1Os/Z Kk83eZjpb/2kRwLdg6viAtv605WfJy6RLW7q2vPV2qYlMVymbN+KEkQ3hLLG7Wdc4eoe mulg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=R4AhdQij; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l21-20020a170906795500b0072b66c5cdb5si19192354ejo.519.2022.07.18.17.15.12; Mon, 18 Jul 2022 17:15:37 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=R4AhdQij; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236632AbiGSAM7 (ORCPT + 99 others); Mon, 18 Jul 2022 20:12:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47842 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236602AbiGSAMw (ORCPT ); Mon, 18 Jul 2022 20:12:52 -0400 Received: from mail-oa1-x30.google.com (mail-oa1-x30.google.com [IPv6:2001:4860:4864:20::30]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 306DE37F89 for ; Mon, 18 Jul 2022 17:12:51 -0700 (PDT) Received: by mail-oa1-x30.google.com with SMTP id 586e51a60fabf-f2a4c51c45so28216484fac.9 for ; Mon, 18 Jul 2022 17:12:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=pCnOpb/tAWKWPuLC7zFzL9Qy3rXC3raHyDODfytTBvo=; b=R4AhdQijFE22qPnuP8yQk+M/z15peEnGnkKXOCnjUdkAyL/8qYwcHUjbV158/lM6gk sOyavYbNdkIe+MD0G2ei2o1p0XnUtTA2n1crgGwCQOVlDSiuU1QNw148fxYCb2Hn2CZ5 00w5GIrzsUT6WALe+OkBqMLXZNrKjZXV/x8xQSScsq84JE0y1I8C2OxrD2HrX35UrIDS s/8jkY6F3XIMtaWX2O0R0XXeLtxRgzpwC9QLHT8YzHdbcbRJC6PQXYNlK3gb97tugHze EAd1IOnVRw6dG/2+z2/q8ET2qWYmUZRPaLYmdlIiPl1rxuoxhQgPNeLNoyKou+G0Hlbi KeVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=pCnOpb/tAWKWPuLC7zFzL9Qy3rXC3raHyDODfytTBvo=; b=MEH/RQtBbxALy8fzTAy8mWf7nl/CSqs1Q4jYw8wqp22EhT9wU2kVe6C7K7Ru8cLXmd dyURrr2y8qOxWKdffObZv/JzaY+iePuNlPrysd1Qk5owBjRsHYU2dkNG30eAWYQcYTOV Gtm9BKtmrG/b/5FzGzP1qDpkOoogNUBtJYUrS2prx1xb6epkWsLF+lh2AFfRnwbMXUYA 1CRJFJX+UYUmFhOiTmkrME1Vmi4NKLOS5fmzDKRYdt/HzML4J4zzZoGEtDBdYBFNyRPU 2/qj5vcSTXlB1Jaq2wWWo51x4ATziErYSNGuKViKUZMLPfdLgrSdj9bQVj/UTFnwWWUM fzSA== X-Gm-Message-State: AJIora+c3h0DS+adZc6Hs/4BkBtxei2gq/8IN6NIv3+eaoGTmlAYWW1N YCDp9UeD8SbcqvZxEanmAobRrvOZEmik5w== X-Received: by 2002:a05:6870:2423:b0:fe:4131:6db9 with SMTP id n35-20020a056870242300b000fe41316db9mr15575223oap.75.1658189570175; Mon, 18 Jul 2022 17:12:50 -0700 (PDT) Received: from builder.lan (104-57-184-186.lightspeed.austtx.sbcglobal.net. [104.57.184.186]) by smtp.gmail.com with ESMTPSA id n23-20020a056870559700b0010c727a3c79sm7214120oao.26.2022.07.18.17.12.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 Jul 2022 17:12:49 -0700 (PDT) Date: Mon, 18 Jul 2022 19:12:47 -0500 From: Bjorn Andersson To: Christian Marangi Cc: Andy Gross , Konrad Dybcio , Michael Turquette , Stephen Boyd , Rob Herring , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 4/4] clk: qcom: gcc-ipq806x: remove cc_register_board for pxo and cxo Message-ID: References: <20220706225321.26215-1-ansuelsmth@gmail.com> <20220706225321.26215-5-ansuelsmth@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220706225321.26215-5-ansuelsmth@gmail.com> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 06 Jul 17:53 CDT 2022, Christian Marangi wrote: > Now that these clock are defined as fixed clk in dts, we can drop the > register_board_clk for cxo_board and pxo_board in gcc_ipq806x_probe. > Are you trying to say, that now that we have .fw_name based lookup of these clocks we don't need the globally registered [cp]xo clocks to bridge towards the [cp]xo_board_clocks which was introduced in: 30fc4212d541 ("arm: dts: qcom: Add more board clocks") I think this change would work out if you also replace .name = "pxo" with .name = "pxo_board_clk" (and same for cxo)... But I don't think we can just drop these, as it would break compatibility with existing devicetree. Regards, Bjorn > Signed-off-by: Christian Marangi > --- > drivers/clk/qcom/gcc-ipq806x.c | 8 -------- > 1 file changed, 8 deletions(-) > > diff --git a/drivers/clk/qcom/gcc-ipq806x.c b/drivers/clk/qcom/gcc-ipq806x.c > index 718de17a1e60..883629de2751 100644 > --- a/drivers/clk/qcom/gcc-ipq806x.c > +++ b/drivers/clk/qcom/gcc-ipq806x.c > @@ -3384,14 +3384,6 @@ static int gcc_ipq806x_probe(struct platform_device *pdev) > struct regmap *regmap; > int ret; > > - ret = qcom_cc_register_board_clk(dev, "cxo_board", "cxo", 25000000); > - if (ret) > - return ret; > - > - ret = qcom_cc_register_board_clk(dev, "pxo_board", "pxo", 25000000); > - if (ret) > - return ret; > - > if (of_machine_is_compatible("qcom,ipq8065")) { > ubi32_core1_src_clk.freq_tbl = clk_tbl_nss_ipq8065; > ubi32_core2_src_clk.freq_tbl = clk_tbl_nss_ipq8065; > -- > 2.36.1 >