Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Trimarchi <michael@amarulasolutions.com>
To: Daniel Mack <zonque@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	1136110@bugs.launchpad.net, Takashi Iwai <tiwai@suse.de>,
	Clemens Ladisch <clemens@ladisch.de>,
	Alan Stern <stern@rowland.harvard.edu>,
	David Henningsson <david.henningsson@canonical.com>
Subject: Re: Asynchronous audio USB chips: choppy playback since 3.8-rc7
Date: Wed, 03 Apr 2013 17:19:21 +0200	[thread overview]
Message-ID: <515C4879.8090208@amarulasolutions.com> (raw)
In-Reply-To: <515C4410.4030904@gmail.com>

Hi Daniel

On 03/04/13 17:00, Daniel Mack wrote:
> Hi Michael,
> 
> On 03.04.2013 16:11, Michael Trimarchi wrote:
>> On 03/04/13 15:55, Michael Trimarchi wrote:
>>> On 03/04/13 12:23, Daniel Mack wrote:
>>>> Hi David,
>>>>
>>>> On 03.04.2013 12:15, David Henningsson wrote:
>>>>> Just to get your attention here on what seems to be an USB audio 
>>>>> regression.
>>>>>
>>>>> The bug is described in detail here:
>>>>>
>>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1136110?comments=all
>>>>>
>>>>> Quoting the bug:
>>>>>
>>>>> "
>>>>> This bug seems to affect only a certain kind of hardware, which is 
>>>>> called "Asynchronous USB Digital Audio Codec (DAC)". It's said that such 
>>>>> a DAC hosts the clock itself (USB Device Host). An ordinary DAC, so 
>>>>> called "Synchronous USB DAC", uses the clock hosted by the mother board, 
>>>>> which is not affected by this bug.
>>>>>
>>>>> When this bug affects an asynchronous USB DAC, the audio played by the 
>>>>> DAC is constantly interrupted. The playback itself does not stop, but 
>>>>> the output becomes discontinous, filling with constant crackling noises, 
>>>>> destroying everything the DAC plays.
>>>>> "
>>>>>
>>>>> According to the bug reporter, which seems to have done quite a bit of 
>>>>> research, this started between 3.8-rc6 and 3.8-rc7 as well as stable 
>>>>> kernels and the bug also lists a few commits which could be the cause, 
>>>>> none under sound/usb though.
>>>>
>>>> There were no relevant changes for snd-usb between the two versions
>>>> mentioned. The only patches that come in mind in this time window are:
>>>>
>>>>  3e619d041 "USB: EHCI: fix bug in scheduling periodic split transfers"
>>>>  b09a61cc0 "USB: EHCI: fix for leaking isochronous data"
>>>
>>> This last one, doesn't give me any problem, just a memory leak and not a choppy
>>> playback (tested on 48Khz, 96Khz, 192Khz 32bit on OMAP3 device) and I don't
>>> think that it can be the reason of the problem.
> 
> Is OMAP3 at all a platform that is affected by the bug? It seems the
> effect is only seen on some special host controller hardware anyway.
> 

Yes, omap3 ehci and m2tech products is not affected and I'm testing a dac with internal clock.

>> Sorry the comment was for a bug that is not included in this list and recently fixed.
>> USB: EHCI: fix bug in iTD/siTD DMA pool allocation
> 
> Sorry, you lost me. So what's the status of this issue now? Does "USB:
> EHCI: fix bug in iTD/siTD DMA pool allocation" fix it?

With or without it, I don't have any choppy audio and this is not a fix
of this bug.

> 
> If not - and assuming you can reproduce the bug - which patches of the
> two I mentioned did you revert, and what was the effect of that? Did you
> try and remove both as well?

In my version I have the other two commits applied. I doubt that these two
commits are the reason of the choppy audio. What I can do, it test it on my
laptop tomorrow and send feedback result

Michael



> 
> 
> Thanks,
> Daniel
>

  reply	other threads:[~2013-04-03 15:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 10:15 Asynchronous audio USB chips: choppy playback since 3.8-rc7 David Henningsson
2013-04-03 10:23 ` Daniel Mack
2013-04-03 13:55   ` Michael Trimarchi
2013-04-03 14:11     ` Michael Trimarchi
2013-04-03 15:00       ` Daniel Mack
2013-04-03 15:19         ` Michael Trimarchi [this message]
     [not found]           ` <515C4879.8090208-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
2013-04-03 15:37             ` [alsa-devel] " Daniel Mack
2013-04-03 10:25 ` Takashi Iwai
2013-04-19 18:54   ` Daniel Mack
2013-04-19 20:48     ` [alsa-devel] " Alan Stern
2013-04-24 18:30       ` David Henningsson
2013-04-24 19:11         ` Alan Stern
2013-04-19 20:48     ` Alan Stern

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=515C4879.8090208@amarulasolutions.com \
    --to=michael@amarulasolutions.com \
    --cc=1136110@bugs.launchpad.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=david.henningsson@canonical.com \
    --cc=stern@rowland.harvard.edu \
    --cc=tiwai@suse.de \
    --cc=zonque@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