From: "Geoffrey D. Bennett" <g@b4.vu>
To: Takashi Iwai <tiwai@suse.de>
Cc: Takashi Iwai <tiwai@suse.com>, linux-sound@vger.kernel.org
Subject: [PATCH 0/2] ALSA: Don't share mixer->urb with the FCP/scarlett2 notification endpoint
Date: Mon, 10 Aug 2026 03:35:41 +0930 [thread overview]
Message-ID: <cover.1786290885.git.g@b4.vu> (raw)
Hi Takashi,
Both the FCP and scarlett2 drivers used mixer->urb for their
notification endpoint URB, but that field belongs to
snd_usb_mixer_status_create() and is managed by mixer.c. Sharing it
means the "already set up" check in the driver's init_notify() can be
satisfied by the status endpoint's URB, so the driver's own URB is
never submitted and the first command would crash in
wait_for_completion_timeout() on the still-zeroed cmd_done. mixer.c
can also kill, resubmit or free the URB from under the driver.
Give each driver its own URB in its private data. For scarlett2 this
also means taking over the free/suspend/resume handling that mixer.c
was doing for it.
Tested on an ISA C8X and a Scarlett 18i20 Gen 4 (FCP), and a Scarlett
4i4 Gen 3 and 4i4 Gen 4 (scarlett2) on 7.1.7, including suspend/resume
and configuration save on suspend.
Thanks,
Geoffrey
Geoffrey D. Bennett (2):
ALSA: FCP: Use a private URB for the notification endpoint
ALSA: scarlett2: Use a private URB for the notification endpoint
sound/usb/fcp.c | 38 +++++++-------
sound/usb/mixer.c | 6 +++
sound/usb/mixer.h | 2 +
sound/usb/mixer_scarlett2.c | 98 ++++++++++++++++++++++++-------------
4 files changed, 92 insertions(+), 52 deletions(-)
--
2.55.0
next reply other threads:[~2026-08-09 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-09 18:05 Geoffrey D. Bennett [this message]
2026-08-09 18:06 ` [PATCH 1/2] ALSA: FCP: Use a private URB for the notification endpoint Geoffrey D. Bennett
2026-08-09 18:06 ` [PATCH 2/2] ALSA: scarlett2: " Geoffrey D. Bennett
2026-08-10 11:37 ` [PATCH 0/2] ALSA: Don't share mixer->urb with the FCP/scarlett2 " 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=cover.1786290885.git.g@b4.vu \
--to=g@b4.vu \
--cc=linux-sound@vger.kernel.org \
--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