From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: mpe@ellerman.id.au, hankmax0000@gmail.com,
williel@supermicro.com.tw, Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH 0/3] powerpc/powernv: PCI hotplug fixes and improvement
Date: Wed, 11 Jan 2017 11:50:05 +1100 [thread overview]
Message-ID: <1484095808-24777-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
This series fixes couple issues or improves its reliability:
* The PDC event is never detected inside the IRQ handler in surprise
hot-add path.
* The slot's initial state should be REGISTERED state if it's emtpy.
Otherwise, the PCI devices behind the slot won't be populated properly
in hot-add path.
* PDC isn't reliable for hot-add on some machines. Introduce another
device-tree property to disable it if required by (skiboot) firmware.
Gavin Shan (3):
drivers/pci/hotplug: Handle presence detection change properly
drivers/pci/hotplug: Fix initial state for empty slot
drivers/pci/hotplug: Mask PDC interrupt if required
arch/powerpc/include/asm/pnv-pci.h | 2 ++
drivers/pci/hotplug/pnv_php.c | 49 +++++++++++++++++++++++++++++++-------
2 files changed, 43 insertions(+), 8 deletions(-)
--
2.7.4
next reply other threads:[~2017-01-11 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 0:50 Gavin Shan [this message]
2017-01-11 0:50 ` [PATCH 1/3] drivers/pci/hotplug: Handle presence detection change properly Gavin Shan
2017-02-16 5:59 ` [1/3] " Michael Ellerman
2017-01-11 0:50 ` [PATCH 2/3] drivers/pci/hotplug: Fix initial state for empty slot Gavin Shan
2017-01-11 0:50 ` [PATCH 3/3] drivers/pci/hotplug: Mask PDC interrupt if required Gavin Shan
2017-01-31 5:42 ` [PATCH 0/3] powerpc/powernv: PCI hotplug fixes and improvement Gavin Shan
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=1484095808-24777-1-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=hankmax0000@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=williel@supermicro.com.tw \
/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).