[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081104020700.GA11761@srcf.ucam.org>
Date: Tue, 4 Nov 2008 02:07:00 +0000
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
Cc: linux-pci@...r.kernel.org, kristen.c.accardi@...el.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add option to passively listen for PCIE hotplug events
On Tue, Nov 04, 2008 at 10:58:11AM +0900, Kenji Kaneshige wrote:
> - Even with pciehp_passive option, pciehp driver controls hotplug
> related registers at the initialization time, enabling software
> notification mechanism for hotplug events, trying to turn power
> on the slot and so on. Is this your intended behaviour?
Yes, although the most recent version of the patch doesn't do the
forcible power on if no card is detected.
> - Maybe I don't understand what "pciehp will listen for events..."
> in your patch description means. But if you expect the pciehp's
> interrupts for hotplug events, it would not work properly when
> hotplug control is not granted through _OSC or OSHP.
What do you mean by "not work properly"? The hardware we've tested with
fires events even without an OSHP method being present. That's the case
we're trying to deal with.
> > t_slot->hpc_ops->get_adapter_status(t_slot, &value); /* Check if
> > slot is occupied */
> >- if (value && pciehp_force) {
> >+ if (value && (pciehp_force || pciehp_passive)) {
> > rc = pciehp_enable_slot(t_slot);
> > if (rc) /* -ENODEV: shouldn't happen, but deal with it */
> > value = 0;
This code no longer runs in the pciehp_passive case. However, by the
looks of it it still does in the resume case - that probably wants
fixing.
--
Matthew Garrett | mjg59@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists