alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mengdong Lin <mengdong.lin@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, vinod.koul@intel.com,
	hardik.t.shah@intel.com, guneshwor.o.singh@intel.com,
	liam.r.girdwood@linux.intel.com, broonie@kernel.org,
	mengdong.lin@intel.com
Subject: Re: [PATCH 0/2] topology: Support widgets' stream name and file inclusion for text conf file
Date: Wed, 19 Oct 2016 12:06:28 +0800	[thread overview]
Message-ID: <5806F144.7060108@linux.intel.com> (raw)
In-Reply-To: <s5hbmyj6syh.wl-tiwai@suse.de>



On 10/17/2016 08:49 PM, Takashi Iwai wrote:
> On Mon, 17 Oct 2016 07:55:21 +0200,
> mengdong.lin@linux.intel.com wrote:
>>
>> From: Mengdong Lin <mengdong.lin@linux.intel.com>
>>
>> This series doesn't require or cause any ABI updates. It doesn't need the
>> kernel patches that trying to udpate ABI from v4 or v5.
>>
>> It just fix a missing feature and enhance text conf file to support
>> including files to control the increasing size of text conf files.
>
> The inclusion of a file can be done in alsaconf syntax via <xxx>,
> too.  We may extend it if needed instead?


Thanks for your review and advice!

It seems etter to extend and reuse alsaconf syntax, instead of adding 
topology specific code. This can also benefit UCM if users want to split 
common codec or SOC settings to other files.

alsaconf already support using absolute path to include a file. But it 
seems we cannot give a relative path (e.g. just a file name) and a 
configuration directory by <confdir:xxx>. I'll try to extend alsaconf.

The other patch is a bug fixing, if it's okay, could it be merged first?

Thanks
Mengdong

>
> The patches themselves look OK, so I'm not strongly against merging
> them, but just to make sure our standpoint.
>
>
> thanks,
>
> Takashi
>
>>
>> Mengdong Lin (2):
>>    topology: Fix missing stream name of widgets in text conf file
>>    topology: Add support for included files
>>
>>   include/topology.h        |  38 +++++
>>   src/topology/dapm.c       |  10 ++
>>   src/topology/parser.c     | 374 +++++++++++++++++++++++++++++++++++++++++++++-
>>   src/topology/tplg_local.h |  17 +++
>>   4 files changed, 434 insertions(+), 5 deletions(-)
>>
>> --
>> 2.5.0
>>
>

      parent reply	other threads:[~2016-10-19  4:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17  5:55 [PATCH 0/2] topology: Support widgets' stream name and file inclusion for text conf file mengdong.lin
2016-10-17  5:57 ` [PATCH 1/2] topology: Fix missing stream name of widgets in " mengdong.lin
2016-10-17  5:58 ` [PATCH 2/2] topology: Add support for included files mengdong.lin
2016-10-17 12:49 ` [PATCH 0/2] topology: Support widgets' stream name and file inclusion for text conf file Takashi Iwai
2016-10-19  3:45   ` Vinod Koul
2016-10-20  6:01     ` Mengdong Lin
2016-10-19  4:06   ` 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=5806F144.7060108@linux.intel.com \
    --to=mengdong.lin@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=guneshwor.o.singh@intel.com \
    --cc=hardik.t.shah@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@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).