From: Francesco Dolcini <francesco@dolcini.it>
To: Nishanth Menon <nm@ti.com>, Jayesh Choudhary <j-choudhary@ti.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] arm64: dts: ti: k3-am62p: Enable AUDIO_REFCLKx
Date: Fri, 7 Feb 2025 09:33:01 +0100 [thread overview]
Message-ID: <Z6XFPYaj069fvW1h@gaggiata.pivistrello.it> (raw)
In-Reply-To: <20250207014239.xzm6rfnusckql2uo@litigator>
Hello Nishanth,
On Thu, Feb 06, 2025 at 07:42:39PM -0600, Nishanth Menon wrote:
> On 16:39-20250206, Francesco Dolcini wrote:
> > From: Francesco Dolcini <francesco.dolcini@toradex.com>
> >
> > On AM62P-based SoCs the AUDIO_REFCLKx clocks can be used as an input to
> > external peripherals when configured through CTRL_MMR, so add the
> > clock nodes.
> >
> > Link: http://downloads.ti.com/tisci/esd/latest/5_soc_doc/am62px/clocks.html
> > Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> > ---
> > arch/arm64/boot/dts/ti/k3-am62p-main.dtsi | 20 ++++++++++++++++++++
> > 1 file changed, 20 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/ti/k3-am62p-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62p-main.dtsi
> > index 420c77c8e9e5..4b47b0774330 100644
> > --- a/arch/arm64/boot/dts/ti/k3-am62p-main.dtsi
> > +++ b/arch/arm64/boot/dts/ti/k3-am62p-main.dtsi
> > @@ -42,6 +42,26 @@ &inta_main_dmss {
> > ti,interrupt-ranges = <5 69 35>;
> > };
> >
> > +&main_conf {
>
> Why not add it to main_conf section it self in the file?
The reason is that main_conf is defined in k3-am62p-j722s-common-main.dtsi,
that is shared between am62p and j722s.
On j722s the audio refclk is added in k3-j722s-main.dtsi the same way as I did
here, so I cannot move this to k3-am62p-j722s-common-main.dtsi without updating
also k3-j722s-main.dtsi.
I looked into the differences of j722s and am62p, and from my understanding,
from the audio refclk point of view, they are identical (same IP, same reg, same
clocks and same IDs), so this should naturally be moved to
k3-am62p-j722s-common-main.dtsi as you are suggesting.
... however, for some reason I am not aware of, on k3-j722s-main.dtsi a different
parent clock is used, and I cannot understand the reason. The actual parent clocks
in this patch are just the same we already have everywhere apart on j722s. I tried
to look at the history of this and it seems that on the TI downstream kernel branch
this is defined in the board dts file (!) and this confused me even more.
So, not wanting to break stuff I was not able to understand I came up with this
proposal.
An alternative could be to override the "unexpected" clocks from
k3-j722s-main.dtsi to the board dts file, and have the "standard" clocks, as
proposed in this patch and already used on all the other AM62 variants, in
k3-am62p-j722s-common-main.dtsi.
+Jayesh that is the author of this specific change in k3-j722s-main.dtsi.
Francesco
> > + audio_refclk0: clock-controller@82e0 {
> > + compatible = "ti,am62-audio-refclk";
> > + reg = <0x82e0 0x4>;
> > + clocks = <&k3_clks 157 0>;
> > + assigned-clocks = <&k3_clks 157 0>;
> > + assigned-clock-parents = <&k3_clks 157 16>;
> > + #clock-cells = <0>;
> > + };
> > +
> > + audio_refclk1: clock-controller@82e4 {
> > + compatible = "ti,am62-audio-refclk";
> > + reg = <0x82e4 0x4>;
> > + clocks = <&k3_clks 157 18>;
> > + assigned-clocks = <&k3_clks 157 18>;
> > + assigned-clock-parents = <&k3_clks 157 34>;
> > + #clock-cells = <0>;
> > + };
> > +};
> > +
next prev parent reply other threads:[~2025-02-07 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 15:39 [PATCH v1] arm64: dts: ti: k3-am62p: Enable AUDIO_REFCLKx Francesco Dolcini
2025-02-07 1:42 ` Nishanth Menon
2025-02-07 8:33 ` Francesco Dolcini [this message]
2025-02-28 12:43 ` Francesco Dolcini
2025-02-28 13:53 ` Nishanth Menon
2025-03-02 13:19 ` Vignesh Raghavendra
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=Z6XFPYaj069fvW1h@gaggiata.pivistrello.it \
--to=francesco@dolcini.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=j-choudhary@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=vigneshr@ti.com \
/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