On Mon, May 15, 2017 at 10:41:43AM +0200, Vishal Thanki wrote: > Thanks for you comments. Actually in our custom hardware, the codec is > not accessible/visible from kernel directly, rather additional MCU > controls and configures it. However MCU needs the I2S clocks and data > from kernel. So I am using I2S platform driver from Linux just to > configure I2S clocks, and registering a dummy codec driver to DAI link > in DT, so that codec can be instantiated and clocks can be enabled > from user-space ALSA utils while accessing this dummy codec. Please > suggest if there is any better way to achieve this kind of > configuration. You should be representing the I2S control offered by the MCU as a CODEC driver. Even if there's no changes ever made there must be some constraints.
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
