Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	tiwai@suse.com, perex@perex.cz, amade@asmblr.net,
	linux-sound@vger.kernel.org, kuninori.morimoto.gx@renesas.com
Subject: Re: [PATCH v3] ALSA: control: Verify put() result when in debug mode
Date: Fri, 6 Feb 2026 14:08:28 +0000	[thread overview]
Message-ID: <aYX13LsGaMjO8X92@sirena.co.uk> (raw)
In-Reply-To: <87ms1m9htu.wl-tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

On Fri, Feb 06, 2026 at 01:28:45PM +0100, Takashi Iwai wrote:
> Cezary Rojewski wrote:

> > +	if (retcmp == ret)
> > +		pr_info("kctl->put() returned the expected value of '%d'\n", ret);
> > +	else
> > +		pr_warn("expected kctl->put() to return '%d' but got '%d'\n", ret, retcmp);

> So this prints out a message at each access even if it succeeds.
> I believe this would flood too many messages unnecessarily.  Can it be
> better to be with debug level?

> Also, this message doesn't show any relevant information about which
> card, device and which control caused the error, and that makes
> debugging harder.  Put some prefix to identify the problematic
> control.

Might it be worth considering doing this via trace_printk() or possibly
tracepoints?  They're very low overhead and with tracepoints they're
strutured so they're more suitable for very high volume logging.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-02-06 14:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 11:32 [PATCH v3] ALSA: control: Verify put() result when in debug mode Cezary Rojewski
2026-02-06 12:28 ` Takashi Iwai
2026-02-06 14:08   ` Mark Brown [this message]
2026-02-06 14:33     ` Takashi Iwai
2026-02-06 14:44       ` Mark Brown
2026-02-06 17:34         ` Cezary Rojewski
2026-02-06 17:45   ` Cezary Rojewski
2026-02-06 17:57     ` Mark Brown
2026-02-09 14:43   ` Cezary Rojewski
2026-02-09 15:14     ` Jaroslav Kysela
2026-02-09 21:05       ` Cezary Rojewski

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=aYX13LsGaMjO8X92@sirena.co.uk \
    --to=broonie@kernel.org \
    --cc=amade@asmblr.net \
    --cc=cezary.rojewski@intel.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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