Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kunal Singh <kunal@singhkunal.com>
To: alsa-devel@alsa-project.org
Subject: Re: bandwidth issue with usb-audio in alsa
Date: Tue, 27 May 2008 18:40:31 +0530	[thread overview]
Message-ID: <483C0847.1080405@singhkunal.com> (raw)

Hi,

	I have some update on the issue which I had reported earlier. In my last e-mail, I had not mentioned that iPod is connected to the target through a USB (HS) Hub. When I connect the
same hub to my Desktop and read its configuration using "usbview" - I see that "interval" for this hub is mentioned
as "256 msec". (I have two hubs and I get all the results same with both the hubs).

	With 36 URBs, the gap between two set of transactions is appx 220 msec (220+36 => 256). So, I am wondering
if the problem which I am seeing is because the external hub. I can not connect iPod directly to my target board,
because this board does not support enough current (as needed by iPod).

	Can some one suggest, where is the problem - is it with the host controller driver? 

Regards,
Kunal Singh

-----------------------------

Kunal Singh wrote:

Hi,

  My Platform
 -------------
  I am trying to stream audio data from a USB-device (an iPod) to my
arm-based embedded device (running kernel 2.6.23). The USB-device confirms
to usb digital audio (subclass - streaming) class. The endpoint buffer size
196 bytes and transfer period is 1 msec. So, I should be reading data every
msec.

  Problem
  -----------
  I am facing some bandwidth issues. The data is not being captured fast
enough.

  I notice that once one set of URBs are captured (one set equal to
MAX_URBS), there is a significant delay in capturing the next set of URBs. 

     I have set MAX_URBS equal to 32.
     When I connect a USB-Analyzer and analyze the timings, I can see that
32 URBs are captured at a interval of 1 msec each. After that there is a
break of around 250 msec. And then again 32 URBs captured in sequence.

      If I change the MAX_URBs to any other value N, N URBs get captured at
interval of 1 msec each, and then there is a break.

      Can some one suggest a way to improve this problem. Is there some
configuration or parameter which I can change, so that URBs get submitted
fast enough? May be as soon as the old one has retired.

Thanks and Regards,
Kunal
www.singhkunal.com

             reply	other threads:[~2008-05-27 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 13:10 Kunal Singh [this message]
2008-05-27 15:34 ` bandwidth issue with usb-audio in alsa Clemens Ladisch
2008-05-27 15:47 ` Jon Smirl
  -- strict thread matches above, loose matches on Subject: below --
2008-05-28  5:12 kunal
2008-05-28  3:03 kunal
2008-05-27  4:23 kunal

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=483C0847.1080405@singhkunal.com \
    --to=kunal@singhkunal.com \
    --cc=alsa-devel@alsa-project.org \
    /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