Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>,
	James Xiong <james.xiong@intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Cc: <jani.saarinen@intel.com>, James Xiong <james.xiong@intel.com>
Subject: Re: [PATCH v2] drm/i915/dmc: fix assert_dmc_loaded WARN during async firmware load
Date: Fri, 8 May 2026 09:33:17 -0300	[thread overview]
Message-ID: <87v7cy6pyq.fsf@intel.com> (raw)
In-Reply-To: <b02ec283a5d2137f48859884805d9c55f216cf58@intel.com>

Jani Nikula <jani.nikula@linux.intel.com> writes:

> On Thu, 07 May 2026, James Xiong <james.xiong@intel.com> wrote:
>> 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.
>
> I wonder if intel_dmc_enable_pipe() should call intel_dmc_wait_fw_load()
> itself?

I also though about that, but, if you need to call
intel_dmc_wait_fw_load() in a regular modeset flow, wouldn't that be a
symptom of a bug?

--
Gustavo Sousa

>
>>
>> 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);
>> +
>
> No matter what, the comment above now appears to refer to this
> intel_dmc_wait_fw_load() call, which makes no sense at all.
>
> BR,
> Jani.
>
>>  	for_each_intel_crtc(display->drm, crtc) {
>>  		struct intel_crtc_state *crtc_state =
>>  			to_intel_crtc_state(crtc->base.state);
>
> -- 
> Jani Nikula, Intel

  reply	other threads:[~2026-05-08 12:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 16:46 [PATCH v2] drm/i915/dmc: fix assert_dmc_loaded WARN during async firmware load James Xiong
2026-05-07 17:58 ` ✓ i915.CI.BAT: success for " Patchwork
2026-05-08  7:32 ` ✓ i915.CI.Full: " Patchwork
2026-05-08 11:27 ` [PATCH v2] " Jani Nikula
2026-05-08 12:33   ` Gustavo Sousa [this message]
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=87v7cy6pyq.fsf@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=james.xiong@intel.com \
    --cc=jani.nikula@linux.intel.com \
    --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