Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/2] ASoC: utils: Add internal call to determine if DAI is dummy.
Date: Wed, 08 Jan 2014 11:49:15 +0000	[thread overview]
Message-ID: <1389181755.2346.12.camel@loki> (raw)
In-Reply-To: <s5hvbxu215f.wl%tiwai@suse.de>

On Wed, 2014-01-08 at 11:55 +0100, Takashi Iwai wrote:
> At Wed,  8 Jan 2014 10:40:18 +0000,
> Liam Girdwood wrote:
> > +
> >  struct snd_soc_dai_ops {
> >  	/*
> >  	 * DAI clocking configuration, all optional.
> > diff --git a/sound/soc/soc-utils.c b/sound/soc/soc-utils.c
> > index 6ebdfd9..7f22ca3 100644
> > --- a/sound/soc/soc-utils.c
> > +++ b/sound/soc/soc-utils.c
> > @@ -119,6 +119,13 @@ static struct snd_soc_dai_driver dummy_dai = {
> >  	 },
> >  };
> >  
> > +int snd_soc_dai_is_dummy(struct snd_soc_dai *dai)
> > +{
> > +	if (dai->driver == &dummy_dai)
> > +		return 1;
> > +	return 0;
> > +}
> 
> No need for EXPORT_SYMBOL since it's for internal use only, or just
> forgotten?

No need for the EXPORT_SYMBOL as the core soc-*.c files are linked into
the same module and it's for internal use only.

Liam 

  reply	other threads:[~2014-01-08 11:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 10:40 [PATCH 1/2] ASoC: utils: Add internal call to determine if DAI is dummy Liam Girdwood
2014-01-08 10:40 ` [PATCH 2/2] ASoC: DAPM: Automatically connect DAI link widgets in DAPM graph Liam Girdwood
2014-01-08 10:55 ` [PATCH 1/2] ASoC: utils: Add internal call to determine if DAI is dummy Takashi Iwai
2014-01-08 11:49   ` Liam Girdwood [this message]
2014-01-08 12:08 ` Mark Brown

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=1389181755.2346.12.camel@loki \
    --to=liam.r.girdwood@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=tiwai@suse.de \
    /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