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>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
David Weinehall <david.weinehall@linux.intel.com>,
"Tangudu, Tilak" <tilak.tangudu@intel.com>,
"Deak, Imre" <imre.deak@intel.com>
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/i915: Enable runtime pm autosuspend by default
Date: Fri, 27 Aug 2021 13:08:33 +0000 [thread overview]
Message-ID: <6f9b48c62f874181bd01848106144f67@intel.com> (raw)
In-Reply-To: <20210825152233.2151037-3-rodrigo.vivi@intel.com>
> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Rodrigo
> Vivi
> Sent: Wednesday, August 25, 2021 8:53 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>; Daniel Vetter
> <daniel.vetter@ffwll.ch>; David Weinehall <david.weinehall@linux.intel.com>;
> Tangudu, Tilak <tilak.tangudu@intel.com>; Deak, Imre <imre.deak@intel.com>
> Subject: [Intel-gfx] [PATCH 3/4] drm/i915: Enable runtime pm autosuspend by
> default
>
> Let's enable runtime pm autosuspend by default everywhere.
>
> But at this time let's not touch the autosuspend_delay time, what caused some
> regression on our previous attempt.
>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: David Weinehall <david.weinehall@linux.intel.com>
> Cc: Tilak Tangudu <tilak.tangudu@intel.com>
> Cc: Imre Deak <imre.deak@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
> drivers/gpu/drm/i915/intel_runtime_pm.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c
> b/drivers/gpu/drm/i915/intel_runtime_pm.c
> index f28b5bab61b4..8f052bd4f58c 100644
> --- a/drivers/gpu/drm/i915/intel_runtime_pm.c
> +++ b/drivers/gpu/drm/i915/intel_runtime_pm.c
> @@ -605,6 +605,8 @@ void intel_runtime_pm_enable(struct intel_runtime_pm
> *rpm)
> pm_runtime_use_autosuspend(kdev);
> }
>
> + pm_runtime_allow(kdev);
Looks good to me.
Reviewed-by: Anshuman Gupta <anshuman.gupta@intel.com>
> +
> /*
> * The core calls the driver load handler with an RPM reference held.
> * We drop that here and will reacquire it during unloading in
> --
> 2.31.1
next prev parent reply other threads:[~2021-08-27 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 15:22 [Intel-gfx] [PATCH 1/4] drm/i915/runtime_pm: Consolidate runtime_pm functions Rodrigo Vivi
2021-08-25 15:22 ` [Intel-gfx] [PATCH 2/4] drm/i915: Disallow D3Cold Rodrigo Vivi
2021-08-27 16:58 ` Imre Deak
2021-08-25 15:22 ` [Intel-gfx] [PATCH 3/4] drm/i915: Enable runtime pm autosuspend by default Rodrigo Vivi
2021-08-27 13:08 ` Gupta, Anshuman [this message]
2021-08-25 15:22 ` [Intel-gfx] [PATCH 4/4] drm/i915/runtime_pm: Reduce autosuspend delay to 1s Rodrigo Vivi
2021-08-27 10:54 ` Gupta, Anshuman
2021-08-25 20:41 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915/runtime_pm: Consolidate runtime_pm functions Patchwork
2021-08-25 21:09 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-08-27 16:31 ` [Intel-gfx] [PATCH 1/4] " Imre Deak
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=6f9b48c62f874181bd01848106144f67@intel.com \
--to=anshuman.gupta@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=david.weinehall@linux.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