Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/4] drm/i915: drpc debugfs update for gen6
Date: Mon, 12 Dec 2011 19:36:04 -0800	[thread overview]
Message-ID: <4EE6C824.3060206@bwidawsk.net> (raw)
In-Reply-To: <1323746520-5592-5-git-send-email-ben@bwidawsk.net>

On 12/12/2011 07:22 PM, Ben Widawsky wrote:
> Many of the old fields from Ironlake have gone away. Strip all those
> fields, and try to update to fields people care about. RC information
> isn't exactly ideal anymore. All we can guarantee when we read the
> register is that we're not using forcewake, ie. the software isn't
> forcing the hardware to stay awake. The downside is that in doing this
> we may wait a while and that causes an unnaturally idle state on the
> GPU.
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=42578
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>


Nak this because of a merge error.

  reply	other threads:[~2011-12-13  3:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13  3:21 [PATCH 0/4] patches for -next Ben Widawsky
2011-12-13  3:21 ` [PATCH 1/4] drm/i915: relative_constants_mode race fix Ben Widawsky
2011-12-13  3:21 ` [PATCH 2/4] drm/i915: Force sync command ordering (Gen6+) Ben Widawsky
2011-12-13  3:21 ` [PATCH 3/4] drm/i915: Update GEN6_RP_CONTROL definitions Ben Widawsky
2011-12-13 19:38   ` Jesse Barnes
2011-12-14 19:13   ` Eugeni Dodonov
2011-12-13  3:22 ` [PATCH 4/4] drm/i915: drpc debugfs update for gen6 Ben Widawsky
2011-12-13  3:36   ` Ben Widawsky [this message]
2011-12-13 19:37   ` Jesse Barnes
2011-12-14 19:13     ` Eugeni Dodonov
2011-12-13  3:34 ` [PATCH 4/4 v2] " Ben Widawsky

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=4EE6C824.3060206@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --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