All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Grant Diffey <gdiffey@gmail.com>
Cc: "Takashi Iwai" <tiwai@suse.de>,
	"Aurélien Leblond" <blablack@gmail.com>,
	alsa-devel@alsa-project.org,
	"Clemens Ladisch" <clemens@ladisch.de>,
	"Felix Homann" <linuxaudio@showlabor.de>
Subject: Re: M-Audio FTU issues
Date: Mon, 4 Jul 2011 19:23:28 +0200	[thread overview]
Message-ID: <CACTFLAO1T=Top4SpZ-1r+tw_b7pUqVOi7QDHr4sFa6POrRY8zw@mail.gmail.com> (raw)
In-Reply-To: <CACckToXFevhAHt_jC9P=ifZ9X0KVT1S7-KQnrcSna_ineeSyZg@mail.gmail.com>

On Sun, Jul 3, 2011 at 1:52 PM, Grant Diffey <gdiffey@gmail.com> wrote:
>> I'd like to discuss the API for the ALSA/USB decoupling as suggested
>> by Clemens, which will solve this problem then.
>
>
> Nobody has any ideas what this interface might look like?
>
> From what I understand this would lead to re-unifying the ua101 driver into
> snd-usb-audio as well?

As I've said, my understanding of the USB audio standard covers a
feedback model for which the capture stream implicitly defines the
pace the driver is supposed to deliver audio samples to the playback
endpoint (most devices do have sync endpoint for that). Considering
that, there might be more devices coming up which do it that way, and
we should have support for this model in the generic driver IMO.

So at least, my patch shows that it's not too hard to support it, and
we just need a way to sort out how to incorporate the new logic in a
way that it doesn't break the concept of the generic driver. Let me
think about it for some more days. In the meantime, it sounded like
Clemens already brooded on that topic for FireWire devices, and it
might make sense to benefit from the results (and keep the API
similar).


Daniel

  parent reply	other threads:[~2011-07-04 17:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24  1:14 M-Audio FTU issues Daniel Mack
2011-06-24  3:27 ` Grant Diffey
2011-06-24  7:35 ` Felix Homann
2011-06-24  8:52 ` Felix Homann
2011-06-24 15:23   ` Daniel Mack
2011-06-24 15:58     ` Clemens Ladisch
2011-06-24 16:10       ` Daniel Mack
2011-06-28 20:37         ` Aurélien Leblond
2011-06-29  8:08           ` Daniel Mack
2011-07-03 11:52             ` Grant Diffey
2011-07-04 17:14               ` Aurélien Leblond
2011-07-04 17:23               ` Daniel Mack [this message]
2011-07-13 21:18               ` Juan Pablo Bouza
2011-07-21  5:08               ` Juan Pablo Bouza
2011-07-21  7:55                 ` Daniel Mack
2011-07-21  8:25                   ` Felix Homann
2011-07-24 14:12                     ` Aurélien Leblond
2011-07-24 14:46                       ` Daniel Mack
2011-07-21 20:31                   ` Juan Pablo Bouza
2011-07-22  8:42                     ` Daniel Mack
2011-07-23  4:25                       ` Juan Pablo Bouza
2011-07-25 13:07         ` Clemens Ladisch
2011-06-27  8:52     ` Felix Homann
2011-06-24  9:08 ` Felix Homann

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='CACTFLAO1T=Top4SpZ-1r+tw_b7pUqVOi7QDHr4sFa6POrRY8zw@mail.gmail.com' \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=blablack@gmail.com \
    --cc=clemens@ladisch.de \
    --cc=gdiffey@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.