From: Rajat Jain <rajat.noida.india@gmail.com>
To: Rajesh Shah <rajesh.shah@intel.com>
Cc: Kristen Accardi <kristen.kml@gmail.com>,
greg@kroah.com, linux-kernel@vger.kernel.org,
linux-newbie@vger.kernel.org, acpi-devel@lists.sourceforge.net,
linux-hotplug-devel@lists.sourceforge.net,
dkumar@noida.hcltech.com
Subject: Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver
Date: Fri, 29 Jul 2005 19:23:40 +0900 [thread overview]
Message-ID: <b115cb5f05072903233fef8dc3@mail.gmail.com> (raw)
In-Reply-To: <20050728175217.A1821@unix-os.sc.intel.com>
On 7/29/05, Rajesh Shah <rajesh.shah@intel.com> wrote:
> On Thu, Jul 28, 2005 at 07:45:49PM +0900, Rajat Jain wrote:
> >
> > Okay. I'm sorry but I'm not very clear with this. I'm just putting
> > down here my understanding. So basically we have two mutually
> > EXCLUSIVE hotplug drivers I can use for PCI Express:
> >
> A hotplug slot can be controlled only by a single hotplug
> technology - pcie shpc or acpiphp. However, different parts of
> the I/O hierarchy can be controlled by different technologies.
> For example, a host bridge I/O complex can be hotplugged using
> acpiphp, but end devices under this IO complex may be hotpplugged
> using pcie or shpc hotplug.
>
> > 1) "pciehp.ko" : We use this PCIE HP driver when our BIOS supports
> > Native Hot-plug for PCI Express (which means that hot-plug will be
> > handled by OS single handedly).
> >
> > 2) "acpiphp.ko" : We use this "generic" ACPI HP driver when BIOS
> > allows only ITSELF to handle hot-plug events.
> >
> No, acpi hotplug is not handled by BIOS only.
> Both acpi and pcie hotplug need firmware support as well as hardware
> support. Hardware in many (but not all) systems support both types of
> hotplug and its up to the BIOS to decide which type to support. If the
> platform supports pcie hotplug, you see an _OSC & _SUN methods in the
> ACPI namespace and the pciehp driver controls hotplug slots. If the
> system supports acpi hotplug, you see _ADR and _EJ0 methods in the ACPI
> namespace and the acpiphp driver controls the corresponding hotplug slots.
>
> Rajesh
>
Thanks a lot. It has proved to be a very useful information for me. I
can now do some R&D on it.
Thanks again,
Rajat
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
WARNING: multiple messages have this Message-ID (diff)
From: Rajat Jain <rajat.noida.india@gmail.com>
To: Rajesh Shah <rajesh.shah@intel.com>
Cc: Kristen Accardi <kristen.kml@gmail.com>,
greg@kroah.com, linux-kernel@vger.kernel.org,
linux-newbie@vger.kernel.org, acpi-devel@lists.sourceforge.net,
linux-hotplug-devel@lists.sourceforge.net,
dkumar@noida.hcltech.com
Subject: Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver
Date: Fri, 29 Jul 2005 10:23:40 +0000 [thread overview]
Message-ID: <b115cb5f05072903233fef8dc3@mail.gmail.com> (raw)
In-Reply-To: <20050728175217.A1821@unix-os.sc.intel.com>
On 7/29/05, Rajesh Shah <rajesh.shah@intel.com> wrote:
> On Thu, Jul 28, 2005 at 07:45:49PM +0900, Rajat Jain wrote:
> >
> > Okay. I'm sorry but I'm not very clear with this. I'm just putting
> > down here my understanding. So basically we have two mutually
> > EXCLUSIVE hotplug drivers I can use for PCI Express:
> >
> A hotplug slot can be controlled only by a single hotplug
> technology - pcie shpc or acpiphp. However, different parts of
> the I/O hierarchy can be controlled by different technologies.
> For example, a host bridge I/O complex can be hotplugged using
> acpiphp, but end devices under this IO complex may be hotpplugged
> using pcie or shpc hotplug.
>
> > 1) "pciehp.ko" : We use this PCIE HP driver when our BIOS supports
> > Native Hot-plug for PCI Express (which means that hot-plug will be
> > handled by OS single handedly).
> >
> > 2) "acpiphp.ko" : We use this "generic" ACPI HP driver when BIOS
> > allows only ITSELF to handle hot-plug events.
> >
> No, acpi hotplug is not handled by BIOS only.
> Both acpi and pcie hotplug need firmware support as well as hardware
> support. Hardware in many (but not all) systems support both types of
> hotplug and its up to the BIOS to decide which type to support. If the
> platform supports pcie hotplug, you see an _OSC & _SUN methods in the
> ACPI namespace and the pciehp driver controls hotplug slots. If the
> system supports acpi hotplug, you see _ADR and _EJ0 methods in the ACPI
> namespace and the acpiphp driver controls the corresponding hotplug slots.
>
> Rajesh
>
Thanks a lot. It has proved to be a very useful information for me. I
can now do some R&D on it.
Thanks again,
Rajat
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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
WARNING: multiple messages have this Message-ID (diff)
From: Rajat Jain <rajat.noida.india@gmail.com>
To: Rajesh Shah <rajesh.shah@intel.com>
Cc: Kristen Accardi <kristen.kml@gmail.com>,
greg@kroah.com, linux-kernel@vger.kernel.org,
linux-newbie@vger.kernel.org, acpi-devel@lists.sourceforge.net,
linux-hotplug-devel@lists.sourceforge.net,
dkumar@noida.hcltech.com
Subject: Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver
Date: Fri, 29 Jul 2005 19:23:40 +0900 [thread overview]
Message-ID: <b115cb5f05072903233fef8dc3@mail.gmail.com> (raw)
In-Reply-To: <20050728175217.A1821@unix-os.sc.intel.com>
On 7/29/05, Rajesh Shah <rajesh.shah@intel.com> wrote:
> On Thu, Jul 28, 2005 at 07:45:49PM +0900, Rajat Jain wrote:
> >
> > Okay. I'm sorry but I'm not very clear with this. I'm just putting
> > down here my understanding. So basically we have two mutually
> > EXCLUSIVE hotplug drivers I can use for PCI Express:
> >
> A hotplug slot can be controlled only by a single hotplug
> technology - pcie shpc or acpiphp. However, different parts of
> the I/O hierarchy can be controlled by different technologies.
> For example, a host bridge I/O complex can be hotplugged using
> acpiphp, but end devices under this IO complex may be hotpplugged
> using pcie or shpc hotplug.
>
> > 1) "pciehp.ko" : We use this PCIE HP driver when our BIOS supports
> > Native Hot-plug for PCI Express (which means that hot-plug will be
> > handled by OS single handedly).
> >
> > 2) "acpiphp.ko" : We use this "generic" ACPI HP driver when BIOS
> > allows only ITSELF to handle hot-plug events.
> >
> No, acpi hotplug is not handled by BIOS only.
> Both acpi and pcie hotplug need firmware support as well as hardware
> support. Hardware in many (but not all) systems support both types of
> hotplug and its up to the BIOS to decide which type to support. If the
> platform supports pcie hotplug, you see an _OSC & _SUN methods in the
> ACPI namespace and the pciehp driver controls hotplug slots. If the
> system supports acpi hotplug, you see _ADR and _EJ0 methods in the ACPI
> namespace and the acpiphp driver controls the corresponding hotplug slots.
>
> Rajesh
>
Thanks a lot. It has proved to be a very useful information for me. I
can now do some R&D on it.
Thanks again,
Rajat
next prev parent reply other threads:[~2005-07-29 10:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050725021747.67869.qmail@web34405.mail.mud.yahoo.com>
[not found] ` <20050725021747.67869.qmail-6mNr3ekj/EivuULXzWHTWIglqE1Y4D90QQ4Iyu8u01E@public.gmane.org>
2005-07-25 2:49 ` Re: Problem while inserting pciehp (PCI Express Hot-plug) driver Rajat Jain
2005-07-25 2:49 ` Rajat Jain
2005-07-25 2:49 ` Rajat Jain
[not found] ` <b115cb5f0507241949da02aa7-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-07-27 18:29 ` Kristen Accardi
2005-07-27 18:29 ` Kristen Accardi
2005-07-27 18:29 ` Kristen Accardi
2005-07-28 10:45 ` Rajat Jain
2005-07-28 10:45 ` Rajat Jain
2005-07-28 10:45 ` Rajat Jain
2005-07-28 17:00 ` Kristen Accardi
2005-07-28 17:00 ` Kristen Accardi
2005-07-28 17:00 ` Kristen Accardi
[not found] ` <b115cb5f05072803451836055c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-07-29 0:52 ` Rajesh Shah
2005-07-29 0:52 ` Rajesh Shah
2005-07-29 0:52 ` Rajesh Shah
2005-07-29 10:23 ` Rajat Jain [this message]
2005-07-29 10:23 ` Rajat Jain
2005-07-29 10:23 ` Rajat Jain
2005-07-30 16:20 kylin
2005-07-30 16:20 ` kylin
2005-07-30 16:20 ` kylin
[not found] ` <87ab37ab0507300920570b0ea6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-08-03 17:49 ` Rajesh Shah
2005-08-03 17:49 ` Rajesh Shah
2005-08-03 17:49 ` Rajesh Shah
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=b115cb5f05072903233fef8dc3@mail.gmail.com \
--to=rajat.noida.india@gmail.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=dkumar@noida.hcltech.com \
--cc=greg@kroah.com \
--cc=kristen.kml@gmail.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=rajesh.shah@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.