From: Pavel Machek <pavel@ucw.cz>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Airlie <airlied@linux.ie>
Subject: Re: [PATCH] don't suspend/resume 8xx chips
Date: Fri, 28 Mar 2008 15:40:04 +0100 [thread overview]
Message-ID: <20080328144003.GF4404@ucw.cz> (raw)
In-Reply-To: <200803261628.12336.jesse.barnes@intel.com>
On Wed 2008-03-26 16:28:12, Jesse Barnes wrote:
> Recent testing has turned up some bugs in the new Intel suspend/resume code
> for old, 8xx chipsets. So for 2.6.25 it probably makes sense to apply this
> patch, which should prevent the new code from getting called on those
> chipsets. We should have this fixed soon, but not in time for 2.6.25
> unfortunately. Note that this patch (along with the suspend/resume code in
> general) could use more testing.
>
> Signed-off-by: Jesse Barnes <jesse.barnes@intel.com>
>
> diff --git a/drivers/char/drm/i915_dma.c b/drivers/char/drm/i915_dma.c
> index e9d6663..6964a28 100644
> --- a/drivers/char/drm/i915_dma.c
> +++ b/drivers/char/drm/i915_dma.c
> @@ -762,6 +762,11 @@ int i915_driver_load(struct drm_device *dev, unsigned
> long
> unsigned long base, size;
> int ret = 0, mmio_bar = IS_I9XX(dev) ? 0 : 1;
>
> + if (!IS_I9XX(dev)) {
> + dev->driver->suspend = NULL;
> + dev->driver->resume = NULL;
> + }
> +
Are you sure your driver needs no state saving?
Maybe register suspend that printks, returns error?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-03-28 20:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 23:28 [PATCH] don't suspend/resume 8xx chips Jesse Barnes
2008-03-27 8:38 ` Soren Hansen
2008-05-05 22:07 ` Jesse Barnes
2008-03-28 14:40 ` Pavel Machek [this message]
2008-03-28 20:13 ` 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=20080328144003.GF4404@ucw.cz \
--to=pavel@ucw.cz \
--cc=airlied@linux.ie \
--cc=jesse.barnes@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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