[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YwOqgSrs6YC6yPm6@sirena.org.uk>
Date: Mon, 22 Aug 2022 17:10:41 +0100
From: Mark Brown <broonie@...nel.org>
To: Martin Povišer <povik+lin@...ebit.org>
Cc: Liam Girdwood <lgirdwood@...il.com>,
Alyssa Rosenzweig <alyssa@...enzweig.io>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
Charles Keepax <ckeepax@...nsource.cirrus.com>,
Richard Fitzgerald <rf@...nsource.cirrus.com>
Subject: Re: [PATCH] ASoC: dapm: Export new 'graph.dot' file in debugfs
On Mon, Aug 22, 2022 at 03:11:48PM +0200, Martin Povišer wrote:
> > On 22. 8. 2022, at 15:04, Mark Brown <broonie@...nel.org> wrote:
> > On Mon, Aug 22, 2022 at 02:38:09PM +0200, Martin Povišer wrote:
> >> simply having a ‘graph.dot’ at hand, especially since it requires
> >> little code. (Although sure there’s the danger of it growing.)
> > I'm also worried about people going in and wanting other more tool
> > specific formats adding, if we didn't have anything at all it'd be one
> > thing but we do have something.
> Sure, although I would argue DOT is by a large margin the standard
> format to represent graphs in.
Well, the debugfs stuff there is more a general tool for introspecting
the current DAPM state than it is indended to draw a pretty picture.
When I wrote it the scale of the devices I was working with was such
that I'm not usre a full graph would've been terribly useful, and
there's even larger devices since then (though also a lot of systems
like yours which do use very much smaller devices).
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists