public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-pm@lists.osdl.org
Cc: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
Subject: Re: A reference implementation of PCI suspend/resume?
Date: Mon, 16 May 2005 22:56:29 +0200	[thread overview]
Message-ID: <200505162256.30090.rjw@sisk.pl> (raw)
In-Reply-To: <20050516201606.GA11189@neo.rr.com>

[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]

Hi,

On Monday, 16 of May 2005 22:16, Adam Belay wrote:
> On Fri, May 13, 2005 at 10:06:42PM -0700, Fabrice Gautier wrote:
> > Hi,
> > 
> > > From: Shaohua Li [mailto:shaohua.li@intel.com] 
> > > Sent: Wednesday, May 11, 2005 6:25 PM
> > > To: linux-pm
> > > Subject: [linux-pm] A reference implementation of PCI suspend/resume?
> > > 
> > > Hi,
> > > There are still many PCI drivers don't implement their 
> > > .suspend/.resume
> > > methods correctly. I felt it would be quite helpful there is 
> > > a reference
> > > implementation. Here is my thought:
> > > 
> > > [...snip...]
> > > 
> > > Currently many drivers don't call
> > > free_irq/request_irq/pci_disable_device, which makes unexpected
> > > interrupt occur and even break suspend/resume in some systems. 
> > 
> > I don't understand why not calling free_irq would cause unexpected
> > interrupts.
> 
> I don't think it would.

Please have a look at http://bugzilla.kernel.org/show_bug.cgi?id=4416
Perhaps you can figure out what else is going on there ...

> However, there are three reasons in favor of unregister PCI interrupts:
> 
> a.) the kernel will complain if the irq isn't handled, revealing a possible
> problem with the driver's suspend routine.
> 
> b.) You're assuming every device has its own interrupt.  This may not be the
> case.  Let's say one device was sharing interrupts with a few other devices.
> We don't want it's interrupt handler to mess up things when it tries to read
> hardware registers from a physically "off" device, as it may possibly generate
> errors.  Almost every interrupt handler assumes the device is "on", as it
> should.  Each interrupt handler has to ask its hardware if it generated the
> interrupt.
> 
> c.) Selective device suspending: obviously we don't want to leave stale
> interrupt handlers around.

I agree.

Greets,
Rafael
 

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2005-05-16 20:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-14  5:06 A reference implementation of PCI suspend/resume? Fabrice Gautier
2005-05-16  4:53 ` David Brownell
2005-05-16  8:55 ` Shaohua Li
2005-05-16 20:16 ` Adam Belay
2005-05-16 20:56   ` Rafael J. Wysocki [this message]
2005-05-16 21:19   ` Jordan Crouse
2005-05-17  0:26     ` David Brownell
2005-05-17  9:10       ` Rafael J. Wysocki
2005-05-17 18:35         ` David Brownell
2005-05-17 19:28           ` Rafael J. Wysocki
2005-05-18  1:26             ` Adam Belay
2005-05-18 17:40               ` Rafael J. Wysocki
2005-05-18 18:32                 ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2005-05-16 19:02 Fabrice Gautier
2005-05-16 19:39 ` David Brownell
2005-05-12  1:24 Shaohua Li
2005-05-12  6:21 ` Adam Belay
2005-05-12  7:03   ` Shaohua Li
2005-05-27  6:49 ` Shaohua Li
2005-05-27  7:20   ` Pavel Machek

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=200505162256.30090.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=Fabrice_Gautier@sdesigns.com \
    --cc=linux-pm@lists.osdl.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