On 03/28/2016 03:57 PM, Takashi Iwai wrote:
On Mon, 28 Mar 2016 09:49:36 +0200, Mengdong Lin wrote:
Hi Takashi and Mark,
Despite the ABI update, could you help to review if this is a doable solution to define vendor-specific data by tuples?
I'll check it tomorrow, as now it's still in Easter holidays.
Thank you very much!
Previously there was a patch for Skylake topology conf file, but this file try to import vendor specific config data as a binary blob from other files. The patch was refused for on license of the binary blob and we were suggested to expose the layout of the data. This patch series is to meet this request, providing a way for vendors to define their structured private data.
Here is the link of the refused patch: [alsa-devel] [PATCH] conf: topology: Add topolgy for skylake i2s configuration
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-February/104099.ht...
The changes are good if they are mandatory. But too late for 4.6, in anyway. And, the missing piece is the "grand plan". When this API/ABI is supposed to be stabilized and released?
We're checking topology feature requests for platforms later than Skylake. We expect to finish the feature collection this or next week. Then we can give a more accurate schedule.
Now the unstable ABI is mainly for ASoC DAI and DAI links. Platforms later than Skylake need them. We're checking the gap between existing ABI and new requests.
Thanks Mengdong