I have few questions on Audio codec driver integration.
I have got Audio codec driver from audio codec vendor. It contains DAPM widgets and audio routes.
In TX1 device tree, there is a property called “nvidia,audio-routing”. As routing information is already available in codec driver, Can we ignore this “nvidia,audio-routing” in device tree?
What is the significance of this property?
Hello, Pal:
It’s OK to connect 2 different audio codecs in Jetson, since the I2S modules are working independently. Just port the driver, and that will be 2 audio device.
There’s no specific document for this. The main part follows ALSA framework.
Hello, Pal:
That looks weird. You’d better check ALSA doc and samples in kernel.
The change you made is 2 DAI links in same codec.
But you mentioned that you have 2 difference codecs.
Hello, Pal:
In Jetson L4T reference, there’s no multi-codec samples. You may search the internet for more help. That part is common issue, and not NV-specific.
Okay. I will look in internet. As Tegra supports multiple I2S interfaces, I thought multiple codec reference may be already there. So just checked with You.
As per my design, One Audio codec is connected to one I2S interface of Tegra and other Audio codec is connected to another I2S interface of Tegra. Was that your understanding also?
In CPU<–> Codec DAI link, Codec names are configured.