From: sashiko-bot@kernel.org
To: "Detlev Casanova" <detlev.casanova@collabora.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 4/7] arm64: dts: rockchip: Rename rk3399 HDMI audio card
Date: Mon, 31 Aug 2026 17:55:13 +0000 [thread overview]
Message-ID: <20260831175514.6082E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831-fix-rockchip-hdmi-audio-names-v1-4-5b155ae05293@collabora.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] Changing the ALSA sound card name breaks userspace audio configurations and constitutes an ABI regression.
- [Medium] The commit message claims the new name matches the Rockchip family naming scheme, which is demonstrably false.
--
commit d9591718c98e7ed37b2a63128b5ae03809c98902
Author: Detlev Casanova <detlev.casanova@collabora.com>
arm64: dts: rockchip: Rename rk3399 HDMI audio card
This commit renames the HDMI audio card in the RK3399 device tree from
"hdmi-sound" to "RK3399 HDMI". The stated goal is to better identify the SoC
in ALSA fields and match naming conventions across the rest of the Rockchip
family.
> Rename the card from "hdmi-sound" to "RK3399 HDMI" so it identifies
> the SoC in user-visible ALSA fields and matches the naming scheme
> used across the rest of the Rockchip family.
[Severity: Medium]
Is this description accurate?
Looking at the baseline tree, all other Rockchip base device trees use generic
HDMI names without an SoC prefix (e.g., "HDMI" in rk3328, rk356x, and rk3576;
"hdmi0" in rk3588).
Since the series itself introduces the SoC prefix to these other files in
subsequent patches, it seems no such naming scheme existed across the rest of
the family at the time of this commit. Could the commit message be more
precise about the motivation?
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-base.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-base.dtsi
> index 49c68fe65de66..c46e58d4af0d4 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-base.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-base.dtsi
> @@ -2008,7 +2008,7 @@ hdmi_sound: hdmi-sound {
> compatible = "simple-audio-card";
> simple-audio-card,format = "i2s";
> simple-audio-card,mclk-fs = <256>;
> - simple-audio-card,name = "hdmi-sound";
> + simple-audio-card,name = "RK3399 HDMI";
[Severity: High]
Does changing the user-visible ALSA card name constitute an ABI regression?
Userspace audio frameworks like PulseAudio or ALSA UCM use the ALSA card name
to identify the device and apply correct mixer and routing profiles. Changing
simple-audio-card,name alters this user-visible identifier.
Existing userspace configurations on the widely deployed RK3399 platform that
match on "hdmi-sound" will fail on boot, resulting in broken audio
out-of-the-box and violating the kernel's rules regarding userspace ABI
regressions.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260831-fix-rockchip-hdmi-audio-names-v1-0-5b155ae05293@collabora.com?part=4
next prev parent reply other threads:[~2026-08-31 17:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 14:20 [PATCH 0/7] arm64: dts: rockchip: give HDMI sound cards SoC-specific names Detlev Casanova
2026-08-31 14:20 ` Detlev Casanova
2026-08-31 14:20 ` [PATCH 1/7] arm64: dts: rockchip: Rename rk3066a HDMI audio card Detlev Casanova
2026-08-31 14:20 ` Detlev Casanova
2026-08-31 14:20 ` [PATCH 2/7] arm64: dts: rockchip: Rename rk3288 " Detlev Casanova
2026-08-31 14:20 ` Detlev Casanova
2026-08-31 17:47 ` sashiko-bot
2026-08-31 14:20 ` [PATCH 3/7] arm64: dts: rockchip: Rename rk3328 " Detlev Casanova
2026-08-31 14:20 ` Detlev Casanova
2026-08-31 17:49 ` sashiko-bot
2026-08-31 14:20 ` [PATCH 4/7] arm64: dts: rockchip: Rename rk3399 " Detlev Casanova
2026-08-31 14:20 ` Detlev Casanova
2026-08-31 17:55 ` sashiko-bot [this message]
2026-08-31 14:20 ` [PATCH 5/7] arm64: dts: rockchip: Rename rk356x " Detlev Casanova
2026-08-31 14:20 ` Detlev Casanova
2026-08-31 17:29 ` Diederik de Haas
2026-08-31 17:29 ` Diederik de Haas
2026-08-31 20:07 ` Detlev Casanova
2026-08-31 20:07 ` Detlev Casanova
2026-08-31 17:59 ` sashiko-bot
2026-08-31 14:20 ` [PATCH 6/7] arm64: dts: rockchip: Rename rk3576 " Detlev Casanova
2026-08-31 14:20 ` Detlev Casanova
2026-08-31 14:20 ` [PATCH 7/7] arm64: dts: rockchip: Rename rk3588 HDMI audio cards Detlev Casanova
2026-08-31 14:20 ` Detlev Casanova
2026-08-31 18:02 ` 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=20260831175514.6082E1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.