From: Daniel Mack <daniel@caiaq.de>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Felix Homann <linuxaudio@showlabor.de>
Subject: Re: Need expert's advice - Fast Track Ultra (8R) dropping samples
Date: Tue, 12 Oct 2010 09:18:31 +0200 [thread overview]
Message-ID: <20101012071831.GA7159@buzzloop.caiaq.de> (raw)
In-Reply-To: <4CAEB9AC.1060208@ladisch.de>
On Fri, Oct 08, 2010 at 08:26:52AM +0200, Clemens Ladisch wrote:
> Felix Homann wrote:
> > @Daniel:
> > You asked for the output of lsusb. Are you thinking of modifying the
> > UA-101 driver yourself? Or something more generic?
>
> I guess he wanted to look for UAC2 descriptors (which this device does
> not have).
Actually, I wanted to check whether the device marks the inbound
(capture) endpoint as isochronous with implicit data feedback usage.
Which it doesn't either.
> When (if) the driver has UAC2 implicit feedback support, it's easy to
> add a simple quirk that makes the FTU work. (In that case, the UA-101
> driver can be merged back, too.)
I wonder if we can always fall back to implicit feedback in case a
playback substream does not have a syncpipe and does not have its
fill_max bit set.
Felix, can you add a
printk(KERN_WARNING "%s() is_playback %d fill_max %d syncpipe %d\n",
__func__, is_playback, subs->fill_max, subs->syncpipe);
at the end of set_format() in pcm.c and send us the output?
I have an untested patch ready which should add support for implicit
feedback, but I'm uncertain about the condition when to activate this
mode.
Daniel
next prev parent reply other threads:[~2010-10-12 7:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 9:57 Need expert's advice - Fast Track Ultra (8R) dropping samples Felix Homann
2010-10-01 11:00 ` Felix Homann
2010-10-01 16:29 ` Clemens Ladisch
2010-10-03 11:50 ` Felix Homann
2010-10-03 12:00 ` Daniel Mack
2010-10-05 7:21 ` Clemens Ladisch
2010-10-06 13:57 ` Felix Homann
2010-10-06 14:38 ` Clemens Ladisch
2010-10-06 16:31 ` Felix Homann
2010-10-07 6:37 ` Clemens Ladisch
2010-10-07 8:10 ` Daniel Mack
2010-10-07 8:50 ` Felix Homann
2010-10-07 11:35 ` Felix Homann
2010-10-08 6:26 ` Clemens Ladisch
2010-10-12 7:18 ` Daniel Mack [this message]
2010-10-12 8:18 ` Felix Homann
2010-10-12 10:26 ` Daniel Mack
2010-10-13 7:47 ` Felix Homann
2010-10-13 12:48 ` Daniel Mack
2010-10-15 7:23 ` Clemens Ladisch
2010-10-15 8:59 ` Daniel Mack
2010-10-15 11:08 ` Felix Homann
2010-10-15 14:21 ` Clemens Ladisch
2010-10-03 10:02 ` Daniel Mack
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=20101012071831.GA7159@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=linuxaudio@showlabor.de \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).