linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: pci express switch driver
Date: Fri, 05 Nov 2004 21:57:34 +0000	[thread overview]
Message-ID: <20041105135733.A17788@unix-os.sc.intel.com> (raw)
In-Reply-To: <73943A6B3BEAA1468EE1A4A090129F436DABCD@corpbridge.corp.idt.com>

On Thu, Nov 04, 2004 at 03:40:54PM -0800, Sadik, Pallathu wrote:
> 
>    Let us say, I have put the second switch and the endpoints
> associated with it to low power mode (D3hot). Then I press
> the Attention button on a downstream port of the second
> switch. This should generate PM_PME event. This event
> should be handled by the ACPI, right? Hence the
> question.
> 
I _think_ I understand your question better now - you are trying
to see if acpi based hotplug will work if you force an acpi
interrupt by putting the switch and devices in the low power
state before you hotplug, correct?

In the case you mentioned, just because an ACPI SCI is asserted
does not mean you will be able to use acpiphp based hotplug.
For ACPI based hotplug to work, your firmware has to create a 
namespace object for the p2p bridge that you are trying to 
hotadd so that acpiphp can install a notify handler on it. When
you hotplug the switch and cause the SCI, the corresponding Lxx
or Exx method for the GPE must issue an ACPI Notify on the 
switch object. Then acpiphp would get a chance to run and add
the switch. 

As I said before, acpiphp, shpc and pcie drivers do not 
currently have all the code to deal with switch hotplug so even
if you hack up the ACPI namespace to do this, the current 
hotplug code will not be able to deal with it anyway.

Rajesh



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

      parent reply	other threads:[~2004-11-05 21:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-10  2:15 pci express switch driver Sadik, Pallathu
2004-10-30  4:37 ` Greg KH
2004-11-02  1:58 ` Rajesh Shah
2004-11-03  0:42 ` Sy, Dely L
2004-11-04  1:52 ` Sadik, Pallathu
2004-11-04 22:22 ` Rajesh Shah
2004-11-04 23:40 ` Sadik, Pallathu
2004-11-05 21:57 ` Rajesh Shah [this message]

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=20041105135733.A17788@unix-os.sc.intel.com \
    --to=rajesh.shah@intel.com \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).