From: Cen Zhang <zzzccc427@gmail.com>
To: perex@perex.cz, tiwai@suse.com
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, baijiaju1990@gmail.com, jjzuming@gmail.com,
zzzccc427@gmail.com
Subject: [PATCH v2 0/3] ALSA: pcm: Retain components across codec teardown
Date: Sat, 24 Oct 2026 19:41:13 +0800 [thread overview]
Message-ID: <pm-pmb-a4703edca61d34aa679b-v9-c4f3df026f28aea10fd1-0@gmail.com> (raw)
A pending PCM opener can retain the card without retaining a PCM removed
by codec-only unbind. A late codec probe can also publish PCM devices
before a subsequent registration failure starts cleanup.
Retain native and OSS PCM lookups through file release, close admission
at component disconnect, and drain codec users before probe-error cleanup.
Keep the existing proc rundown outside open_mutex at disconnect, and wait
for PCM references in final cleanup after the lookup gate is closed.
---
Cen Zhang (3):
ALSA: pcm: Retain components across native minor lookups
ALSA: pcm: oss: Retain the PCM from minor lookup through release
ALSA: hda: Drain PCM users before cleaning up a failed codec probe
include/sound/pcm.h | 11 ++++++
sound/core/oss/pcm_oss.c | 20 +++++++----
sound/core/pcm.c | 74 ++++++++++++++++++++++++++++++++++++++--
sound/core/pcm_native.c | 44 ++++++++++++++++--------
sound/hda/common/bind.c | 3 ++
5 files changed, 128 insertions(+), 24 deletions(-)
Changes in v2:
- Replace the setup-list-only fix with separate native PCM, OSS PCM and HDA
probe-error lifetime fixes.
- Retain PCM references from minor lookup through file release and roll back
partially registered minors.
- Rebase onto current for-next while preserving proc rundown outside
open_mutex at device disconnect.
- Drain codec PCM users before probe-error cleanup removes driver state.
- Describe the native HDA codec sysfs-unbind and PCM cleanup sequence
explicitly in the core patch.
Link to v1: https://lore.kernel.org/r/pm-pmb-a4703edca61d34aa679b-v6-680f350d78e44f9de7a7@gmail.com
next reply other threads:[~2026-10-24 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 11:41 Cen Zhang [this message]
2026-10-24 11:41 ` [PATCH v2 1/3] ALSA: pcm: Retain components across native minor lookups Cen Zhang
2026-10-24 11:41 ` [PATCH v2 2/3] ALSA: pcm: oss: Retain the PCM from minor lookup through release Cen Zhang
2026-10-24 11:41 ` [PATCH v2 3/3] ALSA: hda: Drain PCM users before cleaning up a failed codec probe Cen Zhang
2026-10-26 8:39 ` [PATCH v2 0/3] ALSA: pcm: Retain components across codec teardown Takashi Iwai
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=pm-pmb-a4703edca61d34aa679b-v9-c4f3df026f28aea10fd1-0@gmail.com \
--to=zzzccc427@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=jjzuming@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®