From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: dapm: Fix handling of loops
Date: Fri, 22 Feb 2013 21:41:54 +0000 [thread overview]
Message-ID: <1361569314.2567.13.camel@loki> (raw)
In-Reply-To: <1361555534-6811-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Fri, 2013-02-22 at 17:52 +0000, Mark Brown wrote:
> Currently if a path loops back on itself we correctly skip over it to
> avoid going into an infinite loop but this causes us to ignore the need
> to power up the path as we don't count the loop for the purposes of
> counting inputs and outputs. This means that internal loopbacks within a
> device that have powered devices on them won't be powered up.
>
> Fix this by treating any path that is currently in the process of being
> recursed as having a single input or output so that it is counted for
> the purposes of power decisions.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Acked-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
prev parent reply other threads:[~2013-02-22 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 17:52 [PATCH] ASoC: dapm: Fix handling of loops Mark Brown
2013-02-22 21:41 ` Liam Girdwood [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=1361569314.2567.13.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.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).