From: Dely Sy <dlsy@snoqualmie.dp.intel.com>
To: gregkh@suse.de, rajesh.shah@intel.com
Cc: akpm@osdl.org, dely.l.sy@intel.com, len.brown@intel.com,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
pcihpd-discuss@lists.sourceforge.net, tony.luck@intel.com
Subject: RE: [RFC/Patch 0/12] ACPI based root bridge hot-add
Date: Tue, 22 Mar 2005 19:13:34 -0800 [thread overview]
Message-ID: <200503230313.j2N3DYpE010786@snoqualmie.dp.intel.com> (raw)
On Monday, March 21, 2005 5:07 PM, Dely Sy wrote:
> On Monday, March 21, 2005 10:05 AM, Rajesh Shah wrote:
> > On Fri, Mar 18, 2005 at 09:13:32PM -0800, Greg KH wrote:
> > > - Does this break the i386 acpiphp functionality?
> > Dely Sy had tested hotplug with an earlier version of my patches
> > (with minor differences from the current series) on i386 and it
> > worked fine. She probably hasn't tested the latest one. Dely,
> > could you check that please?
> I tested an earlier version of this patch on my i386 system with
> PCI Express hot-plug slots. The i386 acpiphp functionality worked
> fine - i.e. I was able to do hot-plug of single- & multi-function
> cards.
> I'll check this new patch on my system.
Earlier I reported that Matthew's acpiphp rewrite had problem in
powering down slot on my i386 system. The following patch is
needed to get the acpiphp rewrite properly powering down the slot.
A similar patch was sent out to Matthew for comment and Rajesh
had tested the patch on Tiger4.
I just did a test of Rajesh's latest patch on 2.6.11.5 with
Wilcox's acpiphp rewrite and the following patch. Hot-plug of
PCI Express card worked fine on my i386 system
Thanks,
Dely
Signed-off-by: Dely Sy <dely.l.sy@intel.com>
diff -urpN linux-2.6.11.5rbha/drivers/pci/hotplug/acpiphp_glue.c linux-2.6.11.5rbhatst/drivers/pci/hotplug/acpiphp_glue.c
--- linux-2.6.11.5rbha/drivers/pci/hotplug/acpiphp_glue.c 2005-03-22 00:56:04.000000000 -0800
+++ linux-2.6.11.5rbhatst/drivers/pci/hotplug/acpiphp_glue.c 2005-03-22 23:21:23.000000000 -0800
@@ -586,7 +586,7 @@ static int power_off_slot(struct acpiphp
list_for_each (l, &slot->funcs) {
func = list_entry(l, struct acpiphp_func, sibling);
- if (func->pci_dev && (func->flags & FUNC_HAS_PS3)) {
+ if (func->flags & FUNC_HAS_PS3) {
status = acpi_evaluate_object(func->handle, "_PS3", NULL, NULL);
if (ACPI_FAILURE(status)) {
warn("%s: _PS3 failed\n", __FUNCTION__);
@@ -601,7 +601,7 @@ static int power_off_slot(struct acpiphp
func = list_entry(l, struct acpiphp_func, sibling);
/* We don't want to call _EJ0 on non-existing functions. */
- if (func->pci_dev && (func->flags & FUNC_HAS_EJ0)) {
+ if (func->flags & FUNC_HAS_EJ0) {
/* _EJ0 method take one argument */
arg_list.count = 1;
arg_list.pointer = &arg;
next reply other threads:[~2005-03-23 1:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 3:13 Dely Sy [this message]
2005-03-23 23:03 ` [Pcihpd-discuss] " Tom Duffy
2005-03-31 22:03 ` Rajesh Shah
2005-04-02 0:10 ` Tom Duffy
-- strict thread matches above, loose matches on Subject: below --
2005-03-22 1:06 Sy, Dely L
2005-03-18 21:38 Rajesh Shah
2005-03-19 5:13 ` Greg KH
2005-03-21 18:04 ` Rajesh Shah
2005-03-21 18:27 ` Greg KH
2005-03-31 19:06 ` Len Brown
2005-03-19 13:50 ` Paul Ionescu
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=200503230313.j2N3DYpE010786@snoqualmie.dp.intel.com \
--to=dlsy@snoqualmie.dp.intel.com \
--cc=akpm@osdl.org \
--cc=dely.l.sy@intel.com \
--cc=gregkh@suse.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=rajesh.shah@intel.com \
--cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®