From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
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
Date: Mon, 18 Jul 2022 19:12:47 -0500 [thread overview]
Message-ID: <YtX2///aNWyhKpJn@builder.lan> (raw)
In-Reply-To: <20220706225321.26215-5-ansuelsmth@gmail.com>
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 <ansuelsmth@gmail.com>
> ---
> 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
>
next prev parent reply other threads:[~2022-07-19 0:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 22:53 [PATCH v2 0/4] clk: qcom: Drop use of pxo/cxo_board for rpm devices Christian Marangi
2022-07-06 22:53 ` [PATCH v2 1/4] dt-bindings: clock: fix wrong clock documentation for qcom,rpmcc Christian Marangi
2022-07-11 19:08 ` Rob Herring
2022-07-06 22:53 ` [PATCH v2 2/4] ARM: DTS: qcom: add rpmcc missing clocks for apq/ipq8064 and msm8660 Christian Marangi
2022-07-06 22:53 ` [PATCH v2 3/4] clk: qcom: clk-rpm: convert to parent_data API Christian Marangi
2022-07-06 22:53 ` [PATCH v2 4/4] clk: qcom: gcc-ipq806x: remove cc_register_board for pxo and cxo Christian Marangi
2022-07-19 0:12 ` Bjorn Andersson [this message]
2022-07-19 1:40 ` Christian Marangi
2022-07-19 4:47 ` (subset) [PATCH v2 0/4] clk: qcom: Drop use of pxo/cxo_board for rpm devices Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YtX2///aNWyhKpJn@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox