From: Alex Williamson <alex.williamson@redhat.com>
To: bhelgaas@google.com, linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH v2] pci: Disable slot presence detection around bus reset
Date: Fri, 15 Feb 2013 12:22:56 -0700 [thread overview]
Message-ID: <20130215191944.27692.8935.stgit@bling.home> (raw)
A bus reset can trigger a presence detection change and result in a
suprise hotplug. This is generally not what we want to happen when
trying to reset a device. Disable the presence detection control on
on bridges around bus reset.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
v2: Still hasn't resolved any controversy of this patch, but writing the
presence detect changed bit to the slot status to clear it resolves
the stray remove/add I was still seeing occasionally on v1.
drivers/pci/pci.c | 32 +++++++++++++++++++++++++++-----
1 file changed, 27 insertions(+), 5 deletions(-)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 5cb5820..efccc97 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -3229,8 +3229,8 @@ static int pci_pm_reset(struct pci_dev *dev, int probe)
static int pci_parent_bus_reset(struct pci_dev *dev, int probe)
{
- u16 ctrl;
- struct pci_dev *pdev;
+ u16 ctrl, flags, sltctl = 0;
+ struct pci_dev *pdev, *bridge;
if (pci_is_root_bus(dev->bus) || dev->subordinate || !dev->bus->self)
return -ENOTTY;
@@ -3242,15 +3242,37 @@ static int pci_parent_bus_reset(struct pci_dev *dev, int probe)
if (probe)
return 0;
- pci_read_config_word(dev->bus->self, PCI_BRIDGE_CONTROL, &ctrl);
+ bridge = dev->bus->self;
+
+ /*
+ * If the parent device supports a slot with presence detection
+ * change enabled, holding the bus in reset can trigger that and
+ * cause an unwanted surprise removal. Disable presence detection
+ * around the bus reset.
+ */
+ pcie_capability_read_word(bridge, PCI_EXP_FLAGS, &flags);
+ if (flags & PCI_EXP_FLAGS_SLOT) {
+ pcie_capability_read_word(bridge, PCI_EXP_SLTCTL, &sltctl);
+ if (sltctl & PCI_EXP_SLTCTL_PDCE)
+ pcie_capability_write_word(bridge, PCI_EXP_SLTCTL,
+ sltctl & ~PCI_EXP_SLTCTL_PDCE);
+ }
+
+ pci_read_config_word(bridge, PCI_BRIDGE_CONTROL, &ctrl);
ctrl |= PCI_BRIDGE_CTL_BUS_RESET;
- pci_write_config_word(dev->bus->self, PCI_BRIDGE_CONTROL, ctrl);
+ pci_write_config_word(bridge, PCI_BRIDGE_CONTROL, ctrl);
msleep(100);
ctrl &= ~PCI_BRIDGE_CTL_BUS_RESET;
- pci_write_config_word(dev->bus->self, PCI_BRIDGE_CONTROL, ctrl);
+ pci_write_config_word(bridge, PCI_BRIDGE_CONTROL, ctrl);
msleep(100);
+ if (sltctl & PCI_EXP_SLTCTL_PDCE) {
+ pcie_capability_write_word(bridge,
+ PCI_EXP_SLTSTA, PCI_EXP_SLTSTA_PDC);
+ pcie_capability_write_word(bridge, PCI_EXP_SLTCTL, sltctl);
+ }
+
return 0;
}
reply other threads:[~2013-02-15 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130215191944.27692.8935.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.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