From: James Xiong <james.xiong@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: gustavo.sousa@intel.com, jani.saarinen@intel.com,
James Xiong <james.xiong@intel.com>
Subject: [PATCH v2] drm/i915/dmc: fix assert_dmc_loaded WARN during async firmware load
Date: Thu, 7 May 2026 09:46:05 -0700 [thread overview]
Message-ID: <20260507164605.608368-1-james.xiong@intel.com> (raw)
During driver probe, DMC firmware is loaded asynchronously via a
workqueue. There is a race between parse_dmc_fw() setting the payload
pointer (making has_dmc_id_fw() return true) and intel_dmc_load_program()
writing the firmware to hardware registers. If the probe thread calls
intel_dmc_enable_pipe() -> assert_dmc_loaded() in this window via
intel_modeset_setup_hw_state(), it sees parsed payload but stale HW
registers, triggering a ~20% intermittent WARNING on ADL-N warm boot.
v2: Fix by calling intel_dmc_wait_fw_load() in
intel_modeset_setup_hw_state() before iterating the CRTCs (Gustavo
Sousa).
Signed-off-by: James Xiong <james.xiong@intel.com>
---
drivers/gpu/drm/i915/display/intel_modeset_setup.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/display/intel_modeset_setup.c b/drivers/gpu/drm/i915/display/intel_modeset_setup.c
index e88082c8caac..277e56848470 100644
--- a/drivers/gpu/drm/i915/display/intel_modeset_setup.c
+++ b/drivers/gpu/drm/i915/display/intel_modeset_setup.c
@@ -961,6 +961,8 @@ void intel_modeset_setup_hw_state(struct intel_display *display,
* intel_sanitize_plane_mapping() may need to do vblank
* waits, so we need vblank interrupts restored beforehand.
*/
+ intel_dmc_wait_fw_load(display);
+
for_each_intel_crtc(display->drm, crtc) {
struct intel_crtc_state *crtc_state =
to_intel_crtc_state(crtc->base.state);
--
2.34.1
next reply other threads:[~2026-05-07 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 16:46 James Xiong [this message]
2026-05-07 17:21 ` ✓ CI.KUnit: success for drm/i915/dmc: fix assert_dmc_loaded WARN during async firmware load Patchwork
2026-05-07 19:04 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-08 5:12 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-08 11:27 ` [PATCH v2] " Jani Nikula
2026-05-08 12:33 ` Gustavo Sousa
2026-05-08 12:48 ` Jani Nikula
2026-05-08 13:35 ` Gustavo Sousa
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=20260507164605.608368-1-james.xiong@intel.com \
--to=james.xiong@intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox