From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: dapm: Add API call to query valid DAPM paths.
Date: Wed, 7 Mar 2012 19:15:48 +0000 [thread overview]
Message-ID: <20120307191547.GX3107@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1331142952-6502-1-git-send-email-lrg@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 1300 bytes --]
On Wed, Mar 07, 2012 at 05:55:52PM +0000, Liam Girdwood wrote:
> +struct snd_soc_dapm_widget_list;
I might be blind but I think the hunk that actually declares the widget
list got dropped from the header... probably in some other part of the
series you haven't pushed out yet?
> + dev_vdbg(widget->dapm->dev," %c : %s -> %s -> %s\n",
> + path->sink && path->connect ? '*' : ' ',
> + widget->name, path->name, path->sink->name);
> +
This and the input user look like good candidates for a tracepoint, it's
probably pretty useful to have them around and more accessible than vdbg
is. It's the sort of information people often look for, and it's real
time unlike the debugfs picture which isn't capturing stuff when DAPM is
looking at it.
> + dapm_reset(card);
This function isn't in mainline, another patch series reordering thing I
expect. It does also look like we need some locking somewhere along the
line here (even if the only thing here is a big scary comment saying the
relevant locks need to be held).
> + dev_dbg(dai->dev, "%s: found %d paths\n",
> + stream ? "capture" : "playback", paths);
Tracepoint again? Much less clear for this one. I do think we should
be dumping the stats we've been collecting for the neighbour walks, very
useful if performance blows up again.
[-- 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-03-07 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 17:55 [PATCH] ASoC: dapm: Add API call to query valid DAPM paths Liam Girdwood
2012-03-07 19:15 ` Mark Brown [this message]
2012-03-08 11:42 ` Liam Girdwood
2012-03-08 12:05 ` 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=20120307191547.GX3107@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.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).