From: Vinod Koul <vinod.koul@intel.com>
To: Liam Girdwood <liam.r.girdwood@intel.com>
Cc: jeeja.kp@intel.com, alsa-devel@alsa-project.org,
broonie@kernel.org, subhransu.s.prusty@intel.com,
lgirdwood@gmail.com
Subject: Re: [RFC 2/4] ASoC: Intel: Add merrifield machine driver
Date: Tue, 6 May 2014 22:19:45 +0530 [thread overview]
Message-ID: <20140506164945.GD28638@intel.com> (raw)
In-Reply-To: <1399389439.2814.30.camel@loki>
On Tue, May 06, 2014 at 04:17:19PM +0100, Liam Girdwood wrote:
> On Mon, 2014-05-05 at 23:31 +0530, Vinod Koul wrote:
> > +/* TODO: find better way of doing this */
> > +static struct snd_soc_dai *find_codec_dai(struct snd_soc_card *card, const char *dai_name)
> > +{
> > + int i;
> > + for (i = 0; i < card->num_rtd; i++) {
> > + if (!strcmp(card->rtd[i].codec_dai->name, dai_name))
> > + return card->rtd[i].codec_dai;
> > + }
> > + pr_err("%s: unable to find codec dai\n", __func__);
> > + /* this should never occur */
> > + WARN_ON(1);
> > + return NULL;
> > +}
> > +
>
> It would be good if we could eventually make the above 2 calls generic
> in core. Seem to be quite useful functions.
Yes I didnt do that as I wanted to check if we have a better method or not. With
multi-codec systems we dont have single codec for the card so finding this would
need lookup or else... Somehow I think we should have simpler solution, Mark??
> > +static int mrfld_wm8958_compr_set_params(struct snd_compr_stream *cstream)
> > +{
> > + return 0;
> > +}
>
> Do we need to implement this if it's not used ?
My bad, this was supposed to be removed but... :)
--
~Vinod
next prev parent reply other threads:[~2014-05-06 17:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 18:01 [RFC 0/4] Add support for merrfield audio Vinod Koul
2014-05-05 18:01 ` [RFC 1/4] ASoC: Intel: add SSP BE DAIs Vinod Koul
2014-05-06 14:42 ` Liam Girdwood
2014-05-05 18:01 ` [RFC 2/4] ASoC: Intel: Add merrifield machine driver Vinod Koul
2014-05-06 15:17 ` Liam Girdwood
2014-05-06 16:49 ` Vinod Koul [this message]
2014-05-06 15:54 ` Lars-Peter Clausen
2014-05-06 16:58 ` Vinod Koul
2014-05-06 18:17 ` Lars-Peter Clausen
2014-05-07 4:51 ` Vinod Koul
2014-05-05 18:01 ` [RFC 3/4] ASoC: Intel: add the low level dsp driver for mrfld Vinod Koul
2014-05-06 15:45 ` Liam Girdwood
2014-05-06 16:44 ` Vinod Koul
2014-05-07 6:09 ` Jarkko Nikula
2014-05-07 7:25 ` Vinod Koul
2014-05-05 18:01 ` [RFC 4/4] ASoC: Intel: add support for mrfld DPCM platform Vinod Koul
2014-05-06 15:53 ` Liam Girdwood
2014-05-06 16:46 ` Vinod Koul
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=20140506164945.GD28638@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jeeja.kp@intel.com \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@intel.com \
--cc=subhransu.s.prusty@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