On Wed, Oct 25, 2017 at 02:03:30PM +0300, Peter Ujfalusi wrote:
On 2017-10-08 16:35, Andrey Utkin wrote:
It seems that successful compilation is quite close, I have just one fatal compilation issue currently:
snd_soc_platform_driver from AESS sources has .read, .write callbacks pointing to omap_aess_oppwidget_{read,write}(), but in current sound drivers structure, these callbacks are defined only for snd_soc_codec_driver. Then, I can't make sense of "oppwidget" as codec. So, please help me to resolve my confusion.
As far as I can see they serve the same purpose, to configure the firmware (widgets, features, controls in the firmware). All of these need to be mostly rewritten to soc-topology, the thing asoc-fw did need to be done with the new soc-topology tools to create the new firmware.
Peter,
I tried many times to think of any plan to tackle this, but the best plan so far is "make Peter to do as much as possible".
It is obvious that there's a lot to know about this hardware and existing firmware. What I've done here so far is a coding monkey job, and I really don't possess a fraction of knowledge you have.
What about, say, arbitrary amount of beer to motivate you to help with the rest of this task? Please let me know what you would accept.
What would be great is to have a clear framework to proceed. With hints being that high-level as what you've suggested above, I feel lost. I would need to spend a lot of time before I make sense of how to proceed, and this causes me to procrastinate on this every time.
Please don't take this message as a rant or dissatisfaction with your help - I realize that you are giving your helpful hints for Pyra project out of good will. I just really want to push this task forward, but I find it not practically feasible to succeed on my own.