All of lore.kernel.org
 help / color / mirror / Atom feed
From: b_lkasam@codeaurora.org
To: Mark Brown <broonie@kernel.org>
Cc: Laxminath Kasam <lkasam@codeaurora.org>,
	alsa-devel@alsa-project.org, b_lkasam@codeaurora.org,
	tiwai@suse.com
Subject: Re: [PATCH V1] Add debug print in soc-dapm
Date: Fri, 05 Mar 2021 20:07:19 +0530	[thread overview]
Message-ID: <3511da77c7cc3fa03837dbf9cb03b1c6@codeaurora.org> (raw)
In-Reply-To: <20210305095943.GA4552@sirena.org.uk>

On 2021-03-05 15:29, Mark Brown wrote:
> On Fri, Mar 05, 2021 at 12:24:02PM +0530, Laxminath Kasam wrote:
>> Add debug print useful for issue analysis in soc-dapm.
>> This print for dapm widgets useful for debugging to find
>> widgets powering up and down.
> 
> There's already fairly extensive tracepoints for DAPM - this seems to
> correspond to snd_soc_dapm_widget_power, though it's at the application
> time rather than the queue time so we could add another tracepoint for
> 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.

--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, 
Inc.,
is a member of Code Aurora Forum, a Linux Foundation Collaborative 
Project.


  reply	other threads:[~2021-03-05 14:38 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 [this message]
2021-03-05 16:15     ` 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=3511da77c7cc3fa03837dbf9cb03b1c6@codeaurora.org \
    --to=b_lkasam@codeaurora.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.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 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.