[alsa-devel] switching pcm devices dynamically when using dmix
baeksan at ccrma.stanford.edu
Mon Aug 8 19:27:32 CEST 2011
I'll have a look at the dynamic PCM code. That is a fairly new feature
correct? Perhaps I can use that as an example.
> OTOH, if it handles only the switch for the next open, it'd be just to
> change the configuration, so it sounds feasible.
This is mainly my goal. User application would know when this is switching,
close the current device, reconfigure, open the new device and then continue
On Mon, Aug 8, 2011 at 9:35 AM, Liam Girdwood <lrg at ti.com> wrote:
> On Mon, 2011-08-08 at 18:16 +0200, Takashi Iwai wrote:
> > At Mon, 8 Aug 2011 09:08:49 -0700,
> > Baek Chang wrote:
> > >
> > > Would it be possible to implement this feature in another plugin? For
> > > example, some plugin called "switch", that would take a parameter for
> > > or card name/number that would close the current device and open the
> > > requested device? Would this be worth investigating?
> > The question is whether it allows the dynamic switch of the running
> > PCM stream. If yes, it'd be tough to implement, I suppose.
> > OTOH, if it handles only the switch for the next open, it'd be just to
> > change the configuration, so it sounds feasible.
> Fwiw, the ASoC dynamic PCM code does something a little similar and can
> dynamically remap the PCM stream to different backend DAIs (e.g. McBSP,
> McPDM, McASP etc) at runtime based on kcontrol mixer settings. This wont
> help for routing between cards but could be useful for routing between
> different physical DAIs on the same card.
More information about the Alsa-devel