On Mon, Nov 28, 2011 at 04:49:18PM -0800, Patrick Lai wrote:
In CODEC driver, I will declare codec dai for each port. Then, I will enhance ASoC framework to take a list of CODEC DAIs and pass list of CODEC DAIs back to callback function such as startup, hw_param, prepare, trigger. I believe this approach will not require massive amount of change to framework.
The above is really vauge so it's hard to comment in any detail. I'm not sure it's worth trying to be too non-invasive, anything controlling hardware is going to have to understand what's going on at the physical level anyway and the host side is going to have to interoperate with the Slimbus framework. The core is also going to need to know about the channel groups to allocate and destroy them as required. It seems like being more explicit might be easier.
Also note that the work on submitting your Silmbus driver core to mainline appears totally stalled, there was just an initial posting but no followup.