From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, Jesse Barnes <jbarnes@virtuousgeek.org>,
Dave Airlie <airlied@redhat.com>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Suspend problems in 2.6.31-rc6
Date: Thu, 20 Aug 2009 09:05:28 +0800 [thread overview]
Message-ID: <20090820010528.GA9596@zhen-devel.sh.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0908191040050.3001-100000@iolanthe.rowland.org>
[-- Attachment #1.1: Type: text/plain, Size: 1298 bytes --]
On 2009.08.19 10:42:07 -0400, Alan Stern wrote:
> On Wed, 19 Aug 2009, Zhenyu Wang wrote:
>
> > Rafael, as I added this restore long time ago, pci core has changed in some way?
> > We had problem when reconfigure agp GTT space in resume, as we must be sure
> > gfx device's config space has been restored properly, and as 02:00 gfx device
> > restored later than host bridge 00:00 device, that came to my origin patch to
> > restore it earlier.
>
> Why did you do it that way? I mean, why not restore the gfx device's
> config space in its own resume routine instead of in the host bridge's
> resume routine?
>
That's the order issue I have mentioned. intel_agp is the pci driver for
host bridge (dev 00:00), and drm/i915 is the pci driver for gfx device
(dev 00:02). Host bridge will always resume earlier than gfx device, but
for intel_agp we need to access gfx device when reconfigure GTT in resume,
we can't wait until restore happen in i915 driver.
So there might be a conflict here, as i915 driver also do pci_restore_state()
after we did reconfigure in intel_agp driver, some configs may be corrupted
then. Although I haven't seen it in real testing.
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2009-08-20 1:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 15:11 Suspend problems in 2.6.31-rc6 Alan Stern
2009-08-17 18:28 ` Rafael J. Wysocki
2009-08-17 20:53 ` Alan Stern
2009-08-17 21:14 ` Greg KH
2009-08-17 21:15 ` Greg KH
2009-08-17 21:31 ` Jiri Slaby
2009-08-17 21:33 ` Jiri Slaby
2009-08-17 21:21 ` Rafael J. Wysocki
2009-08-17 21:50 ` Alan Stern
2009-08-18 16:07 ` Alan Stern
2009-08-18 23:22 ` Rafael J. Wysocki
2009-08-19 2:01 ` Zhenyu Wang
2009-08-19 14:42 ` Alan Stern
2009-08-20 1:05 ` Zhenyu Wang [this message]
2009-08-20 14:03 ` Alan Stern
2009-08-21 1:17 ` Zhenyu Wang
2009-08-20 15:34 ` Rafael J. Wysocki
2009-08-19 14:26 ` Alan Stern
2009-08-19 21:22 ` Rafael J. Wysocki
2009-08-20 15:17 ` Alan Stern
2009-08-20 16:17 ` Rafael J. Wysocki
2009-08-21 1:21 ` Zhenyu Wang
2009-08-21 3:13 ` Zhenyu Wang
2009-08-21 14:32 ` Alan Stern
2009-08-21 17:01 ` Rafael J. Wysocki
2009-08-24 2:34 ` Zhenyu Wang
2009-08-24 18:55 ` Rafael J. Wysocki
2009-08-25 0:59 ` Alan Stern
2009-08-27 14:51 ` Alan Stern
2009-08-27 16:18 ` Jesse Barnes
2009-08-24 1:30 ` Zhenyu Wang
2009-08-20 15:41 ` Rafael J. Wysocki
2009-08-20 16:05 ` 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=20090820010528.GA9596@zhen-devel.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=airlied@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.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.