public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Michał Grzelak <michal.grzelak@intel.com>
To: Michał Grzelak <michal.grzelak@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Subject: Re: [PATCH v2 1/2] drm/print: describe 6th & 9th bit of drm.debug
Date: Fri, 22 May 2026 21:55:38 +0200 (CEST)	[thread overview]
Message-ID: <26630a3e-7757-4fa4-1415-7ede60d98305@intel.com> (raw)
In-Reply-To: <20260522135520.1862848-2-michal.grzelak@intel.com>

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

On Fri, 22 May 2026, Michał Grzelak wrote:
> Setting 6th or 9th bit of drm.debug change debug logging. Meanwhile
> `modinfo drm` does not inform about it at all.
>
> Add info to MODULE_PARAM_DESC(debug, ...) about setting 6th and 9th bit
> basing on DECLARE_DYNDBG_CLASSMAP(drm_debug_classes, ...). Match
> description of corresponding bits with enum drm_debug_category. Include
> 9th bit in the example with enabling all possible logging provided at
> comment at include/drm/drm_print.h.
>
> Signed-off-by: Michał Grzelak <michal.grzelak@intel.com>

What should have been added here is R-B: tag provided by Chaitanya,
which currently is very much absent. The omission was not intentional.

BR,
Michał

> ---
> drivers/gpu/drm/drm_print.c | 4 +++-
> include/drm/drm_print.h     | 2 +-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_print.c b/drivers/gpu/drm/drm_print.c
> index ded9461df5f2..86cef1a37678 100644
> --- a/drivers/gpu/drm/drm_print.c
> +++ b/drivers/gpu/drm/drm_print.c
> @@ -50,8 +50,10 @@ MODULE_PARM_DESC(debug, "Enable debug output, where each bit enables a debug cat
> "\t\tBit 3 (0x08)  will enable PRIME messages (prime code)\n"
> "\t\tBit 4 (0x10)  will enable ATOMIC messages (atomic code)\n"
> "\t\tBit 5 (0x20)  will enable VBL messages (vblank code)\n"
> +"\t\tBit 6 (0x40)  will enable STATE messages (atomic state code)\n"
> "\t\tBit 7 (0x80)  will enable LEASE messages (leasing code)\n"
> -"\t\tBit 8 (0x100) will enable DP messages (displayport code)");
> +"\t\tBit 8 (0x100) will enable DP messages (displayport code)\n"
> +"\t\tBit 9 (0x200) will enable DRMRES messages (managed resources code)");
>
> #if !defined(CONFIG_DRM_USE_DYNAMIC_DEBUG)
> module_param_named(debug, __drm_debug, ulong, 0600);
> diff --git a/include/drm/drm_print.h b/include/drm/drm_print.h
> index ab017b05e175..2adc5ac688e1 100644
> --- a/include/drm/drm_print.h
> +++ b/include/drm/drm_print.h
> @@ -87,7 +87,7 @@ extern unsigned long __drm_debug;
>  *  - drm.debug=0x2 will enable DRIVER messages
>  *  - drm.debug=0x3 will enable CORE and DRIVER messages
>  *  - ...
> - *  - drm.debug=0x1ff will enable all messages
> + *  - drm.debug=0x3ff will enable all messages
>  *
>  * An interesting feature is that it's possible to enable verbose logging at
>  * run-time by echoing the debug value in its sysfs node::
> -- 
> 2.45.2
>
>

  reply	other threads:[~2026-05-22 19:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 13:55 [PATCH v2 0/2] fixes to DRM doc & parameter's print Michał Grzelak
2026-05-22 13:55 ` [PATCH v2 1/2] drm/print: describe 6th & 9th bit of drm.debug Michał Grzelak
2026-05-22 19:55   ` Michał Grzelak [this message]
2026-05-25  8:29   ` Claude review: " Claude Code Review Bot
2026-05-22 13:55 ` [PATCH v2 2/2] drm/managed: fix drmm_add_action() kernel-doc Michał Grzelak
2026-05-25  8:29   ` Claude review: " Claude Code Review Bot
2026-05-25  8:29 ` Claude review: fixes to DRM doc & parameter's print Claude Code Review Bot

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=26630a3e-7757-4fa4-1415-7ede60d98305@intel.com \
    --to=michal.grzelak@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@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