From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Andrew Lutomirski <luto@mit.edu>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.sf.net
Subject: Re: [resend] i915: high power consumption after suspend/resume
Date: Fri, 6 Nov 2009 13:57:22 -0800 [thread overview]
Message-ID: <20091106135722.5abfdd03@jbarnes-piketon> (raw)
In-Reply-To: <cb0375e10911061225y1bc29807y5abd67e748ef4164@mail.gmail.com>
On Fri, 6 Nov 2009 15:25:26 -0500
Andrew Lutomirski <luto@mit.edu> wrote:
> Here's what the docs say:
>
>
> 2030, 2034: ring buffer head/tail
> 2074: Active head pointer register
> 20AC: Interrupt Status Register (ISR)
> 2218: Reserved
> 2358, 235C: TIMESTAMP
>
> 1xxxx: MCHBAR aperture
>
> 61110: PORT_HOTPLU_EN
> 61114: PORT_HOTPLU_STAT
> 61170: UDI_IF_CTL (UDI InfoFrame Control)
>
> 61260: BLM_HIST_CTL (Image BLM Histogram Control Register)
>
> 620B4: Reserved (for High Definition?)
>
> 71000: PIPEB_DSL (Pipe B Display Scan Line Count)
> 71040: PIPEBFRAMEH: Pipe B Frame Count High
> 71048: Reserved
>
> Any ideas?
Thanks, that helps. It doesn't look like the documented ones would
have much effect (maybe hotplug enable bits?), I'll have to look
through the MCHBAR differences to see if there's anything there we
should worry about.
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-11-06 21:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 16:39 i915: high power consumption after suspend/resume Andrew Lutomirski
2009-10-03 16:50 ` [resend] " Andrew Lutomirski
2009-10-05 16:21 ` Jesse Barnes
2009-10-08 3:44 ` Andrew Lutomirski
2009-10-29 16:47 ` Jesse Barnes
2009-10-29 17:22 ` Andrew Lutomirski
2009-10-29 17:40 ` Andrew Lutomirski
2009-10-30 6:25 ` Andrew Lutomirski
2009-10-30 15:37 ` Jesse Barnes
2009-10-30 18:55 ` Andrew Lutomirski
2009-11-05 4:00 ` Andrew Lutomirski
2009-11-05 16:28 ` Jesse Barnes
2009-11-06 20:25 ` Andrew Lutomirski
2009-11-06 21:57 ` Jesse Barnes [this message]
2009-11-10 14:42 ` Andrew Lutomirski
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=20091106135722.5abfdd03@jbarnes-piketon \
--to=jbarnes@virtuousgeek.org \
--cc=dri-devel@lists.sf.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
/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.