From: Siarhei Volkau <lis8215@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Siarhei Volkau <lis8215@gmail.com>,
Paul Cercueil <paul@crapouillou.net>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mips@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org
Subject: [PATCH 2/2] MIPS: ingenic: rs90: set MMC_MUX clock
Date: Tue, 8 Nov 2022 07:53:00 +0300 [thread overview]
Message-ID: <20221108045300.2084671-3-lis8215@gmail.com> (raw)
In-Reply-To: <20221108045300.2084671-1-lis8215@gmail.com>
Since the MMC driver can't change the common MMC_MUX clock
anymore, the CGU shall configure that clock properly.
Signed-off-by: Siarhei Volkau <lis8215@gmail.com>
---
arch/mips/boot/dts/ingenic/rs90.dts | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/mips/boot/dts/ingenic/rs90.dts b/arch/mips/boot/dts/ingenic/rs90.dts
index e8df70dd4..d874abaa6 100644
--- a/arch/mips/boot/dts/ingenic/rs90.dts
+++ b/arch/mips/boot/dts/ingenic/rs90.dts
@@ -295,8 +295,9 @@ partition@20000 {
&cgu {
/* Use 32kHz oscillator as the parent of the RTC clock */
- assigned-clocks = <&cgu JZ4725B_CLK_RTC>;
- assigned-clock-parents = <&cgu JZ4725B_CLK_OSC32K>;
+ assigned-clocks = <&cgu JZ4725B_CLK_MMC_MUX>, <&cgu JZ4725B_CLK_RTC>;
+ assigned-clock-parents = <0>, <&cgu JZ4725B_CLK_OSC32K>;
+ assigned-clock-rates = <48000000>;
};
&tcu {
--
2.36.1
prev parent reply other threads:[~2022-11-08 4:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 4:52 [PATCH 0/2] mmc: jz4740: Don't change parent clock rate for some SoCs Siarhei Volkau
2022-11-08 4:52 ` [PATCH 1/2] " Siarhei Volkau
2022-11-18 8:45 ` Ulf Hansson
2022-11-18 9:27 ` Paul Cercueil
2022-11-18 9:51 ` Siarhei Volkau
2022-11-18 10:06 ` Ulf Hansson
2022-11-18 12:48 ` Siarhei Volkau
2022-11-18 13:04 ` Paul Cercueil
2022-11-18 13:14 ` Paul Cercueil
2022-11-18 14:18 ` Aidan MacDonald
2022-11-08 4:53 ` Siarhei Volkau [this message]
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=20221108045300.2084671-3-lis8215@gmail.com \
--to=lis8215@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=paul@crapouillou.net \
--cc=robh+dt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=ulf.hansson@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).