public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Cc: Greg KH <gregkh@suse.de>,
	linux-acpi@vger.kernel.org, pcihpd-discuss@lists.sourceforge.net
Subject: Re: [Pcihpd-discuss] what is writing to /sys/bus/pci/slot/<slot_no>/power really supposed to do?
Date: Mon, 1 Oct 2007 11:46:55 -0600	[thread overview]
Message-ID: <20071001174655.GK12049@parisc-linux.org> (raw)
In-Reply-To: <20071001103557.a1252b78.kristen.c.accardi@intel.com>

On Mon, Oct 01, 2007 at 10:35:57AM -0700, Kristen Carlson Accardi wrote:
> So - here's where we get to interpret.  The spec says that _EJ0 is
> used to "eject" the card.  From the spec:
> 6.3.3 _EJx (Eject)
> These control methods are optional and are supplied for devices that 
> support a software-controlled VCR-style ejection mechanism or that 
> require an action be performed such as isolation of power/data lines 
> before the device can be removed from the system. 
> <snip>
> For hot removal, the device must be immediately ejected when OSPM calls 
> the _EJ0 control method. The _EJ0 control method does not return until 
> ejection is complete. After calling _EJ0, OSPM verifies the
> device no longer exists to determine if the eject succeeded. 
> For _HID devices, OSPM evaluates the _STA method. For _ADR devices, 
> OSPM checks with the bus driver for that device.
> 
> So, when I read this, it seems like if a vendor followed the spec,
> executing _EJ0 would hang until we physically pulled the card out
> of the system, which seems bad.  So, maybe this is why we don't call
> _EJ0?  

I think you've misread it.  Follow the other arm of the 'or':
	"require an action be performed such as isolation of power/data
	lines before the device can be removed from the system."
So I interpret "the eject succeeded" as "power/data lines are isolated"
for PCI cards.

> _PS3 apparently is used to put a device into D3.  By "device" here
> I'm not sure if we are talking about the adapter in the slot, or the
> slot itself.

Slots don't have a D3.  If you're talking about the bus, I guess there's
a B3.  But D is for devices.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2007-10-01 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01 17:08 what is writing to /sys/bus/pci/slot/<slot_no>/power really supposed to do? Kristen Carlson Accardi
2007-10-01 17:19 ` Greg KH
2007-10-01 17:35   ` Kristen Carlson Accardi
2007-10-01 17:46     ` Matthew Wilcox [this message]
2007-10-01 17:43 ` [Pcihpd-discuss] " Gary Hade
2007-10-01 17:50   ` Kristen Carlson Accardi
2007-10-01 18:33     ` Gary Hade
2007-10-01 18:39       ` Gary Hade
2007-10-01 18:43       ` Kristen Carlson Accardi

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=20071001174655.GK12049@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=gregkh@suse.de \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=pcihpd-discuss@lists.sourceforge.net \
    /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