From: Mark Brown <broonie@kernel.org>
To: b_lkasam@codeaurora.org
Cc: Laxminath Kasam <lkasam@codeaurora.org>,
alsa-devel@alsa-project.org, tiwai@suse.com
Subject: Re: [PATCH V1] Add debug print in soc-dapm
Date: Fri, 5 Mar 2021 16:15:09 +0000 [thread overview]
Message-ID: <20210305161509.GB4552@sirena.org.uk> (raw)
In-Reply-To: <3511da77c7cc3fa03837dbf9cb03b1c6@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Fri, Mar 05, 2021 at 08:07:19PM +0530, b_lkasam@codeaurora.org wrote:
> On 2021-03-05 15:29, Mark Brown wrote:
> > this if you like? I can see that the separate tracepoint would be
> > useful, I mostly use the regmap tracepoints for that purpose but not
> > every widget has register I/O. Tracepoints are less noisy for the
> > system as a whole than tracing every DAPM operation in dmesg, that tends
> > to irritate other users if it's left in as standard.
> Thanks Mark for the response. But this is not default err/info print and
> only dynamic debug print which should not result in noise. In case of
> customer OEMs/final product versions where less options of debugging,
> dynamic dmesg logging is preferable provided faster and this print is used
> to identify issues debug fastly sometimes.
This is precisely the use case tracepoints were added for and I know
that they are being succesfully used in the development of major mobile
handsets. They are very low overhead, you can even leave them recording
in production usage without getting in anyone's way, and they're also
simple to flip on and off at runtime.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-05 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 6:54 [PATCH V1] Add debug print in soc-dapm Laxminath Kasam
2021-03-05 9:59 ` Mark Brown
2021-03-05 14:37 ` b_lkasam
2021-03-05 16:15 ` 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=20210305161509.GB4552@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=b_lkasam@codeaurora.org \
--cc=lkasam@codeaurora.org \
--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