From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: "Martin Povišer" <povik+lin@cutebit.org>,
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 17:14:17 +0100 [thread overview]
Message-ID: <YwOrWf3+9c3o5FPO@sirena.org.uk> (raw)
In-Reply-To: <19b60ea9-6bee-1cc9-5384-89231fce3a99@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
On Mon, Aug 22, 2022 at 03:06:03PM +0200, Pierre-Louis Bossart wrote:
> 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
That's a different tool but also interesting - doesn't look like it's
too advanced Python wise so should be fairly easy to update for any
Python 3 incompatibilities.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-08-22 16:14 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
2022-08-22 16:14 ` Mark Brown [this message]
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=YwOrWf3+9c3o5FPO@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=alyssa@rosenzweig.io \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--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