public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: A reference implementation of PCI suspend/resume?
Date: Mon, 16 May 2005 12:39:53 -0700	[thread overview]
Message-ID: <200505161239.54238.david-b@pacbell.net> (raw)
In-Reply-To: <9F77D654ED40B74CA79E5A60B97A087B0310DD26@sd-exchange.sdesigns.com>

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

On Monday 16 May 2005 12:02 pm, Fabrice Gautier wrote:
> > 
> > There's PCI ... and PCI with PM capabilities.  That rule about only
> > issuing PME transactions while suspended can only apply in the latter
> > case.  That is, not all PCI devices support the PCI PM rules; drivers
> > may need to help the hardware.
> 
> You mean, you support some kind of power management on PCI devices without
> PM capabilities ? How are you even sure that the pci_set_power_state will
> work in those kind of devices.

Linux must certainly support suspend() and resume() methods for such
devices.  In terms of PCI PM terminology, they will either stay in
the PCI_D0 state during suspend, or go into PCI_D3cold ... and in
the latter case, the device driver's resume() is going to have to
know how to reinit from a reset state.  (They already have code to
init from that state, so it should be no problem.)

By definition, pci_set_power_state() will be a NOP.  There might
be firmware that knows how to switch power on/off, or maybe not;
that would be board-specific.


> In any case, anyway it works I would say this is very much device specific
> and not really part of a reference implementation. This is supposed to be a
> reference implementation for "PCI PM compliant" devices right ?

It was supposed to be a reference implementation, yes.  But if it was
only for one subset of PCI devices, I didn't notice any suggestion of
that before now.  The "works for small subset" implementation wouldn't
be anywhere near as useful.

- Dave




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



  reply	other threads:[~2005-05-16 19:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 19:02 A reference implementation of PCI suspend/resume? Fabrice Gautier
2005-05-16 19:39 ` David Brownell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-14  5:06 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
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
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=200505161239.54238.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --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