From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
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: Thu, 31 Mar 2016 09:17:33 +0100 [thread overview]
Message-ID: <20160331081733.GG31814@localhost.localdomain> (raw)
In-Reply-To: <20160330172702.GM2350@sirena.org.uk>
On Wed, Mar 30, 2016 at 10:27:02AM -0700, Mark Brown wrote:
> On Wed, Mar 30, 2016 at 06:13:14PM +0100, Charles Keepax wrote:
> > On Wed, Mar 30, 2016 at 09:36:50AM -0700, Mark Brown wrote:
>
> > > 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?
>
> > I think (not 100% certain) you can have multiple backends
> > connected to a single front end, which makes it hard to know when
> > to stop or even if it is assured that all the backends will be
> > before any other spurious DAIs in the widget list.
>
> You can have multiple backends connected but they shouldn't be chained
> together, they should be connected in parallel. We can tell if we're
> walking a node that's a backend, why would we walk the graph beyond
> that?
Ah ok apologies, I misunderstood your suggestion. I
thought you meant aborting the widget list search in
dpcm_add_paths, but you actually mean aborting the graph walk in
snd_soc_dapm_dai_get_connnected_widgets. That looks totally like
it would work, although it needs a bit of thought as I guess the
original intention was for get_connected_widgets to be pretty
generic, but it does only have the single user.
I will get Piotr to have a look at respinning the patch, when he
returns.
Thanks,
Charles
prev parent reply other threads:[~2016-03-31 8:17 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
2016-03-30 17:13 ` Charles Keepax
2016-03-30 17:27 ` Mark Brown
2016-03-31 8:17 ` Charles Keepax [this message]
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=20160331081733.GG31814@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--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).