From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, vinod.koul@intel.com,
mengdong.lin@intel.com, Mark Brown <broonie@kernel.org>,
rakesh.a.ughreja@intel.com, liam.r.girdwood@intel.com,
hardik.t.shah@intel.com, subhransu.s.prusty@intel.com
Subject: Re: [PATCH 0/7] topology: Add support for vendor tuples
Date: Mon, 28 Mar 2016 16:56:08 +0800 [thread overview]
Message-ID: <56F8F1A8.4010604@linux.intel.com> (raw)
In-Reply-To: <s5hshzb6nlp.wl-tiwai@suse.de>
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.html
>
> 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
prev parent reply other threads:[~2016-03-28 8:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 3:05 [PATCH 0/7] topology: Add support for vendor tuples mengdong.lin
2016-03-24 3:06 ` [PATCH 1/7] topology: Use the generic pointer to free an element's object mengdong.lin
2016-03-24 3:06 ` [PATCH 2/7] topology: Define a free handler for the element mengdong.lin
2016-03-24 3:07 ` [PATCH 3/7] topology: Add doc for vendor tuples mengdong.lin
2016-03-24 3:07 ` [PATCH 4/7] topology: ABI - Define types " mengdong.lin
2016-03-24 3:07 ` [PATCH 5/7] topology: Add support for vendor tokens mengdong.lin
2016-03-24 3:07 ` [PATCH 6/7] topology: Add support for parsing vendor tuples mengdong.lin
2016-03-29 14:13 ` Takashi Iwai
2016-03-30 7:15 ` Mengdong Lin
2016-03-24 3:07 ` [PATCH 7/7] topology: Build data objects with tuples mengdong.lin
2016-03-24 11:20 ` [PATCH 0/7] topology: Add support for vendor tuples Mark Brown
2016-03-25 5:39 ` Mengdong Lin
2016-03-28 7:49 ` Mengdong Lin
2016-03-28 7:57 ` Takashi Iwai
2016-03-28 8:56 ` Mengdong Lin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56F8F1A8.4010604@linux.intel.com \
--to=mengdong.lin@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=hardik.t.shah@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=mengdong.lin@intel.com \
--cc=rakesh.a.ughreja@intel.com \
--cc=subhransu.s.prusty@intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).