From: Clemens Ladisch <clemens@ladisch.de>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: 'Sarah Sharp' <sarah.a.sharp@linux.intel.com>,
'ALSA Development Mailing List' <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] ALSA: usb: refine delay information with USB frame counter
Date: Thu, 25 Aug 2011 16:07:50 +0200 [thread overview]
Message-ID: <4E565736.4070600@ladisch.de> (raw)
In-Reply-To: <002301cc632f$5bfe0a90$13fa1fb0$@bossart@linux.intel.com>
Pierre-Louis Bossart wrote:
> > > + if (frame_diff < 0)
> > > + frame_diff += 1024; /* handle 10-bit wrap-around */
> >
> > After reading through some HCD source files, I deduced the following
> > wrap-arounds:
> >
> > EHCI: 8-10 bits (default 9)
> > FHCI: 11 bits
> > IMX21: 16 bits
> > ISP1760: 10 bits
> > OHCI: 16 bits
> > OXU210HP: 10 bits
> > R8A66597: 10 bits
> > SL811: 5 bits(!?)
> > UHCI: 32 bits
> > xHCI: ?
> >
> > As long as there isn't an API that tells us about the valid range of the
> > frame counter, we should probably mask off all except the lowest few bits.
>
> If we only used the 8 least-significant bits, it'd still leave us with up to
> 256 ms. That should work I guess. But the SL811 with 5 bits is a problem,
> that makes 32ms, this is probably too low.
Sorry, I read the code wrong; that driver returns a 16-bit frame counter, it
just doesn't allow to schedule more than 32 frame AFAICT. And that driver
doesn't support USB audio anyway, so 8 bits should be fine.
Regards,
Clemens
next prev parent reply other threads:[~2011-08-25 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 21:26 [PATCH] ALSA: usb: refine delay information with USB frame counter Pierre-Louis Bossart
2011-08-25 7:54 ` Clemens Ladisch
2011-08-25 14:00 ` Pierre-Louis Bossart
[not found] ` <002301cc632f$5bfe0a90$13fa1fb0$@bossart@linux.intel.com>
2011-08-25 14:07 ` Clemens Ladisch [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-29 18:32 Pierre-Louis Bossart
2011-08-30 7:59 ` Clemens Ladisch
2011-08-30 15:34 ` Pierre-Louis Bossart
2011-09-05 7:53 ` Clemens Ladisch
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=4E565736.4070600@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sarah.a.sharp@linux.intel.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