From: Chris Wilson <chris@chris-wilson.co.uk>
To: Zhenyu Wang <zhenyuw@linux.intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/8] drm/i915: remove CACHE_MODE_0 save/restore
Date: Mon, 21 Mar 2011 09:44:00 +0000 [thread overview]
Message-ID: <b7da2f$qpnotu@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <1300699639-23996-5-git-send-email-zhenyuw@linux.intel.com>
On Mon, 21 Mar 2011 17:27:15 +0800, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> we don't use it anywhere.
But we still need to restore the value after resume, right? Or are
guaranteed that it will be reset to the default?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-21 9:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 9:27 [PATCH 0/8] Patches for Sandybridge suspend/resume fixes Zhenyu Wang
2011-03-21 9:27 ` [PATCH 1/8] drm/i915: clock gating fix for gen5 and gen6 Zhenyu Wang
2011-03-21 9:27 ` [PATCH 2/8] drm/i915: remove LBB config save/restore Zhenyu Wang
2011-03-21 17:36 ` Jesse Barnes
2011-03-22 1:29 ` Zhenyu Wang
2011-03-22 1:39 ` Jesse Barnes
2011-03-21 9:27 ` [PATCH 3/8] drm/i915: save/restore DSPARB only for chip before gen4 Zhenyu Wang
2011-03-21 17:39 ` Jesse Barnes
2011-03-22 1:44 ` Zhenyu Wang
2011-03-21 9:27 ` [PATCH 4/8] drm/i915: remove CACHE_MODE_0 save/restore Zhenyu Wang
2011-03-21 9:44 ` Chris Wilson [this message]
2011-03-21 17:40 ` Jesse Barnes
2011-03-22 1:20 ` Zhenyu Wang
2011-03-21 9:27 ` [PATCH 5/8] drm/i915: save/restore MI_ARB_STATE only for gen3 Zhenyu Wang
2011-03-21 17:43 ` Jesse Barnes
2011-03-21 9:27 ` [PATCH 6/8] drm/i915: change force wake order for GT read Zhenyu Wang
2011-03-21 9:46 ` Chris Wilson
2011-03-22 1:27 ` Zhenyu Wang
2011-03-22 7:25 ` Chris Wilson
2011-03-21 9:27 ` [PATCH 7/8] drm/i915: move sandybridge RC6 enable in resume after ring initialization Zhenyu Wang
2011-03-21 17:46 ` Jesse Barnes
2011-03-22 1:48 ` Zhenyu Wang
2011-03-21 9:27 ` [PATCH 8/8] drm/i915: only save/restore VGA clock regs for non-KMS case Zhenyu Wang
2011-03-21 9:49 ` Chris Wilson
2011-03-21 17:49 ` 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='b7da2f$qpnotu@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=zhenyuw@linux.intel.com \
/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