From: sashiko-bot@kernel.org
To: "Neil Armstrong" <neil.armstrong@linaro.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/4] arm64: dts: qcom: sm8450-hdk: Enable I2S for HDMI
Date: Tue, 28 Jul 2026 09:10:11 +0000 [thread overview]
Message-ID: <20260728091012.419DA1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260728-topic-sm8x50-next-hdk-i2s-v1-2-2393a0fe4aa9@linaro.org>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Device Tree Misconfiguration - Pinctrl for SoC I2S interface is incorrectly assigned to the external HDMI bridge node.
- [Low] DT Schema Violation - Invalid clock-names order for dai@16.
--
--- Patch [2]: [PATCH 2/4] arm64: dts: qcom: sm8450-hdk: Enable I2S for HDMI ---
commit bf4f513e744f0c756ca7054358cd98929fb84150
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
the I2S interface for HDMI audio output on the SM8450-HDK board. It configures
the pinctrl for I2S, sets up the q6apmbedai DAI, and adds the primary MI2S DAI
link.
> diff --git a/arch/arm64/boot/dts/qcom/sm8450-hdk.dts b/arch/arm64/boot/dts/qcom/sm8450-hdk.dts
> index b37998cd9a2c3..6a6d8346046bd 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 = <<9611_3v3>;
>
> pinctrl-names = "default";
> - pinctrl-0 = <<9611_irq_pin <9611_rst_pin>;
> + pinctrl-0 = <<9611_irq_pin>,
> + <<9611_rst_pin>,
> + <&i2s0_default_state>,
> + <&audio_mclk0_default_state>;
[Severity: Medium]
Should the SoC I2S and MCLK pin states be assigned to the sound node or CPU
DAI instead of the external HDMI bridge node?
By assigning these to the lt9611_codec node, the SoC's audio pin multiplexing
is tied to the lifecycle of the external display bridge. If the HDMI bridge
driver defers or unloads, the SoC I2S pins will revert to their unconfigured
state, which breaks the hardware description paradigm and might cause runtime
audio issues.
> +
> + #sound-dai-cells = <1>;
>
> ports {
> #address-cells = <1>;
[ ... ]
> @@ -947,6 +952,19 @@ channel@44b {
> };
> };
>
> +&q6apmbedai {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + dai@16 {
> + reg = <PRIMARY_MI2S_RX>;
> + clocks = <&q6prmcc LPASS_CLK_ID_MCLK_1 LPASS_CLK_ATTRIBUTE_COUPLE_NO>,
> + <&q6prmcc LPASS_CLK_ID_PRI_MI2S_IBIT LPASS_CLK_ATTRIBUTE_COUPLE_NO>;
> + clock-names = "mclk",
> + "bclk";
[Severity: Low]
Is this clock-names order correct according to the schema?
The qcom,q6apm-lpass-dais.yaml schema requires that if two clocks are
provided, they must be ordered such that index 1 is mclk. Here, bclk is at
index 1, which will cause make dtbs_check validation to fail.
> + };
> +};
> +
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260728-topic-sm8x50-next-hdk-i2s-v1-0-2393a0fe4aa9@linaro.org?part=2
next prev parent reply other threads:[~2026-07-28 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 8:53 [PATCH 0/4] ASoC: qcom: allow SM[456]50 HDK board to play audio via I2S Neil Armstrong
2026-07-28 8:53 ` [PATCH 1/4] ASoC: qcom: sc8280xp: allow setting m2is clocks for SM8[456]50 boards Neil Armstrong
2026-07-28 8:53 ` [PATCH 2/4] arm64: dts: qcom: sm8450-hdk: Enable I2S for HDMI Neil Armstrong
2026-07-28 9:10 ` sashiko-bot [this message]
2026-07-28 9:34 ` Neil Armstrong
2026-07-28 8:53 ` [PATCH 3/4] arm64: dts: qcom: sm8550-hdk: " Neil Armstrong
2026-07-28 9:05 ` sashiko-bot
2026-07-28 8:53 ` [PATCH 4/4] arm64: dts: qcom: sm8650-hdk: " Neil Armstrong
2026-07-28 9:06 ` sashiko-bot
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=20260728091012.419DA1F000E9@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