From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Martin Povišer" <povik+lin@cutebit.org>,
"Mark Brown" <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>,
Alyssa Rosenzweig <alyssa@rosenzweig.io>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: dapm: Export new 'graph.dot' file in debugfs
Date: Mon, 22 Aug 2022 15:06:03 +0200 [thread overview]
Message-ID: <19b60ea9-6bee-1cc9-5384-89231fce3a99@linux.intel.com> (raw)
In-Reply-To: <3234D74E-0DFF-4BB5-87ED-6135BAC1F31D@cutebit.org>
>>> Provide a DOT summary of the DAPM graph in a newly added 'graph.dot'
>>> file in debugfs, placed in the card's DAPM directory.
>>
>> There was a tool floating about in the past (last copy I knew about was
>> on Wolfson's git but they took that down) - can we not just continue to
>> do that?
>
> I don’t know the tool or where would I find it. I think it’s neat
> simply having a ‘graph.dot’ at hand, especially since it requires
> little code. (Although sure there’s the danger of it growing.)
The Chrome folks used an 'asoc_dapm_graph' python script since 2014
according to the copyright information. IIRC it was python2 so might
need a bit of work.
https://chromium.googlesource.com/chromiumos/third_party/adhd/+/refs/heads/master/scripts/asoc_dapm_graph
next prev parent reply other threads:[~2022-08-22 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 9:52 [PATCH] ASoC: dapm: Export new 'graph.dot' file in debugfs Martin Povišer
2022-08-22 12:27 ` Mark Brown
2022-08-22 12:34 ` Takashi Iwai
2022-08-22 12:47 ` Mark Brown
2022-08-22 12:38 ` Martin Povišer
2022-08-22 13:04 ` Mark Brown
2022-08-22 13:11 ` Martin Povišer
2022-08-22 16:10 ` Mark Brown
2022-08-25 13:11 ` Charles Keepax
2022-08-22 13:06 ` Pierre-Louis Bossart [this message]
2022-08-22 16:14 ` 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=19b60ea9-6bee-1cc9-5384-89231fce3a99@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=alyssa@rosenzweig.io \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=povik+lin@cutebit.org \
/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