alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: "Takashi Iwai" <tiwai@suse.de>, "Michael Laß" <bevan@bi-co.net>
Cc: ALSA development <alsa-devel@alsa-project.org>,
	amd-gfx@lists.freedesktop.org,
	Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [PATCH] ALSA: hda/hdmi: Use only dynamic PCM device allocation
Date: Mon, 26 Dec 2022 20:24:11 +0100	[thread overview]
Message-ID: <47f3590c-f371-c997-374f-0a2a3dde86dc@perex.cz> (raw)
In-Reply-To: <87edsnxqmo.wl-tiwai@suse.de>

On 25. 12. 22 19:52, Takashi Iwai wrote:
> On Sun, 25 Dec 2022 13:14:28 +0100,
> 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).
>>
>> 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
> 
> Could you give alsa-info.sh outputs from both working and non-working
> cases?  Run the script with --no-upload option during the playback of
> HDMI stream, and attach the outputs.

BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=216836

				Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.

  reply	other threads:[~2022-12-26 19:25 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 [this message]
2022-12-26 13:26   ` [PATCH] ALSA: hda/hdmi: Use only dynamic PCM device allocation #forregzbot Thorsten Leemhuis
2023-01-27 12:52     ` 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=47f3590c-f371-c997-374f-0a2a3dde86dc@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bevan@bi-co.net \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=tiwai@suse.de \
    /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).