Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: Luca Coelho <luca@coelho.fi>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dgfx: Disable d3cold Correctly
Date: Tue, 7 Jun 2022 10:55:39 +0000	[thread overview]
Message-ID: <e7b0bd1acd484312a72935100b7d8e68@intel.com> (raw)
In-Reply-To: <345f478e6917f39e68cce331250cf1003e73142d.camel@coelho.fi>



> -----Original Message-----
> From: Luca Coelho <luca@coelho.fi>
> Sent: Monday, June 6, 2022 7:53 PM
> To: Gupta, Anshuman <anshuman.gupta@intel.com>; intel-
> gfx@lists.freedesktop.org
> Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>
> Subject: Re: [Intel-gfx] [PATCH] drm/i915/dgfx: Disable d3cold Correctly
> 
> On Mon, 2022-06-06 at 17:56 +0530, Anshuman Gupta wrote:
> > Currently i915 disables d3cold for i915 pci dev.
> > This blocks D3 for i915 gfx pci upstream bridge (VSP).
> > Let's disable d3cold at gfx root port to make sure that
> > i915 gfx VSP can transition to D3 to save some power.
> 
> (nit) It's better to use imperative in the commit message, so "Disable d3cold at
> gfx root port..." would be easier to read.
Thanks for comment, i will fix this,
> 
> Also, from the code, it's clear that you're disabling d3cold in the root now,
> instead of in the pdev itself.  But you don't explain why you moved the
> enabling/disabling to hw_probe and remove_hw from the actual PM calls...
We don't need to disable/enable root port d3cold multiple times in PM suspend handlers, doing this
in probe should be suffice.

Regards,
Anshuman Gupta.
> 
> --
> Cheers,
> Luca.

  reply	other threads:[~2022-06-07 10:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 12:26 [Intel-gfx] [PATCH] drm/i915/dgfx: Disable d3cold Correctly Anshuman Gupta
2022-06-06 13:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-06-06 14:22 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-06-06 14:22 ` [Intel-gfx] [PATCH] " Luca Coelho
2022-06-07 10:55   ` Gupta, Anshuman [this message]
2022-06-13 10:26 ` Nilawar, Badal
2022-06-16 12:22 ` [Intel-gfx] [PATCH v2] drm/i915/dgfx: Disable d3cold at gfx root port Anshuman Gupta
2022-06-16 17:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dgfx: Disable d3cold Correctly (rev2) Patchwork
2022-06-17  0:16 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-06-27 11:59   ` Anshuman Gupta

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=e7b0bd1acd484312a72935100b7d8e68@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luca@coelho.fi \
    --cc=rodrigo.vivi@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