Linux bluetooth development
 help / color / mirror / Atom feed
From: Max Krasnyansky <maxk@qualcomm.com>
To: James Courtier-Dutton <James@superbug.demon.co.uk>,
	James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: Cozza <ac2crp@blueyonder.co.uk>,
	bluez Dev <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bluetooth headset problems.
Date: Mon, 21 Jul 2003 15:30:32 -0700	[thread overview]
Message-ID: <5.1.0.14.2.20030721152542.096f0a48@unixmail.qualcomm.com> (raw)
In-Reply-To: <3F08719F.70708@superbug.demon.co.uk>

At 11:59 AM 7/6/2003, James Courtier-Dutton wrote:


>>I have made some progress. I can now record audio from the headset without it loosing any samples. I.e. I can record 8 bit PCM at 8000hz and it sounds fine. Before it was loosing samples and recording at more like 4000hz.
>>Once I get playback to work, I will post a patch to this list.
>>Cheers
>>James
>If anyone is interested, the fix for recording required 2 urbs for each isoc connection. The current cvs only uses 1 urb for isoc connections, so the usbcore fills one urb in real time, and then when it is full, sends it to hci_usb.c via a callback. Once hci_usb.c has finished with the urb it sends it back to the usbcore to get refilled. The problem is that while hci_usb.c is processing the urb, usbcore has no urb to put real time audio samples in, so it just drops them. If 2 urbs are used, if hci_usb.c is processing one, usbcore always has another to place samples in. As long as hci_usb.c does not hold on to it's urb for too long, all is ok. This fix was discovered by comparing the alsa snd-usb-audio driver with the hci_usb.c driver.
Make sense. 
So basically you're saying that you're just calling hci_usb_isoc_rx_submit() twice 
during open, right ? ie just like hci_usb_bulk_rx_submit() is called multiple times.

Max
        



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2003-07-21 22:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-02 13:18 [Bluez-devel] Bluetooth headset problems James Courtier-Dutton
2003-07-03 11:05 ` Cozza
2003-07-03 12:36   ` James Courtier-Dutton
2003-07-05  1:55   ` James Courtier-Dutton
2003-07-06 18:59     ` James Courtier-Dutton
2003-07-06 20:44       ` Marcel Holtmann
2003-07-06 22:11         ` James Courtier-Dutton
2003-07-06 22:16           ` Marcel Holtmann
2003-07-08  9:13             ` Cozza
2003-07-09 10:06               ` David Woodhouse
2003-07-21 22:30       ` Max Krasnyansky [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=5.1.0.14.2.20030721152542.096f0a48@unixmail.qualcomm.com \
    --to=maxk@qualcomm.com \
    --cc=James@superbug.demon.co.uk \
    --cc=ac2crp@blueyonder.co.uk \
    --cc=bluez-devel@lists.sourceforge.net \
    /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