From: Francesco Dolcini <francesco@dolcini.it>
To: Nishanth Menon <nm@ti.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Jai Luthra <j-luthra@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v1 1/4] arm64: dts: ti: k3-am62x: Enable AUDIO_REFCLKx
Date: Wed, 2 Aug 2023 15:41:03 +0200 [thread overview]
Message-ID: <ZMpc7x8U91JLVakd@francesco-nb.int.toradex.com> (raw)
In-Reply-To: <20230802133244.b66pg3mztotgqotm@steerable>
On Wed, Aug 02, 2023 at 08:32:44AM -0500, Nishanth Menon wrote:
> On 13:37-20230802, Francesco Dolcini wrote:
> > Il 2 agosto 2023 13:23:50 CEST, Jai Luthra <j-luthra@ti.com> ha scritto:
> > >On Jul 31, 2023 at 16:21:32 +0200, Francesco Dolcini wrote:
> > >> From: Jai Luthra <j-luthra@ti.com>
> > >>
> > >> On AM62-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.
> > >>
> > >> Signed-off-by: Jai Luthra <j-luthra@ti.com>
> > >> Signed-off-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> > >> ---
> > >> arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 18 ++++++++++++++++++
> > >> arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 18 ++++++++++++++++++
> > >
> > >Given currently none of the AM62A boards are using the refclks, can you
> > >drop those or just mark the nodes as disabled. Whoever is the first user
> > >can enable them.
> >
> > I can drop the 2 clocks from AM62A, however, should we really do it?
> > These clocks exist and they are just defined in the DTS, they are
> > not going to be enabled if not used, "ti,am62-epwm-tbclk" is also
> > not disabled for example.
>
> Overall, the SoC clock as such has nothing to do with board specific, so
> leave it default (enabled) in SoC.dts - just want to make sure that the
> clk-parent selection doesn't get in the way of platforms and is a sane
> default.
When I looked into that, months ago, this looked to me the correct and a
sane default. I had the same in our downstream way before the addition
from Jai Luthra to the SoC dtsi.
Not sure if Jai can add more on that regard.
> pll2_hsdiv8 output - which looks like the default mux value anyways..
> I am ok for it being explicit, but wondering if that works for boards
> that do not use this default.
IFF needed, it would be very easy to just override from the board dts,
using the labels that are already there (audio_refclk0, audio_refclk1).
> (sidenote): Fransesco - your new mail client has line wrap issues ;)
Yep, I had the crazy idea to reply from my mobile phone while having a
walk. It's already a success that I did not top post ;-)
Francesco
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-02 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 14:21 [PATCH v1 0/4] arm64: dts: ti: Enable Audio on Verdin AM62 Francesco Dolcini
2023-07-31 14:21 ` [PATCH v1 1/4] arm64: dts: ti: k3-am62x: Enable AUDIO_REFCLKx Francesco Dolcini
2023-08-02 11:23 ` Jai Luthra
2023-08-02 11:37 ` Francesco Dolcini
2023-08-02 13:32 ` Nishanth Menon
2023-08-02 13:41 ` Francesco Dolcini [this message]
2023-08-02 14:00 ` Nishanth Menon
2023-08-03 5:58 ` Jai Luthra
2023-07-31 14:21 ` [PATCH v1 2/4] arm64: dts: ti: verdin-am62: Set I2S_1 MCLK rate Francesco Dolcini
2023-08-02 11:16 ` Jai Luthra
2023-07-31 14:21 ` [PATCH v1 3/4] arm64: dts: ti: verdin-am62: dev: add sound card Francesco Dolcini
2023-08-02 11:17 ` Jai Luthra
2023-07-31 14:21 ` [PATCH v1 4/4] arm64: dts: ti: verdin-am62: dahlia: " Francesco Dolcini
2023-08-02 11:18 ` Jai Luthra
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=ZMpc7x8U91JLVakd@francesco-nb.int.toradex.com \
--to=francesco@dolcini.it \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=j-luthra@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@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