All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Dibin Moolakadan Subrahmanian"
	<dibin.moolakadan.subrahmanian@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] drm/i915/display: avoid logging DC3CO transitions
Date: Wed, 11 Nov 2026 08:10:48 +0000	[thread overview]
Message-ID: <sashiko-outbox-208576@kernel.org> (raw)
In-Reply-To: <20261111075105.2166760-5-dibin.moolakadan.subrahmanian@intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/i915/display: per-frame DC3CO entry log left in
  xe3lpd_enable_dc3co()
--

commit 168565af43c727ae42413d9678ac0afa5023d467
Author: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>

drm/i915/display: avoid logging DC3CO transitions

This commit suppresses per-frame DC3CO transition debug messages in
gen9_set_dc_state() and logs DC3CO trigger changes in
intel_display_power_dc3co_update().

> diff --git a/drivers/gpu/drm/i915/display/intel_display_power_well.c b/drivers/gpu/drm/i915/display/intel_display_power_well.c
> index 233465a8306ec..6d07643fc14fa 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_power_well.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_power_well.c
> @@ -862,8 +862,18 @@ void gen9_set_dc_state(struct intel_display *display, u32 state)
>  
>  	val = intel_de_read(display, DC_STATE_EN);
>  	mask = gen9_dc_mask(display);
> -	drm_dbg_kms(display->drm, "Setting DC state from %02x to %02x\n",
> -		    val & mask, state);
> +
> +	/*
> +	 * DC3co is entered and exited once per frame while PSR2 or panel
> +	 * replay is active, so logging both transitions floods the log. The
> +	 * exit additionally happens from intel_display_power_get(DC_OFF) in
> +	 * the atomic commit path, before the flip has been armed, where the
> +	 * printk is a measurable part of the time budget. Skip both.
> +	 */
> +	if ((val & mask) != DC_STATE_EN_UPTO_DC3CO &&
> +	    state != DC_STATE_EN_UPTO_DC3CO)
> +		drm_dbg_kms(display->drm, "Setting DC state from %02x to %02x\n",
> +			    val & mask, state);

[Severity: Low]
Should the drm_dbg_kms() call in xe3lpd_enable_dc3co() also be removed?

xe3lpd_enable_dc3co() is the sole caller passing DC_STATE_EN_UPTO_DC3CO to
gen9_set_dc_state(), and it still logs "Enabling DC3CO" on every frame
when entering DC3CO:

drivers/gpu/drm/i915/display/intel_display_power_well.c:xe3lpd_enable_dc3co() {
	assert_can_enable_dc3co(display);
	drm_dbg_kms(display->drm, "Enabling DC3CO\n");
	intel_dmc_wl_enable(display, DC_STATE_EN_UPTO_DC3CO);
	gen9_set_dc_state(display, DC_STATE_EN_UPTO_DC3CO);
}

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261111075105.2166760-4-dibin.moolakadan.subrahmanian@intel.com?part=1

  reply	other threads:[~2026-11-11  8:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11  7:51 [PATCH v2 0/2] drm/i915: Reduce overhead in DC3CO transitions Dibin Moolakadan Subrahmanian
2026-11-11  7:51 ` [PATCH v2 1/2] drm/i915/display: avoid logging " Dibin Moolakadan Subrahmanian
2026-11-11  8:10   ` sashiko-bot [this message]
2026-11-11  7:51 ` [PATCH v2 2/2] drm/i915/dmc_wl: Avoid blocking on delayed wakelock release Dibin Moolakadan Subrahmanian
2026-11-11  8:02 ` ✓ CI.KUnit: success for drm/i915: Reduce overhead in DC3CO transitions (rev2) Patchwork
2026-11-11  8:36 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-11  8:55 ` ✓ i915.CI.BAT: " Patchwork
2026-11-11 15:02 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-11-11 20:09 ` ✗ i915.CI.Full: " Patchwork
2026-11-12  6:25 ` ✓ i915.CI.Full: success " Patchwork
2026-11-12  6:39 ` Patchwork

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=sashiko-outbox-208576@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dibin.moolakadan.subrahmanian@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.