From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
mengdong.lin@intel.com, vinod.koul@intel.com,
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: Fri, 25 Mar 2016 13:39:19 +0800 [thread overview]
Message-ID: <56F4CF07.6080001@linux.intel.com> (raw)
In-Reply-To: <20160324112051.GW2566@sirena.org.uk>
On 03/24/2016 07:20 PM, Mark Brown wrote:
> On Thu, Mar 24, 2016 at 11:05:29AM +0800, mengdong.lin@linux.intel.com wrote:
>> From: Mengdong Lin <mengdong.lin@linux.intel.com>
>>
>> This series addes support for vendor tuples to topology, to avoid
>> importing binary data blob from other files.
>>
>> Backward compatibility of ABI is not impacted. A kernel patch is also
>> submitted "ASoC: topology: ABI - Define types for vendor tuples".
>
> It's now been three kernel releases since the original code was merged
> and we've still not seen any effort to make the ABI actually available.
> Where are we with that? I've mentioned it a few times previously but
> don't really recall any response.
>
We've been working on this. I'm sorry we're still not fast enough.
This ABI update is introduced by previous failure to upstream the
topology configuration file for Skylake, which imports vendor-specific
binary data from another file. It was refused because of the license of
the binary data is not obvious. So we turn to use vendor tuples, because
the vendor tuples can show the layout and meaning of binary data, which
can help to check if the data is safe to open source.
This ABI change has no impact on backward compatibility.
Also, the audio device driver for new platforms are under development
now, which uses topology for DAI and DAI links. We're checking if
current ABI can meet all requirements for the new platforms. This may
still need a few weeks.
Thanks
Mengdong
next prev parent reply other threads:[~2016-03-25 5:37 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 [this message]
2016-03-28 7:49 ` Mengdong Lin
2016-03-28 7:57 ` Takashi Iwai
2016-03-28 8:56 ` Mengdong Lin
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=56F4CF07.6080001@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).