From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/icl: do a posting read after irq install
Date: Wed, 23 Jan 2019 10:38:42 -0800 [thread overview]
Message-ID: <352aa47b-eef4-2c35-13b9-b5dbb6fdb552@intel.com> (raw)
In-Reply-To: <87bm47mwjr.fsf@gaia.fi.intel.com>
On 01/23/2019 03:40 AM, Mika Kuoppala wrote:
> Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com> writes:
>
>> On 1/22/2019 6:32 PM, Daniele Ceraolo Spurio wrote:
>>> When reading GEN11_GT_INTR_DWx closely after enabling the interrupts
>>> in gen11_irq_postinstall, the returned value is garbage. This can
>>
>> To clarify, this only happens (or at least I've only seen it) during
>> runtime_resume.
>>
>
> How did you notice?
>
The gen11 guc patches add
WARN_ON_ONCE(gen11_reset_one_iir(dev_priv, 0, GEN11_GUC));
in the resume path and we saw the warning fire off in testing. A bit of
extra logging showed that the whole register was in an invalid state
after interrupts were re-enabled, not just the GuC bit.
pm_rpm@basic-pci-d3-state hits this consistently.
Daniele
>> Daniele
>>
>>> cause other parts of the setup code (e.g. gen11_reset_one_iir) to
>>> think that there are interrupts to be cleared when there are none.
>>>
>>> The garbage value is only seen on the first read done after the enable,
>>> so this looks like a posting issue. Adding a posting read after enabling
>>> the interrupts does indeed fix the problem.
>>>
>>> Note that the posting read has been purposely added outside of
>>> gen11_master_intr_enable since the issue has only been observed when the
>>> full interrupt setup is performed.
>
> Scary enough that maybe it would have been warranted inside it. But
> well we know where to escalate if it shows up elsewhere.
>
> Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>
>>>
>>> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>>> ---
>>> drivers/gpu/drm/i915/i915_irq.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
>>> index 5fd5080c4ccb..7056ae2d1e0e 100644
>>> --- a/drivers/gpu/drm/i915/i915_irq.c
>>> +++ b/drivers/gpu/drm/i915/i915_irq.c
>>> @@ -4089,6 +4089,7 @@ static int gen11_irq_postinstall(struct drm_device *dev)
>>> I915_WRITE(GEN11_DISPLAY_INT_CTL, GEN11_DISPLAY_IRQ_ENABLE);
>>>
>>> gen11_master_intr_enable(dev_priv->regs);
>>> + POSTING_READ(GEN11_GFX_MSTR_IRQ);
>>>
>>> return 0;
>>> }
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-23 18:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 2:32 [PATCH] drm/i915/icl: do a posting read after irq install Daniele Ceraolo Spurio
2019-01-23 3:28 ` Daniele Ceraolo Spurio
2019-01-23 11:40 ` Mika Kuoppala
2019-01-23 18:38 ` Daniele Ceraolo Spurio [this message]
2019-01-23 4:52 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-01-23 6:39 ` ✓ Fi.CI.IGT: " Patchwork
2019-01-23 8:41 ` [PATCH] " Chris Wilson
2019-01-23 11:59 ` Mika Kuoppala
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=352aa47b-eef4-2c35-13b9-b5dbb6fdb552@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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