Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: conor+dt@kernel.org, Frank.Li@kernel.org, robh@kernel.org,
	devicetree@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v2 2/4] arm64: dts: imx8qm-ss-audio: add spdif1 node
Date: Thu, 09 Jul 2026 20:41:05 +0000	[thread overview]
Message-ID: <20260709204105.850C91F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260709-qm_dts-v2-2-3ebcce82bb79@nxp.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The new clock controller node `spdif1_lpcg` is incorrectly marked with `status = "disabled";`. In i.MX8 device trees, LPCG (Local Peripheral Clock Gate) nodes provide clocks to hardware blocks and are intended to be enabled by default at the SoC level, as the clock framework automatically manages them. Setting `status = "disabled";` means the device node will not be instantiated by the OF core, and its platform driver (`imx8qxp-lpcg-clk`) will not probe. Consequently, when a board file enables `spdif1` (using `&spdif1 { status = "okay"; };`), the `spdif1` driver will fail to probe with a persistent `-EPROBE_DEFER` error because its required clock provider (`spdif1_lpcg`) is unavailable.
--

--- Patch [2]: [PATCH v2 2/4] arm64: dts: imx8qm-ss-audio: add spdif1 node ---
commit 5e80d17ca35f0e8c498b103cd29fc869f77a9125
Author: Frank Li <Frank.Li@nxp.com>
arm64: dts: imx8qm-ss-audio: add spdif1 node

This commit adds the spdif1 audio node and its corresponding local peripheral
clock gate (LPCG) node to the imx8qm-ss-audio device tree.

> diff --git a/arch/arm64/boot/dts/freescale/imx8qm-ss-audio.dtsi b/arch/arm64/boot/dts/freescale/imx8qm-ss-audio.dtsi
> --- a/arch/arm64/boot/dts/freescale/imx8qm-ss-audio.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8qm-ss-audio.dtsi
[ ... ]
> @@ -109,6 +134,19 @@ sai5: sai@59090000 {
>  		status = "disabled";
>  	};
>  
> +	spdif1_lpcg: clock-controller@59430000 {
> +		compatible = "fsl,imx8qxp-lpcg";
> +		reg = <0x59430000 0x10000>;
> +		#clock-cells = <1>;
> +		clocks = <&acm IMX_ADMA_ACM_SPDIF1_TX_CLK_SEL>,
> +			 <&audio_ipg_clk>;
> +		clock-indices = <IMX_LPCG_CLK_5>, <IMX_LPCG_CLK_4>;
> +		clock-output-names = "spdif1_lpcg_tx_clk",
> +				     "spdif1_lpcg_gclkw";
> +		power-domains = <&pd IMX_SC_R_SPDIF_1>;
> +		status = "disabled";

[Severity: Medium]
Will this cause a persistent probe deferral for spdif1?

Since LPCG nodes provide clocks to hardware blocks, they are typically enabled
by default at the SoC level so the clock framework can manage them. Setting
the status to disabled here means the clock provider won't probe unless a
board file explicitly enables it.

If a board file only enables spdif1, won't it fail to probe with -EPROBE_DEFER
because its required clock provider is unavailable?

> +	};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260709-qm_dts-v2-0-3ebcce82bb79@nxp.com?part=2

  reply	other threads:[~2026-07-09 20:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09 20:29 [PATCH v2 0/4] arm64: dts: imx8qm: collect some small update and fixes Frank.Li
2026-07-09 20:29 ` [PATCH v2 1/4] arm64: dts: imx8qm-ss-dma: add lpuart4 node Frank.Li
2026-07-09 20:29 ` [PATCH v2 2/4] arm64: dts: imx8qm-ss-audio: add spdif1 node Frank.Li
2026-07-09 20:41   ` sashiko-bot [this message]
2026-07-09 20:29 ` [PATCH v2 3/4] arm64: dts: imx8qm-ss-lsio: add lsio mu8 and mu8b Frank.Li
2026-07-09 20:29 ` [PATCH v2 4/4] arm64: dts: imx8-ss-audio: Fix LPCG clock indices for ASRC0 Frank.Li

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=20260709204105.850C91F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=Frank.Li@oss.nxp.com \
    --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