LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>
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, 04 Nov 2008 12:11:10 +0900 [thread overview]
Message-ID: <490FBD4E.2040308@jp.fujitsu.com> (raw)
In-Reply-To: <20081104023837.GA12165@srcf.ucam.org>
Matthew Garrett wrote:
> On Tue, Nov 04, 2008 at 11:29:43AM +0900, Kenji Kaneshige wrote:
>> Matthew Garrett wrote:
>>> 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.
>>>
>> Because the explanation of PCI Express Native Hot Plug control bit in
>> _OSC return value in PCI firmware spec says
>>
>> "... If firmware allows the operating system control of this feature,
>> then in the context of the _OSC method, it must ensure that all hot
>> plug events are routed to device interrupts as described in the PCI
>> Express Base Specification. ..."
>>
>> My understanding is that it is not ensured that all hot plug events
>> are routed to device interrupts, if hotplug control is not granted.
>
> My understanding is that in the worst case the hardware/firmware won't
> give us any events - that's basically equivalent to not having the
> driver loaded at all. On hardware that gives us the events anyway, we
> get some extra functionality.
>
> Thanks for the feedback!
Ok, I understood that my worries are already within the scope of the
assumption.
Thanks,
Kenji Kaneshige
next prev parent reply other threads:[~2008-11-04 3:13 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
2008-11-04 2:29 ` Kenji Kaneshige
2008-11-04 2:38 ` Matthew Garrett
2008-11-04 3:11 ` Kenji Kaneshige [this message]
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=490FBD4E.2040308@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).