From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH] drm/xe: Restore pci state upon resume
Date: Thu, 12 Sep 2024 17:20:40 -0400 [thread overview]
Message-ID: <ZuNbKM6-oiJUIR4Y@intel.com> (raw)
In-Reply-To: <5o4xl2avzkdnbecni3vg7fmtiw5lfr2ohuz3o6vdfqzjmkdmia@pd7naq6fa42l>
On Thu, Sep 12, 2024 at 03:11:12PM -0500, Lucas De Marchi wrote:
> On Thu, Sep 12, 2024 at 03:05:30PM GMT, Rodrigo Vivi wrote:
> > The pci state was saved, but not restored. Restore
> > right after the power state transition request like
> > every other driver.
> >
> > Fixes: dd08ebf6c352 ("drm/xe: Introduce a new DRM driver for Intel GPUs")
>
> oh, no
>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > drivers/gpu/drm/xe/xe_pci.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
> > index 5ba4ec229494..6d29ef4b396f 100644
> > --- a/drivers/gpu/drm/xe/xe_pci.c
> > +++ b/drivers/gpu/drm/xe/xe_pci.c
> > @@ -949,6 +949,8 @@ static int xe_pci_resume(struct device *dev)
> > if (err)
> > return err;
> >
> > + pci_restore_state(pdev);
> > +
>
> something bad happened... I was sure this line was here before. Indeed.
> git log -L:xe_pci_resume:drivers/gpu/drm/xe/xe_pci.c to the rescue
>
> See commit f6761c68c0ac ("drm/xe/display: Improve s2idle handling.")
hmmm...
Perhaps
Fixes: f6761c68c0ac ("drm/xe/display: Improve s2idle handling.")
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
then?!
The restoration shouldn't have anything to do with that case.
and it pairs with pci_save_state(pdev) is still there...
It is not in i915, but I have an i915 patch to add the restore
there as well.
Also, I might as well in a follow up bring back the
pci_set_power_state(pdev, PCI_D3hot) to Xe.
This is probably the right way, aligns with all other drivers
and i915. So that shouldn't be the cause of the power drainage
on suspend anyway, or i915 would be also draining it.
>
> Lucas De Marchi
>
> > err = pci_enable_device(pdev);
> > if (err)
> > return err;
> > --
> > 2.46.0
> >
next prev parent reply other threads:[~2024-09-12 21:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 19:05 [PATCH] drm/xe: Restore pci state upon resume Rodrigo Vivi
2024-09-12 19:47 ` Cavitt, Jonathan
2024-09-12 20:05 ` ✓ CI.Patch_applied: success for " Patchwork
2024-09-12 20:05 ` ✓ CI.checkpatch: " Patchwork
2024-09-12 20:07 ` ✓ CI.KUnit: " Patchwork
2024-09-12 20:11 ` [PATCH] " Lucas De Marchi
2024-09-12 21:20 ` Rodrigo Vivi [this message]
2024-09-12 21:40 ` Lucas De Marchi
2024-09-17 21:37 ` Maarten Lankhorst
2024-09-12 20:18 ` ✓ CI.Build: success for " Patchwork
2024-09-12 20:21 ` ✓ CI.Hooks: " Patchwork
2024-09-12 20:22 ` ✓ CI.checksparse: " Patchwork
2024-09-12 20:37 ` ✓ CI.BAT: " Patchwork
2024-09-13 11:01 ` [PATCH] " Ville Syrjälä
2024-09-13 15:43 ` Rodrigo Vivi
2024-09-13 15:50 ` Gupta, Anshuman
2024-09-13 16:54 ` Ville Syrjälä
2024-09-17 18:49 ` Rodrigo Vivi
2024-09-17 21:09 ` Ville Syrjälä
2024-09-19 22:10 ` Rodrigo Vivi
2024-09-20 10:19 ` Ville Syrjälä
2024-09-13 14:10 ` ✗ CI.FULL: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 21:45 [PATCH] " Rodrigo Vivi
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=ZuNbKM6-oiJUIR4Y@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@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