alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
	"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>,
	lgirdwood@gmail.com
Subject: Re: [PATCH v7 5/7] ASoC: Intel: mrfld: add the DSP DAPM widgets
Date: Mon, 6 Oct 2014 08:10:10 +0530	[thread overview]
Message-ID: <20141006024010.GQ1638@intel.com> (raw)
In-Reply-To: <20141002181228.GA4273@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1132 bytes --]

On Thu, Oct 02, 2014 at 07:12:28PM +0100, Mark Brown wrote:
> On Fri, Sep 19, 2014 at 04:46:06PM +0530, Subhransu S. Prusty wrote:
> 
> > +#define SST_MMX_DECLARE_MIX_CONTROLS(kctl_name)			\
> > +	static const struct snd_kcontrol_new kctl_name[] = {			\
> > +		SOC_DAPM_SINGLE("media0_in", SND_SOC_NOPM, SST_IP_MEDIA0, 1, 0),	\
> > +		SOC_DAPM_SINGLE("media1_in", SND_SOC_NOPM, SST_IP_MEDIA1, 1, 0),	\
> > +		SOC_DAPM_SINGLE("media2_in", SND_SOC_NOPM, SST_IP_MEDIA2, 1, 0),	\
> > +		SOC_DAPM_SINGLE("media3_in", SND_SOC_NOPM, SST_IP_MEDIA3, 1, 0),	\
> > +	}
> 
> These should be Switch controls?
Yup I will fix this one.

> 
> > +	snd_soc_dapm_new_controls(dapm, sst_dapm_widgets,
> > +			ARRAY_SIZE(sst_dapm_widgets));
> > +	snd_soc_dapm_add_routes(dapm, intercon,
> > +			ARRAY_SIZE(intercon));
> > +	snd_soc_dapm_new_widgets(dapm->card);
> 
> We should be able to do this from the component but we can't yet...
We can convert once ready :)

I still have lots of stuff to do once this series is in. We also need to
enable dynamic firmware here once liam upstreams basic support :)

Thanks
-- 
~Vinod

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2014-10-06  3:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-19 11:16 [PATCH v7 0/7] Add mrfld DSP topology and widgets Subhransu S. Prusty
2014-09-19 11:16 ` [PATCH v7 1/7] ASoC: Intel: mrfld: add the gain controls Subhransu S. Prusty
2014-09-25 14:20   ` Mark Brown
2014-09-25 14:06     ` Vinod Koul
2014-09-19 11:16 ` [PATCH v7 2/7] ASoC: Intel: mfld-pcm: add control for powering up/down dsp Subhransu S. Prusty
2014-09-25 14:22   ` Mark Brown
2014-09-19 11:16 ` [PATCH v7 3/7] ASoC: Intel: mrfld: add DSP core controls Subhransu S. Prusty
2014-09-25 15:08   ` Mark Brown
2014-09-25 16:08     ` Vinod Koul
2014-09-27 11:13       ` Mark Brown
2014-09-29  6:00         ` Vinod Koul
2014-09-19 11:16 ` [PATCH v7 4/7] ASoC: Export dapm_kcontrol_get_value Subhransu S. Prusty
2014-10-02 18:13   ` Mark Brown
2014-09-19 11:16 ` [PATCH v7 5/7] ASoC: Intel: mrfld: add the DSP DAPM widgets Subhransu S. Prusty
2014-10-02 18:12   ` Mark Brown
2014-10-06  2:40     ` Vinod Koul [this message]
2014-10-06  2:44       ` Vinod Koul
2014-10-06 10:50         ` Mark Brown
2014-09-19 11:16 ` [PATCH v7 6/7] ASoC: Intel: mfld-pcm: add FE and BE ops Subhransu S. Prusty
2014-09-19 11:16 ` [PATCH v7 7/7] ASoC: Intel: mrfld: add the DSP mixers Subhransu S. Prusty

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=20141006024010.GQ1638@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.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;
as well as URLs for NNTP newsgroup(s).