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, 18 Nov 2015 19:18:43 +0530 [thread overview]
Message-ID: <20151118134843.GU25173@localhost> (raw)
In-Reply-To: <20151118131757.GI31303@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1366 bytes --]
On Wed, Nov 18, 2015 at 01:17:57PM +0000, Mark Brown wrote:
> On Mon, Nov 09, 2015 at 11:19:59PM +0530, Vinod Koul wrote:
> > From: Jeeja KP <jeeja.kp@intel.com>
> >
> > soc_link_dai_widgets() creates codec-codec loopback link which
> > allows DPCM to trigger these links and program the parameters for
> > these links These links are:
> >
> > Codec1 Tx (Pb) ----------> Rx Codec2 (Cap)
> > Codec2 Tx (Cap) <---------- Tx Codec1 (Pb)
> >
> > But as we try to model a CPU based loops for non host links like
> > modem to codec loop, the above mapping gets wrong as:
> >
> > CPU Tx (Pb) -----------> Codec Tx (Pb)
> > CPU Rx (Cap) <----------- Codec Rx (Cap)
> >
> > So we add a new flag to handle above scenario and link widgets as
> > depecited above
>
> So, what I was really thinking of with the renaming was a bigger rename
> that updates the names in snd_soc_dai_driver and everything that comes
> from that. That's a much bigger thing though, let me think about it a
> bit more.
ah, yes that kind of change does make sense, but as you observed that will
be a larger rework. And I think I am up for it in parallel to my SKL work :)
But that will take a bit of time and I would like update these in bits
rather than one shot
Let me know what you think and how you would like to approach this
Thanks
--
~Vinod
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-11-18 13:45 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 [this message]
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
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=20151118134843.GU25173@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).