On Fri, May 29, 2015 at 06:35:03PM +0100, Mark Brown wrote:
On Fri, May 29, 2015 at 01:45:44PM +0530, Vinod Koul wrote:
well userspace parsing is only for the pin mapping and changes which users want to do on their systems. For basic things the default graph will be read by existing HDA parser and codec driver will create widgets based on that. The generic HDA codec library should do most and the HDA ASoC codecs should do device specfic work (like existing patch_xxx)
So we *are* planning to continue to use the existing CODEC support but with some different interfacing on top of it?
Nope. Existing codecs wont be reused here.
We are doing new ASoC HDA codec drivers which use common hdac parsing logic. Since some codecs need own methods we can't write a single HDA generic codec, and had to do with generic codec parser and then specfic driver (HDMI, ALC to start with) on top.
And it's the reason I suggested for pending merge until the codec side is ready. We need the topology stuff merged at first, then HDA-codec driver together with user-space side.
I dont mind if code doesnt get merged into next merge window and put in one after that. But in needs to get accepted is some topic branch so that subsequent series can be psted and reviewed, merged. Btw users will not see unless we have machine driver. I will add the disable feature after this series, so no user conflicts occur
I need to have another look through. TBH I suspect it would be easier with something that was more of a minimum viable prototype than with a part of the system - with something like this it's as much the overall shape of the solution that's being reviewed as anything else.
Sure, please do let us know if you have more questions on this and overall approach.