Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alexander Tsoy <alexander@tsoy.me>
Cc: Gregor Pintar <grpintar@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: usb-audio: Apply async workaround for Scarlett 2i4 2nd gen
Date: Thu, 23 Apr 2020 19:35:13 +0200	[thread overview]
Message-ID: <s5hr1wet8a6.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5htv1at8kb.wl-tiwai@suse.de>

On Thu, 23 Apr 2020 19:29:08 +0200,
Takashi Iwai wrote:
> 
> On Thu, 23 Apr 2020 18:57:34 +0200,
> Alexander Tsoy wrote:
> > 
> > And some further notes:
> > 
> > - I removed locking from snd_usb_endpoint_next_packet_size() and this
> > seems completely fixed an issue with large URBs I reported here:
> > 
> > https://bugzilla.kernel.org/show_bug.cgi?id=199327#c28
> > 
> > So playing at 96 kHz, driver packs 48 frames per URB and no more audio
> > discontinuities.
> 
> Hmm, that's weird.
> 
> If removing the lock from snd_usb_endpoint_next_packet_size() really
> fixes the problem, it implies the lock contention.  But as far as I
> see the code performed in this lock isn't conflicting so much.  The
> URB processing shouldn't happen in parallel for the same EP.

BTW, one potential racy code I found while looking at the code is the
list management in queue_pending_output_urbs().  The fix patch is
below.


Takashi

--- a/sound/usb/endpoint.c
+++ b/sound/usb/endpoint.c
@@ -321,17 +321,17 @@ static void queue_pending_output_urbs(struct snd_usb_endpoint *ep)
 			ep->next_packet_read_pos %= MAX_URBS;
 
 			/* take URB out of FIFO */
-			if (!list_empty(&ep->ready_playback_urbs))
+			if (!list_empty(&ep->ready_playback_urbs)) {
 				ctx = list_first_entry(&ep->ready_playback_urbs,
 					       struct snd_urb_ctx, ready_list);
+				list_del_init(&ctx->ready_list);
+			}
 		}
 		spin_unlock_irqrestore(&ep->lock, flags);
 
 		if (ctx == NULL)
 			return;
 
-		list_del_init(&ctx->ready_list);
-
 		/* copy over the length information */
 		for (i = 0; i < packet->packets; i++)
 			ctx->packet_size[i] = packet->packet_size[i];

  reply	other threads:[~2020-04-23 17:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 19:09 [PATCH] ALSA: usb-audio: Apply async workaround for Scarlett 2i4 2nd gen Alexander Tsoy
2020-04-21 19:31 ` Takashi Iwai
2020-04-22  3:57   ` Alexander Tsoy
2020-04-22 18:55     ` Gregor Pintar
2020-04-22 19:26       ` Alexander Tsoy
2020-04-22 20:19         ` Alexander Tsoy
2020-04-22 20:28         ` Takashi Iwai
2020-04-22 23:45           ` Alexander Tsoy
2020-04-23  7:22             ` Takashi Iwai
2020-04-23 11:22               ` Takashi Iwai
2020-04-23 15:10                 ` Alexander Tsoy
2020-04-23 16:57                   ` Alexander Tsoy
2020-04-23 17:29                     ` Takashi Iwai
2020-04-23 17:35                       ` Takashi Iwai [this message]
2020-04-23 18:24                         ` Alexander Tsoy
2020-04-26 17:12                           ` Alexander Tsoy
2020-04-27  7:08                             ` Takashi Iwai
2020-04-23 17:32                   ` Takashi Iwai
2020-04-23 11:46             ` Gregor Pintar
2020-04-23 14:01               ` Alexander Tsoy

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=s5hr1wet8a6.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alexander@tsoy.me \
    --cc=alsa-devel@alsa-project.org \
    --cc=grpintar@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