From: Lars-Peter Clausen <lars@metafoo.de>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Kp Jeeja <jeeja.kp@intel.com>,
alsa-devel@alsa-project.org, broonie@kernel.org,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>,
lgirdwood@gmail.com
Subject: Re: [PATCH v2 1/2] ASoC: export dapm_kcontrol_set/get_value functions
Date: Thu, 29 May 2014 12:55:07 +0200 [thread overview]
Message-ID: <5387120B.6090100@metafoo.de> (raw)
In-Reply-To: <1401357817-17942-1-git-send-email-vinod.koul@intel.com>
On 05/29/2014 12:03 PM, Vinod Koul wrote:
> The DSPs like Intel ones use the DPCM to represent the DSP toplogy. So when DAPM
> triggers the widget, the DSP needs to know the kcontrol values and pass on to DSP
> firmware, so export these for driver use
>
As I said I feel a bit uneasy about exporting these and I'd rather much
prefer to see this patch in context (i.e. in the same series as its user).
- Lars
next prev parent reply other threads:[~2014-05-29 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 10:03 [PATCH v2 1/2] ASoC: export dapm_kcontrol_set/get_value functions Vinod Koul
2014-05-29 10:03 ` [PATCH v2 2/2] ASoC: dapm: Add a helper to get the platform for DAPM kcontrol Vinod Koul
2014-06-01 19:28 ` Mark Brown
2014-05-29 10:55 ` Lars-Peter Clausen [this message]
2014-05-30 6:09 ` [PATCH v2 1/2] ASoC: export dapm_kcontrol_set/get_value functions Vinod Koul
2014-05-30 7:22 ` Lars-Peter Clausen
2014-05-30 10:29 ` Vinod Koul
2014-05-30 12:50 ` Lars-Peter Clausen
2014-06-01 19:26 ` Mark Brown
2014-06-03 5:44 ` Vinod Koul
2014-06-03 10:11 ` Mark Brown
2014-06-06 5:54 ` Vinod Koul
2014-06-06 9:51 ` 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=5387120B.6090100@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jeeja.kp@intel.com \
--cc=lgirdwood@gmail.com \
--cc=subhransu.s.prusty@intel.com \
--cc=vinod.koul@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