From: Clemens Ladisch <clemens@ladisch.de>
To: Daniel Mack <daniel@caiaq.de>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/2] ALSA: include/linux/usb/audio.h: add __attribute__((packed))
Date: Wed, 12 May 2010 08:41:28 +0200 [thread overview]
Message-ID: <4BEA4D98.5010900@ladisch.de> (raw)
In-Reply-To: <20100511225054.GL30801@buzzloop.caiaq.de>
Daniel Mack wrote:
> ...
> 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?
The control callbacks accept and return the new values; userspace
gets notified of the changed control information with
snd_ctl_notify(card, SNDRV_CTL_EVENT_MASK_INFO, &elem_id);
I'm quite sure that alsamixer can cope with this, but I don't know
about any other mixers. :)
I think "alsactl restore" already does the right thing for controls
that have changed.
> 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 :)
With a mixer control "Clock Source", of course. :)
Or are you talking about new samples rates made available?
Regards,
Clemens
next prev parent reply other threads:[~2010-05-12 6:41 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
2010-05-12 6:41 ` Clemens Ladisch [this message]
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=4BEA4D98.5010900@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@caiaq.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).