From: Takashi Iwai <tiwai@suse.de>
To: Cen Zhang <zzzccc427@gmail.com>
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, tiwai@suse.de,
baijiaju1990@gmail.com, jjzuming@gmail.com
Subject: Re: [PATCH v4 0/3] ALSA: opl3: Fix sequencer timer and channel lifetimes
Date: Mon, 26 Oct 2026 09:01:22 +0100 [thread overview]
Message-ID: <87wlr46gbx.wl-tiwai@suse.de> (raw)
In-Reply-To: <pm-pmb-4552c4e605507d8d9b16-v9-70247b8436e10e26d324-0@gmail.com>
On Sat, 24 Oct 2026 18:49:48 +0200,
Cen Zhang wrote:
>
> OPL3 can receive a fixed-duration note before its timer is initialized,
> and the card-owned voice array can retain channel pointers after either
> sequencer port has freed its channel set. The delayed-note timer can also
> remain queued after the sequencer client has been deleted.
>
> Initialize the timer before publishing ports, key off active voices and
> clear their aliases before freeing each channel set, and shut down the
> shared timer after client deletion has drained both event producers.
> Retire higher-numbered partners before their 4-op primaries so no active
> hardware KEYON is skipped when the primary changes its partner's state.
>
> This series applies to tiwai/sound.git for-next at d74eb09af56b.
>
> ---
> Cen Zhang (3):
> ALSA: opl3: Initialize the timer before publishing a sequencer port
> ALSA: opl3: Clear voice channels before freeing their sets
> ALSA: opl3: Shut down the timer after draining sequencer ports
Applied all three patches now. Thanks.
Takashi
prev parent reply other threads:[~2026-10-26 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 16:49 Cen Zhang
2026-10-24 16:49 ` [PATCH v4 1/3] ALSA: opl3: Initialize the timer before publishing a sequencer port Cen Zhang
2026-10-24 16:49 ` [PATCH v4 2/3] ALSA: opl3: Clear voice channels before freeing their sets Cen Zhang
2026-10-24 16:49 ` [PATCH v4 3/3] ALSA: opl3: Shut down the timer after draining sequencer ports Cen Zhang
2026-10-26 8:01 ` Takashi Iwai [this message]
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=87wlr46gbx.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--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=zzzccc427@gmail.com \
/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®