Hi Sameer
But, I guess new driver 1st version is focus to detecting normal-link and DPCM-link only.
Do you plan to propose something like enum for card2 and has scope for extension, where link type can be normal/DPCM/codec-to-codec/etc., ? Since there are so many board variants and may have some specific requirements, I am wondering being able to detect link type from DT should be the only motivation for a new driver.
I'm now thinking that new one can detect normal-link, DPCM-link, multi-CPU / multi-Codec, Codec-to-Codec as normal audio-graph feature. And has .hook callback for Eeach board specific feature. see my previous mail which was To:Pierre-Louis But, it is still under idea, not yet fixed.
I am afraid that even the new driver won't work as it is for my case unless a similar compatible and flag exposed for it. So I am not sure how different it would be from [0].
Yes, that is the reason why I'm discussing how to implement new driver. If we have "-cc-" and you use it on upsteam, we will keep current card driver as-is, and I will create new "card2" driver. Because keeping compatible will be difficult. But I'm not sure what should I do.
Thank you for your help !!
Best regards --- Kuninori Morimoto