From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Tangudu, Tilak" <tilak.tangudu@intel.com>,
"Deak, Imre" <imre.deak@intel.com>
Subject: Re: [Intel-gfx] [PATCH 2/3] drm/i915: Disallow D3Cold.
Date: Mon, 13 Sep 2021 10:52:51 +0000 [thread overview]
Message-ID: <05c65f7e1cf04fdea37d2914beb0fe7c@intel.com> (raw)
In-Reply-To: <20210910174447.289750-2-rodrigo.vivi@intel.com>
> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Rodrigo
> Vivi
> Sent: Friday, September 10, 2021 11:15 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>; Tangudu, Tilak
> <tilak.tangudu@intel.com>; Deak, Imre <imre.deak@intel.com>
> Subject: [Intel-gfx] [PATCH 2/3] drm/i915: Disallow D3Cold.
>
> During runtime or s2idle suspend and resume cases on discrete cards, if D3Cold
> is really achieved, we will blow everything up and freeze the machine because
> we are not yet handling the pci states properly.
>
> On Integrated it simply doesn't matter because D3hot is the maximum that we
> will get anyway, unless the system is on S3/S4 and our power is cut.
>
> Let's put this hammer for now everywhere. So we can work to enable the auto-
> suspend by default without blowing up the world.
>
> Then, this should be removed when we finally fix the D3Cold flow.
>
> Cc: Tilak Tangudu <tilak.tangudu@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Acked-by: Imre Deak <imre.deak@intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
> index a40b5d806321..086a9a475ce8 100644
> --- a/drivers/gpu/drm/i915/i915_drv.c
> +++ b/drivers/gpu/drm/i915/i915_drv.c
> @@ -301,6 +301,7 @@ static void sanitize_gpu(struct drm_i915_private *i915)
> */
> static int i915_driver_early_probe(struct drm_i915_private *dev_priv) {
> + struct pci_dev *pdev = to_pci_dev(dev_priv->drm.dev);
> int ret = 0;
>
> if (i915_inject_probe_failure(dev_priv))
> @@ -331,6 +332,13 @@ static int i915_driver_early_probe(struct
> drm_i915_private *dev_priv)
> if (ret < 0)
> return ret;
>
> + /*
> + * FIXME: Temporary hammer to avoid freezing the machine on our
> DGFX
> + * This should be totally removed when we handle the pci states
> properly
> + * on runtime PM and on s2idle cases.
> + */
> + pci_d3cold_disable(pdev);
This still doesn't protect, if user space enables d3cold via sys-fs.
d3cold_allowed_store() may call pci_d3cold_enable()
Is it possible to disable it via PCI PM Caps at early probe?
Otherwise it should done in respective suspend callback to make sure
d3cold is disabled.
Thanks,
Anshuman Gupta.
> +
> ret = vlv_suspend_init(dev_priv);
> if (ret < 0)
> goto err_workqueues;
> --
> 2.31.1
next prev parent reply other threads:[~2021-09-13 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-10 17:44 [Intel-gfx] [PATCH 1/3] drm/i915/runtime_pm: Consolidate runtime_pm functions Rodrigo Vivi
2021-09-10 17:44 ` [Intel-gfx] [PATCH 2/3] drm/i915: Disallow D3Cold Rodrigo Vivi
2021-09-13 10:52 ` Gupta, Anshuman [this message]
2021-09-13 18:48 ` Vivi, Rodrigo
2021-09-10 17:44 ` [Intel-gfx] [PATCH 3/3] drm/i915: Enable runtime pm autosuspend by default Rodrigo Vivi
2021-09-13 10:57 ` Gupta, Anshuman
2021-09-13 18:49 ` Vivi, Rodrigo
2021-09-10 18:10 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm/i915/runtime_pm: Consolidate runtime_pm functions Patchwork
2021-09-10 18:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-09-10 19:56 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-09-10 22:06 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/3] drm/i915/runtime_pm: Consolidate runtime_pm functions (rev2) Patchwork
2021-09-10 22:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-09-11 0:25 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=05c65f7e1cf04fdea37d2914beb0fe7c@intel.com \
--to=anshuman.gupta@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=tilak.tangudu@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