alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: ALSA development <alsa-devel@alsa-project.org>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] ALSA: hda/hdmi: Use only dynamic PCM device allocation #forregzbot
Date: Mon, 26 Dec 2022 14:26:11 +0100	[thread overview]
Message-ID: <163d5366-35d9-f7db-cf50-796d6b011c0a@leemhuis.info> (raw)
In-Reply-To: <1c9c00dec72c241a399b3b7c0a305382a5712529.camel@bi-co.net>

[Note: this mail contains only information for Linux kernel regression
tracking. Mails like these contain '#forregzbot' in the subject to make
then easy to spot and filter out. The author also tried to remove most
or all individuals from the list of recipients to spare them the hassle.]

On 25.12.22 13:14, Michael Laß wrote:
> CC'ing amd-gfx as this might be an issue in the amd driver.
> 
> This change causes a regression in Linux 6.1 at least on some AMD APUs.
> There are reports from users with Ryzen 4750U, 5800U and 5850U chips
> where the HDMI sound devices don't show up anymore. I'm affected by
> this as well.
> 
> Reverting this commit (ef6f5494) makes the HDMI audio devices show up
> again. I verified that this is still an issue in current Linux git
> (72a85e2b).

Thanks for the report. To be sure below issue doesn't fall through the
cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
tracking bot:

#regzbot ^introduced ef6f5494faf6a37c74990689a
#regzbot title alsa: hda/hdmi: HDMI sound devices don't show up anymore
with some AMD APUs
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.


> Am Donnerstag, dem 22.09.2022 um 10:40 +0200 schrieb Jaroslav Kysela:
>>> Per discussion on the alsa-devel mailing list [1], the legacy PIN to PCM
>>> device mapping is obsolete nowadays. The maximum number of the simultaneously
>>> usable PCM devices is equal to the HDMI codec converters.
>>>
>>> Remove the extra PCM devices (beyond the detected converters) and force
>>> the use of the dynamic PCM device allocation. The legacy code is removed.
>>>
>>> I believe that all HDMI codecs have the jack sensing feature. Move the check
>>> to the codec probe function and print a warning, if a codec without this
>>> feature is detected.
> 
> The corresponding message ("jack not detectable") is not shown on the
> affected system.
> 
>>> [1] https://lore.kernel.org/alsa-devel/2f37e0b2-1e82-8c0b-2bbd-1e5038d6ecc6@perex.cz/
> 
> Links to some reports of this issue:
> https://bugzilla.kernel.org/show_bug.cgi?id=216836
> https://bbs.archlinux.org/viewtopic.php?pid=2075700
> https://bugs.archlinux.org/task/76917
> https://www.reddit.com/r/archlinux/comments/zsqq7i/hdmi_audio_is_broken_after_updating_kernel_to_611
> 
> Best regards,
> Michael

  parent reply	other threads:[~2022-12-26 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22  8:40 [PATCH] ALSA: hda/hdmi: Use only dynamic PCM device allocation Jaroslav Kysela
2022-09-22 11:59 ` Takashi Iwai
2022-12-25 12:14 ` Michael Laß
2022-12-25 18:52   ` Takashi Iwai
2022-12-26 19:24     ` Jaroslav Kysela
2022-12-26 13:26   ` Thorsten Leemhuis [this message]
2023-01-27 12:52     ` [PATCH] ALSA: hda/hdmi: Use only dynamic PCM device allocation #forregzbot Linux kernel regression tracking (#update)

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=163d5366-35d9-f7db-cf50-796d6b011c0a@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=alsa-devel@alsa-project.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=regressions@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;
as well as URLs for NNTP newsgroup(s).