From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Help request - ASoC recursion issue
Date: Mon, 23 Jul 2012 15:39:56 +0100 [thread overview]
Message-ID: <20120723143955.GA8071@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <500D5A1F.9000808@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 683 bytes --]
On Mon, Jul 23, 2012 at 03:05:19PM +0100, Lee Jones wrote:
> I was wondering if I may bother you for some help. I've been having
> serious issues with testing the new mop500 sound system you have in
You might want to CC some of the people who wrote that code...
> The problem seems to be that 'dapm_supply_check_power()' then calls
> back into 'dapm_widget_power_check()'. Then round and round we go!
Please describe what the problem you think you're seeing is, you've just
cut'n'pasted the code into your mail without describing any actual
problem in the system...
The tree walk is recursive so the fact that we call the same function
more than once isn't terribly surprising.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-07-23 14:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 14:05 Help request - ASoC recursion issue Lee Jones
2012-07-23 14:39 ` Mark Brown [this message]
2012-07-23 14:50 ` Lee Jones
2012-07-23 14:56 ` Lee Jones
2012-07-23 18:12 ` Will Deacon
2012-07-24 7:26 ` Lee Jones
2012-07-24 22:46 ` 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=20120723143955.GA8071@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.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).