Re: [RFC/PATCH]reconfigure MSI registers after resume

2005-09-02 Thread Rajesh Shah
On Thu, Sep 01, 2005 at 01:59:32PM -0700, Nguyen, Tom L wrote: > On Thursday, September 01, 2005 1:10 PM Andrew Morton wrote: > > Is it not possible to do this in some single centralized place? > Existing pci_save_state(dev)/pci_restore_state(dev) covers only 64 bytes > of PCI header. One solution

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

2005-08-03 Thread Rajesh Shah
On Sun, Jul 31, 2005 at 12:20:30AM +0800, kylin wrote: > I wonder if i can workaround the MSI using the polling way on the > server geared by E7520 and the firmware with no OSC implemented > Per the PCI firmware spec (I'm looking at draft 0.9, version 3.0), the OS must explicitly get control of na

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

2005-07-28 Thread Rajesh Shah
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 si

Re: hot-addacpi-hotplug-decouple-slot-power-state-changes-from-physical-hotplug.patch

2005-04-18 Thread Rajesh Shah
On Sat, Apr 16, 2005 at 11:46:13AM -0700, Paul Ionescu wrote: > > Was this setup supposed to work ? > Not yet, sorry. This patch was simply decoupling the power state of the device from its physical presence in the slot. It had nothing to do about programming p2p bridges and subordinate devices

Re: [Pcihpd-discuss] RE: [RFC/Patch 0/12] ACPI based root bridge hot-add

2005-03-31 Thread Rajesh Shah
m physical presence. You can now echo to the corresponding sysfs power control file to repeatedly enable and disable a device without having to physically re-insert it. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.12-rc1-mm4-rshah1/drivers/pci/hotplug/acpiphp_glue

Reading root bridge resources

2005-03-30 Thread Rajesh Shah
Greg, A while back I had volunteered to write a patch that stores the resource ranges being decoded by root bridges for ACPI based i386 and x86_64 systems. The thread at: http://sourceforge.net/mailarchive/message.php?msg_id=10604487 has some context regarding this. The basic intent was to allow h

Re: [ACPI] Re: [RFC/Patch 0/12] ACPI based root bridge hot-add

2005-03-21 Thread Rajesh Shah
On Mon, Mar 21, 2005 at 12:34:07PM -0800, Paul Ionescu wrote: > > --- Rajesh Shah <[EMAIL PROTECTED]> wrote: > > > > No. The current patches only trigger when a _root_ bridge is > > hot-added, not a PCI to PCI bridge (which is what the docking > > station

Re: [ACPI] Re: [RFC/Patch 0/12] ACPI based root bridge hot-add

2005-03-21 Thread Rajesh Shah
On Sat, Mar 19, 2005 at 03:50:16PM +0200, Paul Ionescu wrote: > > Does this mean that when it will be ported for i386, I will be able to > really use my Docking Station ? No. The current patches only trigger when a _root_ bridge is hot-added, not a PCI to PCI bridge (which is what the docking st

Re: [RFC/Patch 0/12] ACPI based root bridge hot-add

2005-03-21 Thread Rajesh Shah
On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote: > > This all looks very good, nice job. I only had one minor comment on the > patches, which I'll reply to directly. > > But I did have a few questions: > - This series relys on Mathew's rewrite of the acpiphp driver. > Is th

[patch 12/12] ACPI based root bridge hot-add

2005-03-18 Thread Rajesh Shah
acpiphp changes to support acpi based root bridge hot-add. This patch applies on top of the acpiphp re-write patch by Matthew Wilcox at: http://marc.theaimsgroup.com/?l=linux-ia64&m=110616116714938&w=2 Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rsha

[patch 08/12] Remove hot-plugged devices that could not be allocated resources

2005-03-18 Thread Rajesh Shah
ction. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/drivers/pci/setup-bus.c |5 - 1 files changed, 4 insertions(+), 1 deletion(-) diff -puN drivers/pci/setup-bus.c~discard_no_resource_devs drivers/pci/setup-bus.c --- linux-2.6.11-mm4-iohp/drivers/pci/

[patch 10/12] Allow ACPI .add and .start operations to be done independently

2005-03-18 Thread Rajesh Shah
separately after the hot-plugged devices have been properly configured. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/drivers/acpi/container.c |2 linux-2.6.11-mm4-iohp-rshah1/drivers/acpi/processor_core.c |2 linux-2.6.11-mm4-iohp-rshah1/driver

[patch 11/12] Export the interface to get PCI id for an ACPI handle

2005-03-18 Thread Rajesh Shah
Export an acpi interface to get PCI domain/bus/devfn information from the corresponding namespace handle. Used by acpiphp code to transpate the device handle of the hot-plugged root bridge to the corresponding pci location information. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> ---

[patch 09/12] Read bridge resources when fixing up the bus

2005-03-18 Thread Rajesh Shah
Read bridge io/mem/pfmem ranges when fixing up the bus so that bus resources are tracked. This is required to properly support pci end device and bridge hotplug. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/arch/ia64/pci/pci.c |4 1 files chan

[patch 06/12] Link newly created pci child bus to its parent on creation

2005-03-18 Thread Rajesh Shah
e the normal pci bus search functions for the hot-plug bridges/buses. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/drivers/pci/bus.c | 11 +++ linux-2.6.11-mm4-iohp-rshah1/drivers/pci/probe.c |4 ++-- 2 files changed, 9 insertions(+), 6 deletio

[patch 07/12] Make the PCI remove routines safe for failed hot-plug

2005-03-18 Thread Rajesh Shah
global device list. Make sure the pci remove functions can handle this case. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/drivers/pci/remove.c | 14 +- 1 files changed, 9 insertions(+), 5 deletions(-) diff -puN drivers/pci/remove.c~pci-

[patch 05/12] Take the PCI lock when modifying pci bus or device lists

2005-03-18 Thread Rajesh Shah
With root bridge and pci bridge hot-plug, new buses and devices can be added or removed at run time. Protect the pci bus and device lists with the pci lock when doing so. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/drivers/pci/probe.c | 12 +

[patch 04/12] Prevent duplicate bus numbers when scanning PCI bridge

2005-03-18 Thread Rajesh Shah
When hot-plugging a root bridge, as we try to assign bus numbers we may find that the hotplugged hieratchy has more PCI to PCI bridges (i.e. bus requirements) than available. Make sure we don't step over an existing bus when that happens. Signed-off-by: Rajesh Shah <[EMAIL P

[patch 03/12] Make pcibios_fixup_bus() hot-plug safe

2005-03-18 Thread Rajesh Shah
up the way pci resources are claimed (in pci_enable_device()), so this is only a stopgap fix. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/arch/ia64/pci/pci.c | 22 +- 1 files changed, 21 insertions(+), 1 deletion(-) diff -puN arc

[Patch 2/12] Fix pci_enable_device() for p2p bridges

2005-03-18 Thread Rajesh Shah
resources in its PCI BARs. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/arch/ia64/pci/pci.c | 10 +++--- 1 files changed, 7 insertions(+), 3 deletions(-) diff -puN arch/ia64/pci/pci.c~fix-ia64-pcibios_enable_resources arch/ia64/pci/pci.c --- linux-2.6.

[Patch 1/12] ACPI based root bridge hot-add

2005-03-18 Thread Rajesh Shah
many different places. Signed-off-by: Rajesh Shah <[EMAIL PROTECTED]> --- linux-2.6.11-mm4-iohp-rshah1/arch/i386/pci/common.c |2 - linux-2.6.11-mm4-iohp-rshah1/arch/i386/pci/legacy.c |2 + linux-2.6.11-mm4-iohp-rshah1/arch/i386/pci/numa.c |2 + linux-2.6.11-mm4-iohp-

[RFC/Patch 0/12] ACPI based root bridge hot-add

2005-03-18 Thread Rajesh Shah
Here is a series of patches to support ACPI hot-add of a root bridge hierarchy. The added hierarchy may contain other p2p bridges and end/leaf I/O devices too. The root bridge itself is assumed to have been assigned resource ranges, but the p2p bridges and end devices are not required to be initia