Re: Re: Problem while inserting pciehp (PCI Express Hot-plug) driver

From: Rajesh Shah (rajesh.shah_at_intel.com)
Date: 07/29/05

  • Next message: expansao_infor: "PROPOSTA PARA QDIVULGA=C7=C3O?= DE EMPRESA" 
    Date:	Thu, 28 Jul 2005 17:52:17 -0700
To: Rajat Jain <rajat.noida.india@gmail.com>

    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
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: expansao_infor: "PROPOSTA PARA QDIVULGA=C7=C3O?= DE EMPRESA"

    Relevant Pages

    • PATCH-ACPI based CPU hotplug[0/6]
      ... I am resending the following set of patches which support ACPI based physical ... CPU hotplug for IA64 platform, after having including all the community ...
      (Linux-Kernel)
    • Re: [PATCH 0/5][RFC] Physical PCI slot objects
      ... I think your patches assume that all the hotplug slots have ... ACPI _SUN method regardless of the hotplug controller type, ... But I think there are hotplug slots without _SUN. ... detect all physical PCI slots in the system (as described by ...
      (Linux-Kernel)
    • [BKPATCH] ACPI for 2.6.11
      ... The ACPI spec mandates it be disabled only for C3. ... ACPI 3.0 support is nearing completion in both the iASL ... resulting string length was incorrectly calculated. ... Initial container driver to support hotplug notifications ...
      (Linux-Kernel)
    • Re: [PATCH 3/3] Altix: Add ACPI SSDT PCI device support (hotplug)
      ... ACPI SSDT table containing info for every device and PPB attached to the slot. ... These SSDTs are generated by the prom at initial boot and hotplug time. ... On hot unplugs ), if running with an ACPI capable prom, ...
      (Linux-Kernel)
    • [PATCH 3/3] Altix: Add ACPI SSDT PCI device support (hotplug)
      ... ACPI SSDT table containing info for every device and PPB attached to the slot. ... These SSDTs are generated by the prom at initial boot and hotplug time. ... int func, num_funcs; ...
      (Linux-Kernel)