On Friday 26 November 2010 15:41:52 ext Mark Brown wrote:
On Fri, Nov 26, 2010 at 03:35:48PM +0200, Jarkko Nikula wrote:
Peter Ujfalusi peter.ujfalusi@nokia.com wrote:
If DAPM core knows which widget belongs to which component, than I see no real problem with this method. The DAPM would work just fine. The PCM operatins would only apply to component with DAI.
Actually these are already well separated in current ASoC. Like my RFC patch didn't not need touch soc-dapm.c at all and efectively other changes were around codec probing/removal and by not registering the PCM.
That's pretty much where I'm coming from - we already have most of the infrastructure, we just need to get the devices into the system but once we do that we should be able to cope with everything already.
So, if let's say I rewrite the tpa6130a2 driver as DAIless CODEC driver, and connect to a system, where we already have a proper codec. What should I expect? Can this work with 'reasonable' ;) amount of work (or non) on the core side?