alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Vinod Koul <vinod.koul@intel.com>,
	Mark Brown <broonie@kernel.org>,
	liam.r.girdwood@linux.intel.com,
	Mengdong <mengdong.lin@intel.com>
Cc: patches.audio@intel.com, alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/4] ASoC: Intel: Skylake: Add token support for topology data
Date: Wed, 17 Aug 2016 14:59:28 +0800	[thread overview]
Message-ID: <57B40B50.8000105@linux.intel.com> (raw)
In-Reply-To: <20160812105531.GL9681@localhost>



On 08/12/2016 06:55 PM, Vinod Koul wrote:
> On Fri, Aug 12, 2016 at 11:41:07AM +0100, Mark Brown wrote:
>> On Fri, Aug 12, 2016 at 12:29:49PM +0530, Vinod Koul wrote:
>>> With topology changes in alsa-lib, driver data for modules can now be
>>> passed in topology conf file using tuples.
>>>
>>> These changes allow private data to represented by tuples of type UUID,
>>> byte, short, word and strings.
>>
>> A question I ask quite often: the topology code has been in mainline
>> since v4.2 but still has a big old #error at the top preventing any
>> actual use from userspace.  We're now more than a year after the code
>> was originally merged and still no patches to actually make this ABI
>> usable from userspace.  Where are we at with that?
>
> Mengdong was working on last set of features for providing DAIlinks. After
> that we dont have any more updates planned on topology API.

There will be 2 more series to bring some topology ABI update. The code 
is ready and verified. And we will not modify ABI to break backward 
compatibility after this.

>
> So I think we cna remove it for current cycle. Mengdong cna you please
> confirm..

I think we may remove those #error after this cycle of upstreaming. 
We'll resume the patch upstreaming this week.

Thanks
Mengdong

  reply	other threads:[~2016-08-17  6:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-12  6:59 [PATCH 0/4] ASoC: Intel: Skylake: Add token support for topology data Vinod Koul
2016-08-12  6:59 ` [PATCH 1/4] ASoC: uapi: Intel: Skylake: Define vendor specific tokens Vinod Koul
2016-08-22 17:59   ` Applied "ASoC: uapi: Intel: Skylake: Define vendor specific tokens" to the asoc tree Mark Brown
2016-08-12  6:59 ` [PATCH 2/4] ASoC: Intel: Skylake: Parse vendor tokens to build module data Vinod Koul
2016-08-22 17:59   ` Applied "ASoC: Intel: Skylake: Parse vendor tokens to build module data" to the asoc tree Mark Brown
2016-08-12  6:59 ` [PATCH 3/4] ASoC: Intel: Skylake: Remove dfw config and associated structures Vinod Koul
2016-08-22 17:59   ` Applied "ASoC: Intel: Skylake: Remove dfw config and associated structures" to the asoc tree Mark Brown
2016-08-12  6:59 ` [PATCH 4/4] ASoC: Intel: Skylake: Parse manifest data Vinod Koul
2016-08-22 17:47   ` Mark Brown
2016-08-23  4:02     ` Vinod Koul
2016-08-12 10:41 ` [PATCH 0/4] ASoC: Intel: Skylake: Add token support for topology data Mark Brown
2016-08-12 10:55   ` Vinod Koul
2016-08-17  6:59     ` Mengdong Lin [this message]
2016-08-17 10:01       ` Mark Brown
2016-08-17 15:03         ` Lin, Mengdong

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=57B40B50.8000105@linux.intel.com \
    --to=mengdong.lin@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@intel.com \
    --cc=patches.audio@intel.com \
    --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).