Re: ASoC and a codec that can't be controlled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2007-05-25 at 15:17 -0500, Timur Tabi wrote:
> Liam Girdwood wrote:
> 
> > These are used for setting up the dynamic audio power management and
> > won't be needed in stand alone mode.
> 
> So if I don't care about power management, can I completely ignore anything with "dapm" in it?

Yes.

> 
> Also, do I need a codec driver at all, even if I can't control the codec?  That is, can I 
> do stuff like this:
> 
> static struct snd_soc_device mysoc_snd_devdata = {
> 	.machine = &snd_soc_machine_mysoc,
> 	.platform = &mysoc_soc_platform,
> };
> 
> static struct snd_soc_dai_link mpc8610hpcd_dai = {
> 	.name = "CS4270",
> 	.stream_name = "CS4270",
> 	.cpu_dai = &mysoc_i2s_dai,
> 	.init = mpc8610hpcd_machine_init,
> 	.ops = &mpc8610hpcd_ops,
> };

Yes, although my feeling is that a codec "driver" would still be needed
to define the capabilities of your codec within the audio subsystem.

e.g. supported sample rates, interface formats, etc

Liam

_______________________________________________
Alsa-devel mailing list
Alsa-devel@xxxxxxxxxxxxxxxx
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux