From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <lgirdwood@gmail.com>,
Nenghua Cao <nhcao@marvell.com>, Henry zhao <xzhao10@marvell.com>,
Yacine Belkadi <yacine.belkadi.1@gmail.com>,
cxie4@marvell.com
Subject: Re: [PATCH] ASOC:DAPM: extend dapm kcontrol to support runtime route update
Date: Sun, 15 Dec 2013 19:21:16 +0530 [thread overview]
Message-ID: <20131215135116.GR29580@intel.com> (raw)
In-Reply-To: <20131212104347.GH11044@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]
On Thu, Dec 12, 2013 at 10:43:47AM +0000, Mark Brown wrote:
> On Thu, Dec 12, 2013 at 04:06:59PM +0800, Nenghua Cao wrote:
> > From: nhcao <nhcao@marvell.com>
> >
> > DPCM can dynamically alter the FE to BE PCM links at runtime based
> > on mixer setting updates. DAPM has provided common get/put function for
> > mixer/mux. But these function doesn't call soc_dpcm_runtime_update()
> > func to update pcm links. This patch defines a DPCM DPCM kcontrol. For
> > this control, the common get/put function will update FE to BE links
> > dynamically. This patch has no impact to the current code.
>
> Why shouldn't we just add the DPCM update to the standard controls -
> what's the benefit in defining a new set of controls?
Precisely my thoughts too, I think that would be a better approach!
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-12-15 14:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 8:06 [PATCH] ASOC:DAPM: extend dapm kcontrol to support runtime route update Nenghua Cao
2013-12-12 10:43 ` Mark Brown
[not found] ` <F766E4F80769BD478052FB6533FA745D4E76B8FA79@SC-VEXCH4.marvell.com>
2013-12-12 11:07 ` Mark Brown
2013-12-13 11:33 ` Nenghua Cao
2013-12-13 11:37 ` Takashi Iwai
2013-12-13 11:42 ` Mark Brown
2013-12-13 12:11 ` Nenghua Cao
2013-12-13 11:53 ` Nenghua Cao
2013-12-13 12:10 ` Mark Brown
2013-12-15 13:51 ` Vinod Koul [this message]
2013-12-12 16:52 ` Takashi Iwai
2013-12-13 11:25 ` Nenghua Cao
-- strict thread matches above, loose matches on Subject: below --
2013-12-13 11:20 [PATCH V1] " Nenghua Cao
2013-12-13 11:20 ` [PATCH] " Nenghua Cao
2013-12-13 12:10 [PATCH V2] ASOC:DAPM: update DPCM runtime when mixer/mux changes Nenghua Cao
2013-12-13 12:10 ` [PATCH] ASOC:DAPM: extend dapm kcontrol to support runtime route update Nenghua Cao
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=20131215135116.GR29580@intel.com \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cxie4@marvell.com \
--cc=lgirdwood@gmail.com \
--cc=nhcao@marvell.com \
--cc=tiwai@suse.de \
--cc=xzhao10@marvell.com \
--cc=yacine.belkadi.1@gmail.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).