From: Nishanth Menon <nm@ti.com>
To: Santosh Shilimkar <ssantosh@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <kristo@kernel.org>,
Nishanth Menon <nm@ti.com>
Subject: [PATCH 4/4] ARM: dts: keystone: k2g-evm: Move audio oscillator assigned clock to mcasp
Date: Mon, 10 May 2021 09:43:12 -0500 [thread overview]
Message-ID: <20210510144312.986-5-nm@ti.com> (raw)
In-Reply-To: <20210510144312.986-1-nm@ti.com>
Setting assigned clock with a dependency on itself for k2g_clks
creates a circular dependency. Instead, Lets model the audio clock
as a assigned-clock configuration for mcasp and set it up as the
first clock assigned-clock to be satisfied. Following the standard
convention, we use null entries to indicate entries that doesn't need
to be programmed.
References:
[1] schematics: https://www.ti.com/lit/df/sprr302/sprr302.pdf
[2] TRM: https://www.ti.com/lit/ug/spruhy8i/spruhy8i.pdf
Signed-off-by: Nishanth Menon <nm@ti.com>
---
yaml fixup series:
https://lore.kernel.org/linux-arm-kernel/20210503190824.GA2192378@robh.at.kernel.org
Specific yaml:
https://lore.kernel.org/linux-arm-kernel/20210426155457.21221-3-nm@ti.com/
arch/arm/boot/dts/keystone-k2g-evm.dts | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/arch/arm/boot/dts/keystone-k2g-evm.dts b/arch/arm/boot/dts/keystone-k2g-evm.dts
index 14e26a4fd62a..d800f26b6275 100644
--- a/arch/arm/boot/dts/keystone-k2g-evm.dts
+++ b/arch/arm/boot/dts/keystone-k2g-evm.dts
@@ -544,20 +544,15 @@ dpi_out: endpoint {
};
};
-&k2g_clks {
- /* on the board 22.5792MHz is connected to AUDOSC_IN */
- assigned-clocks = <&k2g_clks 0x4c 2>;
- assigned-clock-rates = <22579200>;
-};
-
&mcasp2 {
#sound-dai-cells = <0>;
pinctrl-names = "default";
pinctrl-0 = <&mcasp2_pins>;
- assigned-clocks = <&k2g_clks 0x6 1>;
- assigned-clock-parents = <&k2g_clks 0x6 2>;
+ assigned-clocks = <&k2g_clks 0x4c 2>, <&k2g_clks 0x6 1>;
+ assigned-clock-parents = <0>, <&k2g_clks 0x6 2>;
+ assigned-clock-rates = <22579200>, <0>;
status = "okay";
--
2.31.0
next prev parent reply other threads:[~2021-05-10 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 14:43 [PATCH 0/4] ARM: dts: keystone: k2g: Update dts node for yaml Nishanth Menon
2021-05-10 14:43 ` [PATCH 1/4 RESEND] ARM: dts: keystone: k2g: Rename message-manager node Nishanth Menon
2021-05-10 14:43 ` [PATCH 2/4] ARM: dts: keystone: k2g: Rename the TI-SCI node Nishanth Menon
2021-05-10 14:43 ` [PATCH 3/4] ARM: dts: keystone: k2g: Rename the TI-SCI clocks node name Nishanth Menon
2021-05-10 14:43 ` Nishanth Menon [this message]
2021-05-11 7:16 ` [PATCH 0/4] ARM: dts: keystone: k2g: Update dts node for yaml Tero Kristo
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=20210510144312.986-5-nm@ti.com \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ssantosh@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).