From: anish kumar <yesanishhere@gmail.com>
To: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-sound@vger.kernel.org, anish kumar <yesanishhere@gmail.com>
Subject: [PATCH] ASoC: doc: dapm: Add location information for dapm-graph tool
Date: Thu, 21 Nov 2024 15:29:58 -0800 [thread overview]
Message-ID: <20241121232958.46179-1-yesanishhere@gmail.com> (raw)
To help developers debug DAPM issues and visualize widget connectivity,
the dapm-graph tool provides a graphical representation of how widgets
and routes are connected. This commit adds the location information for
the tool to the documentation, making it easier for users to find and
use it for troubleshooting DAPM-related problems.
Signed-off-by: anish kumar <yesanishhere@gmail.com>
---
This patch was generated as a result of recent problem I was
debugging with dapm widgets, where I was looking for a way
to visualize as was shown in the documentation, I had to
do a lot of google searches to figure out this tool. So,
just adding the information here so that future developers
doesn't need to look around.
Documentation/sound/soc/dapm.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/sound/soc/dapm.rst b/Documentation/sound/soc/dapm.rst
index 14c4dc026e6b..73a42d5a9f30 100644
--- a/Documentation/sound/soc/dapm.rst
+++ b/Documentation/sound/soc/dapm.rst
@@ -35,6 +35,9 @@ The graph for the STM32MP1-DK1 sound card is shown in picture:
:alt: Example DAPM graph
:align: center
+You can also generate compatible graph for your sound card using
+`tools/sound/dapm-graph` utility.
+
DAPM power domains
==================
--
2.39.5 (Apple Git-154)
next reply other threads:[~2024-11-21 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 23:29 anish kumar [this message]
2024-11-25 14:14 ` [PATCH] ASoC: doc: dapm: Add location information for dapm-graph tool 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=20241121232958.46179-1-yesanishhere@gmail.com \
--to=yesanishhere@gmail.com \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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