From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [PATCH v3 0/3] powerpc/powernv: Unified PCI slot reset
Date: Tue, 24 Mar 2015 11:39:39 +1100 [thread overview]
Message-ID: <1427157582-11196-1-git-send-email-gwshan@linux.vnet.ibm.com> (raw)
The patches intend to utilize the PCI slot reset capability exposed from
the skiboot firmware, which requires corresponding changes as follows:
Changelog
=========
v2 -> v3
* Rebased to Richard's SRIOV patchset.
* Removed hotplug part, which needs rework.
v1 -> v2
* Keep opal_pci_reinit(). In case the slot is resetted by kernel,
instead of skiboot, this API should be called to restore states
for those affected devices.
* Reworked slot ID scheme so that old/new kernel can work with
skiboot with or without unified PCI slot management support.
* Code cleanup here and there.
* Separate powernv-php driver to support PCI hotplug for
PowerNV platform.
* Check if the OPAL API supported by firmware before calling
into it, which is necessary for back-compability.
* Separate patch for factoring pnv_pci_poll().
Gavin Shan (3):
powerpc/powernv: Use PCI slot reset infrastructure
powerpc/powernv: Fundamental reset for PCI bus reset
powerpc/pci: Don't scan empty slot
arch/powerpc/include/asm/eeh.h | 1 +
arch/powerpc/include/asm/opal.h | 4 +-
arch/powerpc/kernel/pci-hotplug.c | 3 +-
arch/powerpc/platforms/powernv/eeh-powernv.c | 235 ++++++++++++++-------------
4 files changed, 127 insertions(+), 116 deletions(-)
--
1.8.3.2
next reply other threads:[~2015-03-24 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 0:39 Gavin Shan [this message]
2015-03-24 0:39 ` [PATCH v3 1/3] powerpc/powernv: Use PCI slot reset infrastructure Gavin Shan
2015-03-24 0:39 ` [PATCH v3 2/3] powerpc/powernv: Fundamental reset for PCI bus reset Gavin Shan
2015-03-24 0:39 ` [PATCH v3 3/3] powerpc/pci: Don't scan empty slot 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=1427157582-11196-1-git-send-email-gwshan@linux.vnet.ibm.com \
--to=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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).