Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stefano Radaelli" <stefano.radaelli21@gmail.com>
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: Mon, 31 Aug 2026 23:10:41 +0000	[thread overview]
Message-ID: <20260831231042.59BBF1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <7a3aa8bc7d4613998904db4fbbae03d213c6c30d.1788184274.git.stefano.r@variscite.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `wm8904` codec references an unconfigured and incorrect clock (`IMX7D_AUDIO_MCLK_ROOT_DIV`) instead of the actual physical clock providing its MCLK.
--

commit 1b158b02c4e2ef7937d25acb3234a66676fd29b6
Author: Stefano Radaelli <stefano.r@variscite.com>
Subject: ARM: dts: imx7d: add Variscite VAR-SOM-MX7 support

This commit adds device tree support for the Variscite VAR-SOM-MX7 system
on module. It introduces the common SoM description along with support for
eMMC, NAND, WM8731, WM8904, and the V2 hardware revision.

Link: https://variscite.com/system-on-module-som/i-mx-7/var-som-mx7/

> 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?

> +		clock-names = "mclk";
> +		AVDD-supply = <&vgen6_reg>;
> +		CPVDD-supply = <&vgen6_reg>;
[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1788184274.git.stefano.r@variscite.com?part=2

  reply	other threads:[~2026-08-31 23:10 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 [this message]
2026-08-31 23:14     ` Stefano Radaelli
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=20260831231042.59BBF1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --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 \
    --cc=stefano.radaelli21@gmail.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