public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Adam Belay <abelay@novell.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Greg KH <greg@kroah.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH 9/9] PCI PM: generic suspend/resume fixes
Date: Tue, 06 Jun 2006 10:33:59 +1000	[thread overview]
Message-ID: <1149554040.559.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1149529685.7831.177.camel@localhost.localdomain>

On Mon, 2006-06-05 at 13:48 -0400, Adam Belay wrote:

> I've only tested this on a few x86 boxes.  However, I think it's moving
> in the right direction for correctly suspending devices.  It's worth
> mentioning that the PCI PM specification requires the device to be
> disabled before entering D3 (something that we fail to do before this
> patchset), and the vast majority of devices would end up in this state
> if we were using pci_set_power_state() in this function.

That should be done only for D3 though. Not other states.

> Unfortunately, far too many drivers still depend on this generic suspend
> call, when they should all implement their own suspend function.  I
> would except pci_disable_device() issues to the the exception, and as
> such, device drivers should provide a ->suspend function that doesn't
> call pci_disable_device() when they know their hardware can be
> problematic.
> 
> With that in mind, any thoughts on giving this a little time in -mm and
> seeing how it fares?  If any problems come up, we could revert to a more
> conservative approach.

Problem is that you may end up disabling something like ... the ACPI
controller, and that will cause VERY BAD things with your BIOS when
actually trying to enter S3 or S4

Ben.



  parent reply	other threads:[~2006-06-06  0:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05  8:46 [PATCH 9/9] PCI PM: generic suspend/resume fixes Adam Belay
2006-06-05 10:21 ` Alan Cox
2006-06-05 17:48   ` Adam Belay
2006-06-05 18:45     ` Alan Cox
2006-06-06  0:33     ` Benjamin Herrenschmidt [this message]
2006-06-07  3:13       ` Adam Belay

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=1149554040.559.8.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=abelay@novell.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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