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: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
	alsa-devel@alsa-project.org, Jeeja KP <jeeja.kp@intel.com>
Subject: Re: [PATCH 2/4] ASoC: core: Adds support for cpu loopback dai_link
Date: Wed, 16 Dec 2015 20:18:06 +0530	[thread overview]
Message-ID: <20151216144806.GO1854@localhost> (raw)
In-Reply-To: <20151202103241.GC1929@sirena.org.uk>


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

On Wed, Dec 02, 2015 at 10:32:41AM +0000, Mark Brown wrote:
> On Wed, Dec 02, 2015 at 10:53:30AM +0530, Vinod Koul wrote:
> 
> > But if we do wrt from CPU the situation is different
> 
> >      CPU Tx (Pb)  -----------> Codec Tx (Pb)
> >      CPU Rx (Cap) <----------- Codec Rx (Cap)
> 
> > Since this follows normal playback kind of scenario, we need to link pb-pb
> > and cap-cap
> 
> But neither of these is a CODEC so why would the CODEC flag be set in
> the DAI?  Unless your "Codec" here is genuinely the CODEC rather than
> the CPU DAI connected to the CODEC in which case surely this is just a
> normal DAI link?

Sorry Mark for late reply..

You are right this is like a normal link, and yes that is _exactly_ we need,
but we also need parameters to be specified for this as this is hostless.

The moment I add 'params" core will do different connections which do not
work for us.

I am okay if you have something else in mind which solves our problem :)

Thanks
-- 
~Vinod

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

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



  reply	other threads:[~2015-12-16 14:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 17:49 [PATCH 0/4] ASoC: core: Update for DSP systems Vinod Koul
2015-11-09 17:49 ` [PATCH 1/4] ASoC: core: refactor soc_link_dai_widgets() Vinod Koul
2015-11-18 13:13   ` Applied "ASoC: core: refactor soc_link_dai_widgets()" to the asoc tree Mark Brown
2015-11-09 17:49 ` [PATCH 2/4] ASoC: core: Adds support for cpu loopback dai_link Vinod Koul
2015-11-18 13:17   ` Mark Brown
2015-11-18 13:48     ` Vinod Koul
2015-11-25 16:13       ` Vinod Koul
2015-11-30 16:25       ` Mark Brown
2015-12-01  2:56         ` Vinod Koul
2015-12-01 12:27           ` Mark Brown
2015-12-02  5:23             ` Vinod Koul
2015-12-02 10:32               ` Mark Brown
2015-12-16 14:48                 ` Vinod Koul [this message]
2015-12-30 18:03                   ` Mark Brown
2016-01-04 15:42                     ` Vinod Koul
2015-11-09 17:50 ` [PATCH 3/4] ASoC: core: Pass kcontrol to bytes tlv callbacks Vinod Koul
2015-11-18 13:13   ` Applied "ASoC: core: Pass kcontrol to bytes tlv callbacks" to the asoc tree Mark Brown
2015-11-09 17:50 ` [PATCH 4/4] ASoC: topology: fix info callback for TLV byte control Vinod Koul
2015-11-18 13:13   ` Applied "ASoC: topology: fix info callback for TLV byte control" to the asoc tree 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=20151216144806.GO1854@localhost \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jeeja.kp@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@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).