From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: linux-pci@vger.kernel.org, kristen.c.accardi@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add option to passively listen for PCIE hotplug events
Date: Tue, 4 Nov 2008 02:07:00 +0000 [thread overview]
Message-ID: <20081104020700.GA11761@srcf.ucam.org> (raw)
In-Reply-To: <490FAC33.9050808@jp.fujitsu.com>
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@srcf.ucam.org
next prev parent reply other threads:[~2008-11-04 2:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 20:09 [PATCH] Add option to passively listen for PCIE hotplug events Matthew Garrett
2008-11-01 17:51 ` Grant Grundler
2008-11-03 13:26 ` [PATCH v2] " Matthew Garrett
2008-11-03 13:43 ` Fabio Comolli
2008-11-03 13:46 ` Matthew Garrett
2008-11-14 16:56 ` Randy Dunlap
2008-11-14 17:00 ` Matthew Garrett
2008-11-03 22:23 ` [PATCH] " Andrew Morton
2008-11-03 22:30 ` Matthew Garrett
2008-11-04 1:58 ` Kenji Kaneshige
2008-11-04 2:07 ` Matthew Garrett [this message]
2008-11-04 2:29 ` Kenji Kaneshige
2008-11-04 2:38 ` Matthew Garrett
2008-11-04 3:11 ` Kenji Kaneshige
2008-11-04 5:02 ` Matthew Garrett
2008-11-04 5:46 ` Kenji Kaneshige
2008-11-04 12:45 ` Matthew Garrett
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=20081104020700.GA11761@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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