@dbaluta we specify all our DAI links in a single machine driver and yes we have a single sound card with multiple devices for different codecs
Do you have a requirement for using separate tplg file for the different DAIs? Its not a big deal but I'm guessing you'd need 2 separate component drivers and therefore have separate cards for the 2 topologies
hey all! FYI, we now tagged a Zephyr mainline git version in the build scripts for the v2.0 branch. this is still very loose way to define the dependency, but at least something to indicate a working combination of SOF and Zephyer. let me know if anyone has ideas how to best tackle this dependency in the future. I did try v2.7.0 as well, but that is missing key patches... maybe in the future we can sync to a public release
@dbaluta FYI ^^^
@kv2019i great! thanks for pinging me
we thought about this together with our Yocto team. the preffered way (as we already doing with SOF is to have a separate branch)
but having a tag i think can work for a while.
do we plan to do this for each SOF release, right?
zephyr development model looked a little bit different than SOF (I think they have some sort of LTS release every year and keep that for customers)
I think we'll do this for a while now. one recommendation from Zephyr folks for us to branch a stable release and cherry-pick patches SOF needs. we could host this in SOF github project (we already have a copy of zephyr there)
probably for all platforms, we'll need a pretty bleeding edge Zephyr in practise, so we'll probably need a few iterations before we can move to use a Zephyr LTS for SOF
I think that would be a good choice. Initially, I suggested to fork zephyr internally. but i think doing that on SOF github is better.
@kv2019i can you point me to the script you use the zephyr tagged version? I'm trying to integrate this internally now