From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Rudraksha Gupta <guptarud@gmail.com>
Cc: agross@kernel.org, david@ixit.cz, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v2 1/2] ARM: msm8960: Rename cxo_board to cxo-board and add alias
Date: Wed, 10 Aug 2022 12:53:45 -0700 [thread overview]
Message-ID: <YvQMyQLohqcc8Fug@ripper> (raw)
In-Reply-To: <20220809000300.6384-1-guptarud@gmail.com>
On Mon 08 Aug 17:02 PDT 2022, Rudraksha Gupta wrote:
> This patch renames cxo_board to be up to date with the current naming
> style. It also adds an alias.
>
> Signed-off-by: Rudraksha Gupta <guptarud@gmail.com>
> ---
> v2:
> - Group the correct changes together
>
> arch/arm/boot/dts/qcom-msm8960.dtsi | 2 +-
> drivers/clk/qcom/gcc-msm8960.c | 2 +-
Clock and dts patches goes through two different paths towards mainline,
so they should be separated.
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/boot/dts/qcom-msm8960.dtsi b/arch/arm/boot/dts/qcom-msm8960.dtsi
> index 0e099aa7c889..2ed969785b78 100644
> --- a/arch/arm/boot/dts/qcom-msm8960.dtsi
> +++ b/arch/arm/boot/dts/qcom-msm8960.dtsi
> @@ -58,7 +58,7 @@ cpu-pmu {
> };
>
> clocks {
> - cxo_board {
> + cxo_board: cxo-board {
> compatible = "fixed-clock";
> #clock-cells = <0>;
> clock-frequency = <19200000>;
> diff --git a/drivers/clk/qcom/gcc-msm8960.c b/drivers/clk/qcom/gcc-msm8960.c
> index 051745ef99c8..56ce05a846dd 100644
> --- a/drivers/clk/qcom/gcc-msm8960.c
> +++ b/drivers/clk/qcom/gcc-msm8960.c
> @@ -3624,7 +3624,7 @@ static int gcc_msm8960_probe(struct platform_device *pdev)
> if (!match)
> return -EINVAL;
>
> - ret = qcom_cc_register_board_clk(dev, "cxo_board", "cxo", 19200000);
> + ret = qcom_cc_register_board_clk(dev, "cxo-board", "cxo", 19200000);
This breaks compatibility with existing DTB files.
What you probably want is to make sure that any clocks with parent name
of "cxo", should have a .fw_name = "cxo", then you can make a
phandle-based reference in DT and these global names doesn't matter (and
in the end we can remove this board_clk from the driver).
Regards,
Bjorn
> if (ret)
> return ret;
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-08-10 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 23:47 [PATCH 1/2] ARM: msm8960: Rename cxo_board to cxo-board and add alias Rudraksha Gupta
2022-08-08 23:47 ` [PATCH 2/2] ARM: msm8960: Add Samsung Galaxy Express support Rudraksha Gupta
2022-08-09 0:02 ` [PATCH v2 1/2] ARM: msm8960: Rename cxo_board to cxo-board and add alias Rudraksha Gupta
2022-08-09 0:03 ` [PATCH v2 2/2] ARM: msm8960: Add Samsung Galaxy Express support Rudraksha Gupta
2022-08-09 5:35 ` Krzysztof Kozlowski
2022-08-09 23:57 ` Rudraksha Gupta
2022-08-10 7:47 ` Krzysztof Kozlowski
2022-08-09 5:32 ` [PATCH v2 1/2] ARM: msm8960: Rename cxo_board to cxo-board and add alias Krzysztof Kozlowski
2022-08-10 19:53 ` Bjorn Andersson [this message]
2022-08-11 2:51 ` Rudraksha Gupta
2022-08-29 21:54 ` Bjorn Andersson
2023-02-21 6:40 ` Rudraksha Gupta
2022-08-09 5:30 ` [PATCH " Krzysztof Kozlowski
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=YvQMyQLohqcc8Fug@ripper \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=guptarud@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).