From: David Weinehall <david.weinehall@linux.intel.com>
To: Deepak S <deepak.s@linux.intel.com>
Cc: daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Disable WaGsvRC0ResidencyMethod for vlv
Date: Thu, 19 Mar 2015 15:38:19 +0200 [thread overview]
Message-ID: <20150319133819.GD10425@boom> (raw)
In-Reply-To: <550AC544.5040207@linux.intel.com>
On Thu, Mar 19, 2015 at 06:17:00PM +0530, Deepak S wrote:
>
>
> On Thursday 19 March 2015 05:14 PM, David Weinehall wrote:
> >On Thu, Mar 19, 2015 at 04:09:44PM +0530, deepak.s@linux.intel.com wrote:
> >>From: Deepak S <deepak.s@linux.intel.com>
> >>
> >>Unfortunately WaGsvRC0ResidencyMethod causing system freeze on some
> >>of the baytrail systems :(. Switching back to legacy mode rps.
> >Is there any way to identify either what systems it's OK to use on,
> >or to identif what Baytrail systems it isn't OK to use on?
> >
> >Just reverting this completely seems overly broad if it's possible to
> >tell the difference between working and non-working systems.
>
> Restricting the changes to few system will be the right way to go.
> How do we get details of now working system?
That depends. Who reported the non-working Baytrail-systems?
And just as importantly, do we have Baytrail systems where this is
confirmed to work?
If we can identify the respective revisions of the systems
we might be able to discern the pattern and continue from there.
Kind regards, David Weinehall
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-03-19 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 10:39 [PATCH] drm/i915: Disable WaGsvRC0ResidencyMethod for vlv deepak.s
2015-03-19 11:17 ` Jani Nikula
2015-03-19 11:18 ` Ville Syrjälä
2015-03-19 11:53 ` Deepak S
2015-03-19 11:44 ` David Weinehall
2015-03-19 12:47 ` Deepak S
2015-03-19 13:38 ` David Weinehall [this message]
2015-03-19 16:38 ` Daniel Vetter
2015-04-13 12:06 ` Jani Nikula
2015-04-15 7:56 ` Deepak S
2015-03-19 19:51 ` shuang.he
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=20150319133819.GD10425@boom \
--to=david.weinehall@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=deepak.s@linux.intel.com \
--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