On Thu, Feb 18, 2016 at 01:27:26PM +0530, Vaibhav Agarwal wrote: > Yes, I agree machine driver is the real owner of soc card & should > decide/choose on possible capabilities of codec. Also, codec may wish > to choose from different soc cards registered based on the > functionality supported. Say, performance mode using I2S interface, > otherwise feature mode (supporting multichannel, etc.) using PCM > interface or may be via USB interface. No, the driver should offer whatever the hardware is capable of doing and let userspace make any policy decisions. > In case we are using generic codec driver (existing in > sound/soc/codecs), it would need a helper driver to glue it to soc > card dynamically. Otherwise, for a specific platform, we can have a > wrapper codec driver that can fetch capabilities of removable codec > (may be via binary data) and expose them to already known soc cards > for that device. It sounds like there might be some review concerns with some of this stuff...
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
