From: Quentin Schulz <quentin.schulz@cherry.de>
To: Quentin Schulz <foss+uboot@0leil.net>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Alexander Dahl <ada@thorsis.com>
Subject: Re: [PATCH] dm: core: downgrade some dm_warn messages to log_debug()
Date: Wed, 16 Oct 2024 13:31:30 +0200 [thread overview]
Message-ID: <0f0124fb-b324-4110-9c42-433233fad83d@cherry.de> (raw)
In-Reply-To: <20241015-dm-debug-less-verbose-v1-1-366e8f00b556@cherry.de>
On 10/15/24 4:32 PM, Quentin Schulz wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> People complained that enabling (SPL_)DM_WARN was now totally unusable
> due to the amount of messages printed on the console.
>
> Let's downgrade the log level of some messages that are clearly not on
> the error path.
>
> Note that there's one pr_debug in there, because it is followed by
> pr_cont so it made sense to reuse the same family of functions.
>
> Reported-by: Alexander Dahl <ada@thorsis.com>
> Fixes: 6afdb1585112 ("dm: core: migrate debug() messages to use dm_warn")
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
> Note that I am not entirely sure about the "not found" and "not large
> enough" changes there.
>
> Another note, %#x isn't handled by tinyprintf so it just prints "x"
> instead of the value.
>
> Finally, I don't know how one can enable LOG_DEBUG level without
> enabling DEBUG which enables assert() so I just tested that by removing
> the #define DEBUG in include/log.h :)
Ah, and I was also wondering if we shouldn't actually use
log(LOGC_DM, LOGL_DEBUG, ...)
instead of log_debug() (which uses LOGL_CATEGORY, set by UCLASSes or
drivers usually as far as I could tell?)
If we do, then maybe having dm_debug() similarly to dm_warn() would make
sense?
Cheers,
Quentin
next prev parent reply other threads:[~2024-10-16 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 14:32 [PATCH] dm: core: downgrade some dm_warn messages to log_debug() Quentin Schulz
2024-10-16 11:31 ` Quentin Schulz [this message]
2024-10-17 14:56 ` Alexander Dahl
2024-10-17 15:09 ` Quentin Schulz
2024-10-27 17:16 ` Simon Glass
2024-10-28 10:04 ` Quentin Schulz
2024-10-29 22:28 ` Tom Rini
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=0f0124fb-b324-4110-9c42-433233fad83d@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=ada@thorsis.com \
--cc=foss+uboot@0leil.net \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 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.