From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH v2] ASoC: dapm - Add API call to query the widgets of valid DAPM paths.
Date: Thu, 21 Jul 2011 20:52:22 +0100 [thread overview]
Message-ID: <4E288376.2040500@ti.com> (raw)
In-Reply-To: <20110720201524.GG26043@opensource.wolfsonmicro.com>
On 20/07/11 21:15, Mark Brown wrote:
> On Wed, Jul 20, 2011 at 12:23:15PM +0100, Liam Girdwood wrote:
>
>> + dev_dbg(widget->dapm->dev," %c : %s -> %s -> %s\n",
>> + path->sink && path->connect ? '*' : ' ',
>> + widget->name, path->name, path->sink->name);
>
> We should fix the debugfs stuff to include unconnected paths too, only
> showing currently active paths was a mistake.
This will show the unconnected paths but not weak paths.
I can update to include a flag for weak though.
Might be worth dialing
> down to vdbg too, we look at DAPM a *lot* during scenario changes and
> on big systems it can obscure what's going on.
Ok, that would make sense. I can think of a few other areas for dev_vdbg too...
>
>> +/**
>> + * snd_soc_dapm_get_connected_widgets - query audio path and it's widgets.
>> + * @dapm: the dapm context.
>> + * @stream_name: stream name.
>> + * @list: list of active widgets for this stream.
>> + * @stream: stream direction.
>> + *
>> + * Queries DAPM graph as to whether an valid audio stream path exists for
>> + * the initial widget specified by name. This takes into account
>
> s/initial widget/stream/
>
>> + /* get stream root widget AIF from stream string and direction */
>> + list_for_each_entry(w, &dapm->card->widgets, list) {
>> +
>> + if (w->id != type)
>> + continue;
>> +
>> + if (strstr(w->sname, stream_name))
>> + goto found;
>> + }
>> + dev_err(dapm->dev, "root widget for %s not found\n", stream_name);
>
> Hrm, this will only check the widgets connected to the first widget it
> sees for an AIF. For streams with multiple widgets connected (eg, left
> and right channel) it's only going to see things on the first widget it
> comes across which probably isn't what we were expecting. Unless we
> change to match the comment and query by widget name in which case we're
> already requiring uniqueness.
Yes, but I cant think of any single channel AIFs atm, unless Wolfson has some ?
Liam
next prev parent reply other threads:[~2011-07-21 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 11:23 [PATCH v2] ASoC: dapm - Add API call to query the widgets of valid DAPM paths Liam Girdwood
2011-07-20 20:15 ` Mark Brown
2011-07-21 19:52 ` Liam Girdwood [this message]
2011-07-22 8:40 ` 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=4E288376.2040500@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.