From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org, rodrigo.vivi@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
Date: Wed, 12 Oct 2022 08:19:23 -0700 [thread overview]
Message-ID: <87tu4983yc.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <6fb51e71-bc5c-16d1-ad13-33017035be83@intel.com>
On Wed, 12 Oct 2022 02:48:30 -0700, Matthew Auld wrote:
>
> So with this change all the runtime pm stuff is disabled on dgfx? i.e
> intel_runtime_pm_get() always returns zero or so?
I guess it should always return non-zero (or the wakeref) since the device
is always on...
next prev parent reply other threads:[~2022-10-12 15:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 8:34 [Intel-gfx] [PATCH] drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' Anshuman Gupta
2022-10-12 9:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-10-12 9:21 ` [Intel-gfx] [PATCH] " Andi Shyti
2022-10-12 14:56 ` Rodrigo Vivi
2022-10-12 9:48 ` Matthew Auld
2022-10-12 14:57 ` Rodrigo Vivi
2022-10-12 15:13 ` Matthew Auld
2022-10-12 15:19 ` Dixit, Ashutosh [this message]
2022-10-13 15:18 ` Gupta, Anshuman
2022-10-14 4:31 ` Gupta, Anshuman
2022-10-12 10:26 ` Joonas Lahtinen
2022-10-12 15:00 ` Rodrigo Vivi
2022-10-14 4:13 ` Gupta, Anshuman
2022-10-12 11:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-10-14 11:32 ` [Intel-gfx] [PATCH v2] drm/i915/dgfx: Keep PCI autosuspend control 'on' by default on all dGPU Anshuman Gupta
2022-10-17 6:02 ` Gupta, Anshuman
2022-10-14 12:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' (rev2) Patchwork
2022-10-14 13:30 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-10-18 13:20 ` Gupta, Anshuman
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=87tu4983yc.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--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