From: Keith Packard <keithp@keithp.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: add multi-threaded forcewake support
Date: Fri, 18 Nov 2011 15:27:14 -0800 [thread overview]
Message-ID: <86lirdko4t.fsf@sumi.keithp.com> (raw)
In-Reply-To: <20111118144839.21458831@jbarnes-desktop>
[-- Attachment #1.1: Type: text/plain, Size: 620 bytes --]
On Fri, 18 Nov 2011 14:48:39 -0800, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> So the ECOBUS reg *is* in the GT power well. Which means in order to
> read it we have to disable RC6 altogether, forcibly, using the 0xa090
> reg, set up force wake, then re-enable RC6.
Not surprising the ECOBUS is in the well; we really only need to read it
when rc6 is getting set up, so it'll be disabled at that point.
But, unless I'm confused, ECOBUS doesn't have any useful information in
it anyways:
# intel_reg_read 0xa090
0xA090 : 0x0
# intel_reg_read 0xa080
0xA080 : 0x0
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2011-11-18 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-18 19:36 [PATCH] drm/i915: add multi-threaded forcewake support Jesse Barnes
2011-11-18 22:01 ` Keith Packard
2011-11-18 22:12 ` Jesse Barnes
2011-11-18 22:35 ` Keith Packard
2011-11-18 22:48 ` Jesse Barnes
2011-11-18 23:27 ` Keith Packard [this message]
2011-11-18 23:34 ` Ben Widawsky
2011-11-19 5:33 ` Keith Packard
2011-11-21 15:47 ` Robert Hooker
[not found] <B32E3D5F1713054290B4FF257B89C51A2E8F496B66@shsmsx502.ccr.corp.intel.com>
2011-11-21 6:55 ` Fang, XunX
2011-12-05 22:42 ` Jesse Barnes
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=86lirdko4t.fsf@sumi.keithp.com \
--to=keithp@keithp.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.