From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: "Poosa, Karthik" <karthik.poosa@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [1/3] drm/xe: Toggle the D3Cold enable flag at runtime resume
Date: Fri, 16 Oct 2026 11:35:54 -0700 [thread overview]
Message-ID: <7f92dbae-5b66-4fe0-9dcc-6cd2e2d5a4f0@intel.com> (raw)
In-Reply-To: <553c4753-6c38-471b-8e3a-c6b8c4407e29@intel.com>
On 10/16/2026 11:23 AM, Poosa, Karthik wrote:
>
> On 15-10-2026 22:24, Vinay Belgaumkar wrote:
>> We enable this flag during runtime suspend,
> i think there should be Fixes tag for this.
>
> Fixes: f026520367be ("drm/xe: Only set PCI d3cold_allowed when we are
> really allowing.")
ok.
>
>> need to set it back to
>> false early during resume to prevent any race with pci driver.
> What is race that seen without this ?
While D0 is being programmed in xe_pci_runtime_resume(), pci driver's
internal auto suspend timer could expire and, since this d3cold flag is
still true, pci driver could try to put vsp into D3. This is probably
why we toggle this flag as the very first thing in the S3 resume
function xe_pci_resume().
Thanks,
Vinay.
>>
>> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> ---
>> drivers/gpu/drm/xe/xe_pci.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
>> index 57c6f778ca24..2269e51868c1 100644
>> --- a/drivers/gpu/drm/xe/xe_pci.c
>> +++ b/drivers/gpu/drm/xe/xe_pci.c
>> @@ -1450,6 +1450,9 @@ static int xe_pci_runtime_resume(struct device
>> *dev)
>> struct xe_device *xe = pdev_to_xe_device(pdev);
>> int err;
>> + if (xe->d3cold.allowed)
>> + d3cold_toggle(pdev, D3COLD_DISABLE);
>> +
>> err = pci_set_power_state(pdev, PCI_D0);
>> if (err)
>> return err;
next prev parent reply other threads:[~2026-10-16 18:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 16:54 [PATCH 0/3] drm/xe: Some d3cold related fixes Vinay Belgaumkar
2026-10-15 16:54 ` [PATCH 1/3] drm/xe: Toggle the D3Cold enable flag at runtime resume Vinay Belgaumkar
2026-10-16 18:23 ` [1/3] " Poosa, Karthik
2026-10-16 18:35 ` Belgaumkar, Vinay [this message]
2026-10-15 16:54 ` [PATCH 2/3] drm/xe: Access MMIO after pcode init Vinay Belgaumkar
2026-10-15 23:43 ` sashiko-bot
2026-10-15 23:52 ` Belgaumkar, Vinay
2026-10-16 18:02 ` [2/3] " Poosa, Karthik
2026-10-16 18:05 ` Belgaumkar, Vinay
2026-10-15 16:54 ` [PATCH 3/3] drm/xe: Memset g2g buffer on resume Vinay Belgaumkar
2026-10-16 18:49 ` Matthew Brost
2026-10-16 18:56 ` Matthew Brost
2026-10-16 20:43 ` Belgaumkar, Vinay
2026-10-16 0:03 ` ✓ CI.KUnit: success for drm/xe: Some d3cold related fixes Patchwork
2026-10-16 0:41 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-16 11:38 ` ✓ Xe.CI.FULL: " 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=7f92dbae-5b66-4fe0-9dcc-6cd2e2d5a4f0@intel.com \
--to=vinay.belgaumkar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@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