diff options
| author |   Piotr Stankiewicz <piotrs@opensource.wolfsonmicro.com> | 2016-05-13 17:03:56 +0100 |
|---|---|---|
| committer |   Mark Brown <broonie@kernel.org> | 2016-05-30 16:15:10 +0100 |
| commit | 5fdd022c20264791310b188ec4a080bcb8647d23 (patch) | |
| tree | 0733590c59a9731fb84571e78bd382ad20257003 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | ASoC: dapm: support user-defined stop condition in dai_get_connected_widgets (diff) | |
| download | linux-dev-5fdd022c20264791310b188ec4a080bcb8647d23.tar.xz linux-dev-5fdd022c20264791310b188ec4a080bcb8647d23.zip | |
ASoC: dpcm: play nice with CODEC<->CODEC links
Currently in situations where a normal CODEC to CODEC link follows a
DPCM DAI, an error in the following form will be logged:
ASoC: can't get [playback|capture] BE for <widget name>
ASoC: no BE found for <widget name>
This happens because all widgets in a path containing a DPCM DAI will
be passed to dpcm_add_paths, which will try to interpret the CODEC<->CODEC
as if it were a DPCM DAI, in turn causing the error.
This patch aims to resolve the described issue by stopping the DPCM graph
walk, initiated from dpcm_path_get, at the first widget associated with
a DPCM BE.
Signed-off-by: Piotr Stankiewicz <piotrs@opensource.wolfsonmicro.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions