alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: Piotr Stankiewicz <piotrs@opensource.wolfsonmicro.com>,
	alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com,
	lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: dpcm: prevent error for paths including static links
Date: Wed, 30 Mar 2016 09:36:50 -0700	[thread overview]
Message-ID: <20160330163650.GG2350@sirena.org.uk> (raw)
In-Reply-To: <20160330085812.GE31814@localhost.localdomain>


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

On Wed, Mar 30, 2016 at 09:58:12AM +0100, Charles Keepax wrote:
> On Tue, Mar 29, 2016 at 02:22:24PM -0700, Mark Brown wrote:

> > Is this not just a normal CODEC connected to a back end on a DPCM
> > system?  What are a "dynamic DAI" and "static DAI"?  Your changelog is
> > very unclear, I really can't tell from your changelog what this is
> > aiming to do or how it proposes to do it.

> The issue is basically if you have a path with a DPCM DAI at the
> front, but then a regular CODEC to CODEC DAI link later in the
> path. Say for example a CODEC attached to a CPU that uses DPCM
> but then the path goes through a CODEC to CODEC link to a speaker
> AMP after the CODEC.

Doesn't this mean that the appropriate fix is to terminate the DPCM
routing at the first back end DAI so we're not trying to DPCM outside
the SoC?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

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



  reply	other threads:[~2016-03-30 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 15:34 [PATCH] ASoC: dpcm: prevent error for paths including static links Piotr Stankiewicz
2016-03-29 21:22 ` Mark Brown
2016-03-30  8:58   ` Charles Keepax
2016-03-30 16:36     ` Mark Brown [this message]
2016-03-30 17:13       ` Charles Keepax
2016-03-30 17:27         ` Mark Brown
2016-03-31  8:17           ` Charles Keepax

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=20160330163650.GG2350@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=lgirdwood@gmail.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=piotrs@opensource.wolfsonmicro.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).