From: Imre Deak <imre.deak@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: don't enable autosuspend on platforms without RPM support
Date: Thu, 17 Dec 2015 19:24:20 +0200 [thread overview]
Message-ID: <1450373060.11561.8.camel@intel.com> (raw)
In-Reply-To: <20151217171929.GK22950@nuc-i3427.alporthouse.com>
On to, 2015-12-17 at 17:19 +0000, Chris Wilson wrote:
> On Thu, Dec 17, 2015 at 07:04:33PM +0200, Imre Deak wrote:
> > Since
> >
> > commit 357597e51dd1aa3cf764d322abf89217e3dcd7bb
> > Author: Imre Deak <imre.deak@intel.com>
> > Date: Tue Nov 10 06:12:22 2015 +0200
> >
> > drm/i915: remove HAS_RUNTIME_PM check from RPM get/put/assert
> > helpers
> >
> > this file is writeable also on platforms without RPM support, but
>
> Which file?
sysfs power/autosuspend_delay_ms is only writeable by userspace if we
call pm_runtime_use_autosuspend().
>
> > userspace (at least IGT) depends on this file being unchangable to
> > determine whether the device supports autosuspend. So restore the
> > old
> > behavior.
> >
> > This gets rid of igt/pm_rpm failures on old platforms without RPM
> > support, where the test should be skipped.
> >
> > Testcase: igt/pm_rpm/basic-rte
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_runtime_pm.c | 13 ++++++++-----
> > 1 file changed, 8 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c
> > b/drivers/gpu/drm/i915/intel_runtime_pm.c
> > index a0b9eaf..ddbdbff 100644
> > --- a/drivers/gpu/drm/i915/intel_runtime_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_runtime_pm.c
> > @@ -2309,18 +2309,21 @@ void intel_runtime_pm_enable(struct
> > drm_i915_private *dev_priv)
> > struct drm_device *dev = dev_priv->dev;
> > struct device *device = &dev->pdev->dev;
> >
> > + pm_runtime_set_autosuspend_delay(device, 10000); /* 10s */
> > + pm_runtime_mark_last_busy(device);
> > +
> > /*
> > * Take a permanent reference to disable the RPM
> > functionality and drop
> > * it only when unloading the driver. Use the low level
> > get/put helpers,
> > * so the driver's own RPM reference tracking asserts also
> > work on
> > * platforms without RPM support.
> > */
> > - if (!HAS_RUNTIME_PM(dev))
> > + if (!HAS_RUNTIME_PM(dev)) {
> > + pm_runtime_dont_use_autosuspend(device);
> > pm_runtime_get_sync(device);
> > -
> > - pm_runtime_set_autosuspend_delay(device, 10000); /* 10s */
> > - pm_runtime_mark_last_busy(device);
> > - pm_runtime_use_autosuspend(device);
> > + } else {
> > + pm_runtime_use_autosuspend(device);
> > + }
>
> This seems to make sense to me.
> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-17 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 17:04 [PATCH] drm/i915: don't enable autosuspend on platforms without RPM support Imre Deak
2015-12-17 17:19 ` Chris Wilson
2015-12-17 17:24 ` Imre Deak [this message]
2015-12-17 17:49 ` ✗ warning: Fi.CI.BAT Patchwork
2015-12-18 10:32 ` [PATCH] drm/i915: don't enable autosuspend on platforms without RPM support David Weinehall
2015-12-18 13:58 ` 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=1450373060.11561.8.camel@intel.com \
--to=imre.deak@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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