public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Anton Swart <anton.swart.jhb@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Add quirk flags for AlphaTheta EUPHONIA
Date: Mon, 04 May 2026 13:29:27 +0200	[thread overview]
Message-ID: <87tssnxvjc.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260503211517.14332-1-anton.swart.jhb@gmail.com>

On Sun, 03 May 2026 23:15:17 +0200,
Anton Swart wrote:
> 
> The AlphaTheta EUPHONIA (VID 0x2b73, PID 0x0047) is a USB Audio
> Class 2 DJ mixer that requires implicit feedback for full-duplex
> operation. The capture endpoint (0x83 IN, interface 2) acts as the
> implicit feedback source for the playback endpoint (0x03 OUT,
> interface 1), and the device firmware does not send isochronous
> data on the capture endpoint unless the host is simultaneously
> sending data on the playback endpoint, i.e. playback must be
> started first.
> 
> Without QUIRK_FLAG_PLAYBACK_FIRST the kernel waits for capture URBs
> before submitting playback URBs, creating a deadlock: the device
> waits for playback data and the host waits for capture data.
> Without QUIRK_FLAG_GENERIC_IMPLICIT_FB the kernel does not detect
> the implicit feedback relationship between the two interfaces.
> 
> The same flag combination is already used for the Behringer UMC202HD,
> UMC204HD and UMC404HD (0x1397:0x0507/0x0508/0x0509), which exhibit
> the identical implicit-feedback topology.
> 
> Tested on Raspberry Pi 5 with kernel 6.12.75; continuous full-duplex
> streaming at 96 kHz / 24-bit, zero XRUNs.
> 
> Signed-off-by: Anton Swart <anton.swart.jhb@gmail.com>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-05-04 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 21:15 [PATCH] ALSA: usb-audio: Add quirk flags for AlphaTheta EUPHONIA Anton Swart
2026-05-04 11:29 ` 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=87tssnxvjc.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=anton.swart.jhb@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox