Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Neil Armstrong" <neil.armstrong@linaro.org>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/3] arm64: dts: qcom: sm8450-hdk: Enable I2S for HDMI
Date: Wed, 05 Aug 2026 07:59:25 +0000	[thread overview]
Message-ID: <20260805075925.D09111F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260805-topic-sm8x50-next-hdk-i2s-v3-1-07a6483c430f@linaro.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Device Tree topological violation: SoC I2S and MCLK pinctrl states are incorrectly assigned to an external I2C codec node.
--

--- Patch [1]: [PATCH v3 1/3] arm64: dts: qcom: sm8450-hdk: Enable I2S for HDMI ---
commit 1e06799a0230632b985134cd0731cc4a2e53b31d
Author: Neil Armstrong <neil.armstrong@linaro.org>

arm64: dts: qcom: sm8450-hdk: Enable I2S for HDMI

This commit adds the necessary Device Tree nodes and configurations to enable
I2S audio output via the DSI HDMI bridge on the SM8450 HDK. It defines the
audio clock and pin configurations, links the DAI components, and assigns
the pinctrl states to the HDMI bridge node.

> diff --git a/arch/arm64/boot/dts/qcom/sm8450-hdk.dts b/arch/arm64/boot/dts/qcom/sm8450-hdk.dts
> index b37998cd9a2c3..6bc2e8630dc37 100644
> --- a/arch/arm64/boot/dts/qcom/sm8450-hdk.dts
> +++ b/arch/arm64/boot/dts/qcom/sm8450-hdk.dts
> @@ -665,7 +665,12 @@ lt9611_codec: hdmi-bridge@2b {
>  		vcc-supply = <&lt9611_3v3>;
>  
>  		pinctrl-names = "default";
> -		pinctrl-0 = <&lt9611_irq_pin &lt9611_rst_pin>;
> +		pinctrl-0 = <&lt9611_irq_pin>,
> +			    <&lt9611_rst_pin>,
> +			    <&i2s0_default_state>,
> +			    <&audio_mclk0_default_state>;

[Severity: Low]
Are the SoC's I2S and MCLK pinctrl states being assigned to the correct
node here?

These pins belong to the host SoC and are driven by its audio controller,
rather than the external LT9611 HDMI bridge. Assigning the SoC's pin
configuration to the external bridge's node makes the codec driver
responsible for configuring the host SoC's hardware, which seems to cross
topological boundaries in the Device Tree.

Should these pins be assigned to the sound card node or the CPU DAI node
instead?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260805-topic-sm8x50-next-hdk-i2s-v3-0-07a6483c430f@linaro.org?part=1

  reply	other threads:[~2026-08-05  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  7:48 [PATCH v3 0/3] ASoC: qcom: allow SM[456]50 HDK board to play audio via I2S Neil Armstrong
2026-08-05  7:48 ` [PATCH v3 1/3] arm64: dts: qcom: sm8450-hdk: Enable I2S for HDMI Neil Armstrong
2026-08-05  7:59   ` sashiko-bot [this message]
2026-08-05  8:04     ` Neil Armstrong
2026-08-05  7:48 ` [PATCH v3 2/3] arm64: dts: qcom: sm8550-hdk: " Neil Armstrong
2026-08-05  7:48 ` [PATCH v3 3/3] arm64: dts: qcom: sm8650-hdk: " Neil Armstrong

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=20260805075925.D09111F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=neil.armstrong@linaro.org \
    --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