All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
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 14:34:58 +0200	[thread overview]
Message-ID: <87bksccv7x.wl-tiwai@suse.de> (raw)
In-Reply-To: <YwN2Pd4Ez08yDFno@sirena.org.uk>

On Mon, 22 Aug 2022 14:27:41 +0200,
Mark Brown wrote:
> 
> On Mon, Aug 22, 2022 at 11:52:42AM +0200, Martin Povišer wrote:
> 
> > 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?

IMO such a conversion could be done in user-space gracefully.
Or is any info missing in debugfs as of now to achieve that?

If any, we may put such a tool in the standard repo (e.g. alsa-tools),
too.


Takashi

  reply	other threads:[~2022-08-22 12:35 UTC|newest]

Thread overview: 18+ 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  9:52 ` Martin Povišer
2022-08-22 12:27 ` Mark Brown
2022-08-22 12:27   ` Mark Brown
2022-08-22 12:34   ` Takashi Iwai [this message]
2022-08-22 12:47     ` Mark Brown
2022-08-22 12:38   ` Martin Povišer
2022-08-22 12:38     ` Martin Povišer
2022-08-22 13:04     ` Mark Brown
2022-08-22 13:04       ` Mark Brown
2022-08-22 13:11       ` Martin Povišer
2022-08-22 13:11         ` Martin Povišer
2022-08-22 16:10         ` Mark Brown
2022-08-22 16:10           ` Mark Brown
2022-08-25 13:11           ` Charles Keepax
2022-08-25 13:11             ` Charles Keepax
2022-08-22 13:06     ` Pierre-Louis Bossart
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=87bksccv7x.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --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 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.