Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Igor Paunovic" <royalnet026@gmail.com>
Cc: media-ci@linuxtv.org, robh@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v4 3/4] arm64: dts: rockchip: add HDMI RX audio on RK3588
Date: Tue, 21 Jul 2026 06:54:15 +0000	[thread overview]
Message-ID: <20260721065415.B67001F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260721064115.64809-4-royalnet026@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but the DAPM widget for the HDMI RX capture source is incorrectly defined as an OUTPUT widget, breaking the DAPM graph for the capture path.
--

--- Patch [3]: [PATCH v4 3/4] arm64: dts: rockchip: add HDMI RX audio on RK3588 ---
commit e5a9a8ba89a4a45c730c1b44e28e899087346b1f
Author: Igor Paunovic <royalnet026@gmail.com>

arm64: dts: rockchip: add HDMI RX audio on RK3588

This commit exposes the HDMI RX controller's digital audio interfaces by
adding the #sound-dai-cells property. It also adds a shared
simple-audio-card routing the receiver I2S DAI to i2s7_8ch, mirroring
existing HDMI TX sound cards.

> diff --git a/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi b/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
> index a2640014ee042..e0dce15643997 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3588-extra.dtsi

[ ... ]

> @@ -23,6 +23,23 @@ simple-audio-card,cpu {
>  		};
>  	};
>  
> +	hdmi_receiver_sound: hdmi-receiver-sound {
> +		compatible = "simple-audio-card";
> +		simple-audio-card,format = "i2s";
> +		simple-audio-card,name = "RK3588 HDMI-IN";
> +		simple-audio-card,bitclock-master = <&hdmiin_codec>;
> +		simple-audio-card,frame-master = <&hdmiin_codec>;
> +		status = "disabled";
> +
> +		hdmiin_codec: simple-audio-card,codec {
> +			sound-dai = <&hdmi_receiver 0>;
> +		};

[Severity: High]
This isn't a bug introduced by this patch, but will this HDMI RX capture
path work correctly with DAPM given how the underlying codec is currently
defined?

Looking at the hdmi-codec driver used for this receiver:

sound/soc/codecs/hdmi-codec.c:hdmi_widgets[] {
    ...
    SND_SOC_DAPM_OUTPUT("RX"),
    ...
}

The DAPM widget for the HDMI RX capture source is incorrectly defined as an
OUTPUT (sink) instead of an INPUT (source).

When a capture stream starts, DAPM walks backward from the active CPU DAI
sink to find a source, but terminates at "RX" without finding an EP_SOURCE.
Does this prevent DAPM-managed components on the capture path (such as SoC
FIFOs, regulators, or clock supplies) from powering on, causing silent
failures during capture?

> +
> +		simple-audio-card,cpu {
> +			sound-dai = <&i2s7_8ch>;
> +		};
> +	};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260721064115.64809-1-royalnet026@gmail.com?part=3

  reply	other threads:[~2026-07-21  6:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  6:41 [PATCH v4 0/4] media: synopsys: hdmirx: add HDMI audio capture support Igor Paunovic
2026-07-21  6:41 ` [PATCH v4 1/4] dt-bindings: media: snps,dw-hdmi-rx: add #sound-dai-cells Igor Paunovic
2026-07-21 15:13   ` Sebastian Reichel
2026-07-21  6:41 ` [PATCH v4 2/4] media: synopsys: hdmirx: add HDMI audio capture support Igor Paunovic
2026-07-21  7:00   ` sashiko-bot
2026-07-21  7:51     ` Igor Paunovic
2026-07-21  6:41 ` [PATCH v4 3/4] arm64: dts: rockchip: add HDMI RX audio on RK3588 Igor Paunovic
2026-07-21  6:54   ` sashiko-bot [this message]
2026-07-21 15:13   ` Sebastian Reichel
2026-07-21  6:41 ` [PATCH v4 4/4] arm64: dts: rockchip: enable HDMI RX audio capture on Orange Pi 5 Plus Igor Paunovic
2026-07-21 15:15   ` Sebastian Reichel

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=20260721065415.B67001F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=media-ci@linuxtv.org \
    --cc=robh@kernel.org \
    --cc=royalnet026@gmail.com \
    --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