From: Rajat Jain <rajatjain.linux@gmail.com>
To: linux-pci@vger.kernel.org, linux-hotplug@vger.kernel.org
Subject: pciehp & other hot-plug drivers (shpc etc..)
Date: Sun, 29 Sep 2013 18:27:23 +0000 [thread overview]
Message-ID: <CADTPrLTuzvj3iSMdNVs2BjDFHsWqjRPM4qDkkpmv+P11LMP0JQ@mail.gmail.com> (raw)
Hello List,
Today all the PCI Hot-plug drivers (shpc, acpihp, cpqhp, ibmhp etc
except pciedhp) directly claim the downstream port bridge device.
Where as in case of pciehp, the PCIe port bus driver claims the bridge
device, and service drivers (aer, pm, pciehp) simply register for the
service with it.
1) Does that mean that in a system where I am using a driver other
than pciehp for hot-plug (eg. shpc), I cannot use service drivers like
AER or PM on the same port (since the device would be claimed by
shpc, it would not be available to port bus driver)?
2) In the same system, can I use SHPC on one port, and pciehp on
another port? I believe not?
Please note that it may not be a realistic scenarios, my intent of
asking is to just understand how things are intended to behave.
Thanks,
Rajat
next reply other threads:[~2013-09-29 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 18:27 Rajat Jain [this message]
2013-09-30 2:05 ` pciehp & other hot-plug drivers (shpc etc..) Greg KH
2013-10-04 1:08 ` Rajat Jain
2013-10-04 23:01 ` Bjorn Helgaas
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=CADTPrLTuzvj3iSMdNVs2BjDFHsWqjRPM4qDkkpmv+P11LMP0JQ@mail.gmail.com \
--to=rajatjain.linux@gmail.com \
--cc=linux-hotplug@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).