alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: [PATCH 1/2] ALSA: include/linux/usb/audio.h: add __attribute__((packed))
Date: Wed, 12 May 2010 00:50:54 +0200	[thread overview]
Message-ID: <20100511225054.GL30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <s5hd3x2p3ds.wl%tiwai@suse.de>

On Tue, May 11, 2010 at 10:52:47PM +0200, Takashi Iwai wrote:
> At Tue, 11 May 2010 18:13:49 +0200,
> Daniel Mack wrote:
> > 
> > This was missing on the definition of struct uac_iso_endpoint_descriptor
> > 
> > Signed-off-by: Daniel Mack <daniel@caiaq.de>
> > Cc: Takashi Iwai <tiwai@suse.de>
> > Cc: Clemens Ladisch <clemens@ladisch.de>
> 
> Applied these fixes now.  Thanks.

Thanks! One of the noted TODOs is that UAC2 offers the ability to a
device to dynamically change the supported range of options for a given
control. So an enum-driven control can get new values, lose some,
whatever. What would be the best way to map that to ALSA controls?

Another thing that we would need to support at some time is clock
selectors to switch from an internal clock to some external one. And
this can also be notfied dynamically - so for example: once an external
S/PDIF transmitter is connected, the driver gets informed about a new
valid clock source. I haven't found anything how this could be passed on
to higher levels from a driver, but I might have missed something :)

Daniel

  reply	other threads:[~2010-05-11 22:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-11 16:13 [PATCH 1/2] ALSA: include/linux/usb/audio.h: add __attribute__((packed)) Daniel Mack
2010-05-11 16:13 ` [PATCH 2/2] ALSA: sound/usb: add preliminary support for UAC2 interrupts Daniel Mack
2010-05-11 20:52 ` [PATCH 1/2] ALSA: include/linux/usb/audio.h: add __attribute__((packed)) Takashi Iwai
2010-05-11 22:50   ` Daniel Mack [this message]
2010-05-12  6:41     ` Clemens Ladisch
2010-05-12  7:30       ` 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=20100511225054.GL30801@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.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).