From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [PATCH] ALSA: hda/hdmi: Use only dynamic PCM device allocation
Date: Thu, 22 Sep 2022 13:59:02 +0200 [thread overview]
Message-ID: <87a66r7h89.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220922084017.25925-1-perex@perex.cz>
On Thu, 22 Sep 2022 10:40:17 +0200,
Jaroslav Kysela wrote:
>
> 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.
>
> [1] https://lore.kernel.org/alsa-devel/2f37e0b2-1e82-8c0b-2bbd-1e5038d6ecc6@perex.cz/
>
> Cc: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Signed-off-by: Jaroslav Kysela <perex@perex.cz>
Applied now. Thanks.
Takashi
next prev parent reply other threads:[~2022-09-22 12:00 UTC|newest]
Thread overview: 10+ 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 [this message]
2022-12-25 12:14 ` Michael Laß
2022-12-25 18:52 ` Takashi Iwai
2022-12-25 18:52 ` Takashi Iwai
2022-12-26 19:24 ` Jaroslav Kysela
2022-12-26 13:26 ` [PATCH] ALSA: hda/hdmi: Use only dynamic PCM device allocation #forregzbot Thorsten Leemhuis
2022-12-26 13:26 ` Thorsten Leemhuis
2023-01-27 12:52 ` Linux kernel regression tracking (#update)
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=87a66r7h89.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=perex@perex.cz \
/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.