From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: imx@lists.linux.dev, robh@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v8 2/3] ARM: dts: imx7d: add Variscite VAR-SOM-MX7 support
Date: Tue, 1 Sep 2026 01:14:44 +0200 [thread overview]
Message-ID: <apYK5AIXkEnDYEHV@GLaDOS.station> (raw)
In-Reply-To: <20260831231042.59BBF1F000E9@smtp.kernel.org>
On Mon, Aug 31, 2026 at 11:10:41PM +0000, sashiko-bot@kernel.org wrote:
>
> > diff --git a/arch/arm/boot/dts/nxp/imx/imx7d-var-som-wm8904.dtsi b/arch/arm/boot/dts/nxp/imx/imx7d-var-som-wm8904.dtsi
> > new file mode 100644
> > index 0000000000000..b56f3680edcff
> > --- /dev/null
> > +++ b/arch/arm/boot/dts/nxp/imx/imx7d-var-som-wm8904.dtsi
> [ ... ]
> > @@ -0,0 +1,118 @@
> [ ... ]
> > +&i2c2 {
> > + wm8904: audio-codec@1a {
> > + compatible = "wlf,wm8904";
> > + reg = <0x1a>;
> > + #sound-dai-cells = <0>;
> > + clocks = <&clks IMX7D_AUDIO_MCLK_ROOT_DIV>;
>
> [Severity: Medium]
> Does this code assign the wrong clock to the wm8904 codec's mclk?
>
> The codec is configured to use IMX7D_AUDIO_MCLK_ROOT_DIV, but shouldn't this
> point to the clock actually driving the MCLK pad (such as
> IMX7D_SAI1_ROOT_CLK)?
>
> If the driver queries the frequency of this incorrect clock tree node (which
> defaults to 24MHz) instead of the actual 12.288MHz rate driven by the SAI1
> pad, it may miscalculate its internal PLL/FLL configuration.
>
> Could this result in incorrect audio playback speeds or a failure to lock
> the FLL when the audio subsystem initializes?
>
This is intentional. The WM8904 MCLK is provided by the dedicated audio
MCLK root, while the SAI1 root clock is configured separately for the
SAI interface.
The fact that the pad is muxed as SAI1_MCLK does not imply that the
codec clock provider must be IMX7D_SAI1_ROOT_CLK.
This configuration has been validated on the hardware.
Stefano
next prev parent reply other threads:[~2026-08-31 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 22:55 [PATCH v8 0/3] Add support for Variscite VAR-SOM-MX7 and MX7CustomBoard Stefano Radaelli
2026-08-31 22:55 ` [PATCH v8 1/3] dt-bindings: arm: fsl: add Variscite VAR-SOM-MX7 boards Stefano Radaelli
2026-08-31 22:55 ` [PATCH v8 2/3] ARM: dts: imx7d: add Variscite VAR-SOM-MX7 support Stefano Radaelli
2026-08-31 23:10 ` sashiko-bot
2026-08-31 23:14 ` Stefano Radaelli [this message]
2026-08-31 22:55 ` [PATCH v8 3/3] ARM: dts: imx7d: add Variscite MX7CustomBoard support Stefano Radaelli
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=apYK5AIXkEnDYEHV@GLaDOS.station \
--to=stefano.radaelli21@gmail.com \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imx@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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