From: "André Draszik" <andre.draszik@linaro.org>
To: tudor.ambarus@linaro.org
Cc: alim.akhtar@samsung.com, conor+dt@kernel.org,
devicetree@vger.kernel.org, kernel-team@android.com,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
mturquette@baylibre.com, peter.griffin@linaro.org,
robh+dt@kernel.org, robh@kernel.org, semen.protsenko@linaro.org
Subject: Re: [PATCH 2/2] arm64: dts: exynos: gs101: comply with the new cmu_misc clock names
Date: Thu, 21 Dec 2023 17:22:15 +0000 [thread overview]
Message-ID: <aa2991470dfb8fb2e80892d62538d0c75444e6c9.camel@linaro.org> (raw)
In-Reply-To: <20231221090046.1486195-2-tudor.ambarus@linaro.org>
Hi Tudor,
> diff --git a/arch/arm64/boot/dts/exynos/google/gs101.dtsi b/arch/arm64/boot/dts/exynos/google/gs101.dtsi
> index 9747cb3fa03a..d838e3a7af6e 100644
> --- a/arch/arm64/boot/dts/exynos/google/gs101.dtsi
> +++ b/arch/arm64/boot/dts/exynos/google/gs101.dtsi
> @@ -289,7 +289,7 @@ cmu_misc: clock-controller@10010000 {
> #clock-cells = <1>;
> clocks = <&cmu_top CLK_DOUT_CMU_MISC_BUS>,
> <&cmu_top CLK_DOUT_CMU_MISC_SSS>;
> - clock-names = "dout_cmu_misc_bus", "dout_cmu_misc_sss";
> + clock-names = "bus", "sss";
> };
>
With this change, parent clock enablement fails, and we get:
exynos_arm64_register_cmu: could not enable bus clock dout_cmu_misc_bus; err = -2
during boot.
Cheers,
Andre'
next prev parent reply other threads:[~2023-12-21 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 9:00 [PATCH 1/2] dt-bindings: clock: gs101: rename cmu_misc clock-names Tudor Ambarus
2023-12-21 9:00 ` [PATCH 2/2] arm64: dts: exynos: gs101: comply with the new cmu_misc clock names Tudor Ambarus
2023-12-21 17:22 ` André Draszik [this message]
2023-12-21 17:23 ` Tudor Ambarus
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=aa2991470dfb8fb2e80892d62538d0c75444e6c9.camel@linaro.org \
--to=andre.draszik@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peter.griffin@linaro.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=tudor.ambarus@linaro.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).