public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: Mengdong Lin <mengdong.lin@intel.com>,
	alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/3] topology: Add C templates structure for building topology from C programs
Date: Fri, 07 Aug 2015 18:14:20 +0200	[thread overview]
Message-ID: <s5htwsbf543.wl-tiwai@suse.de> (raw)
In-Reply-To: <1438963434-6407-2-git-send-email-liam.r.girdwood@linux.intel.com>

On Fri, 07 Aug 2015 18:03:52 +0200,
Liam Girdwood wrote:
> 
> From: Mengdong Lin <mengdong.lin@intel.com>
> 
> Define structures that can be used by applications to directly build topology
> data instead of using text files. The application will build up the topology
> data by populating the template structures for each object type and then
> registering the template with the topology core.
> 
> Signed-off-by: Mengdong Lin <mengdong.lin@intel.com>
> Signed-off-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
> ---
>  include/sound/asoc.h      |   2 +
>  include/topology.h        | 178 ++++++++++++++++++++++++++++++++++++++++++++++
>  src/topology/builder.c    |  38 +++++-----
>  src/topology/ctl.c        |  38 +++++-----
>  src/topology/dapm.c       |  28 ++++----
>  src/topology/data.c       |  10 +--
>  src/topology/elem.c       |  26 +++----
>  src/topology/parser.c     |   6 +-
>  src/topology/pcm.c        |  34 ++++-----
>  src/topology/text.c       |   2 +-
>  src/topology/tplg_local.h |  23 +-----
>  11 files changed, 273 insertions(+), 112 deletions(-)
> 
> diff --git a/include/sound/asoc.h b/include/sound/asoc.h
> index c642855..1b19739 100644
> --- a/include/sound/asoc.h
> +++ b/include/sound/asoc.h
> @@ -15,6 +15,8 @@
>  #ifndef __LINUX_UAPI_SND_ASOC_H
>  #define __LINUX_UAPI_SND_ASOC_H
>  
> +#include <sound/type_compat.h>
> +

Don't modify this file specific to alsa-lib.  This file should be a
copy from the kernel uapi header.

>  #ifdef __cplusplus
> diff --git a/src/topology/builder.c b/src/topology/builder.c
> index a944866..3bccd44 100644
> --- a/src/topology/builder.c
> +++ b/src/topology/builder.c
> @@ -141,7 +141,7 @@ static int write_elem_block(snd_tplg_t *tplg,
>  		if (elem->compound_elem)
>  			continue;
>  
> -		if (elem->type != OBJECT_TYPE_DAPM_GRAPH)
> +		if (elem->type != SND_TPLG_TYPE_DAPM_GRAPH)

I prefer splitting this systematic replacement in another patch.
Then it's easier to check by a script, and the size won't matter.
Otherwise the whole patch became too big and difficult to follow.


thanks,

Takashi

  reply	other threads:[~2015-08-07 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07 16:03 [PATCH 0/3] topology: Add external API for building topology data Liam Girdwood
2015-08-07 16:03 ` [PATCH 1/3] topology: Add C templates structure for building topology from C programs Liam Girdwood
2015-08-07 16:14   ` Takashi Iwai [this message]
2015-08-10 10:23     ` Liam Girdwood
2015-08-07 16:03 ` [PATCH 2/3] topology: A API calls to directly build topology data from templates Liam Girdwood
2015-08-07 16:03 ` [PATCH 3/3] topology: add support for adding bytes controls to widgets Liam Girdwood

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=s5htwsbf543.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=mengdong.lin@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