From: Alex Williamson <alex.williamson@redhat.com>
To: bhelgaas@google.com, linux-pci@vger.kernel.org
Cc: ddutile@redhat.com, indou.takao@jp.fujitsu.com,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 2/9] pci: Add hotplug_slot_ops.reset_slot()
Date: Mon, 05 Aug 2013 13:37:16 -0600 [thread overview]
Message-ID: <20130805193715.9260.21461.stgit@bling.home> (raw)
In-Reply-To: <20130805193200.9260.38729.stgit@bling.home>
This optional callback allows htoplug controllers to perform slot
specific resets. These may be necessary in cases where a normal
secondary bus reset can interact with controller logic and expose
spurious hotplugs.
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
---
include/linux/pci_hotplug.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/include/linux/pci_hotplug.h b/include/linux/pci_hotplug.h
index 8db71dc..bd32109 100644
--- a/include/linux/pci_hotplug.h
+++ b/include/linux/pci_hotplug.h
@@ -63,6 +63,9 @@ enum pcie_link_width {
* @get_adapter_status: Called to get see if an adapter is present in the slot or not.
* If this field is NULL, the value passed in the struct hotplug_slot_info
* will be used when this value is requested by a user.
+ * @reset_slot: Optional interface to allow override of a bus reset for the
+ * slot for cases where a secondary bus reset can result in spurious
+ * hotplug events or where a slot can be reset independent of the bus.
*
* The table of function pointers that is passed to the hotplug pci core by a
* hotplug pci driver. These functions are called by the hotplug pci core when
@@ -80,6 +83,7 @@ struct hotplug_slot_ops {
int (*get_attention_status) (struct hotplug_slot *slot, u8 *value);
int (*get_latch_status) (struct hotplug_slot *slot, u8 *value);
int (*get_adapter_status) (struct hotplug_slot *slot, u8 *value);
+ int (*reset_slot) (struct hotplug_slot *slot, int probe);
};
/**
next prev parent reply other threads:[~2013-08-05 19:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 19:37 [PATCH v4 0/9] pci: bus and slot reset interfaces Alex Williamson
2013-08-05 19:37 ` [PATCH v4 1/9] pci: Create pci_reset_bridge_secondary_bus() Alex Williamson
2013-08-05 19:37 ` Alex Williamson [this message]
2013-08-05 19:37 ` [PATCH v4 3/9] pci: Implement reset_slot for pciehp Alex Williamson
2013-08-05 19:37 ` [PATCH v4 4/9] pci: Add slot reset option to pci_dev_reset Alex Williamson
2013-08-05 19:37 ` [PATCH v4 5/9] pci: Split out pci_dev lock/unlock and save/restore Alex Williamson
2013-08-05 19:37 ` [PATCH v4 6/9] pci: Add slot and bus reset interfaces Alex Williamson
2013-08-05 19:37 ` [PATCH v4 7/9] pci: Wake-up devices before save for reset Alex Williamson
2013-08-05 19:37 ` [PATCH v4 8/9] pci: Tune secondary bus reset timing Alex Williamson
2013-08-06 23:27 ` Alexander Duyck
2013-08-07 2:56 ` Alex Williamson
2013-08-07 18:30 ` Alexander Duyck
2013-08-08 5:23 ` Alex Williamson
2013-08-08 16:46 ` Alexander Duyck
2013-08-08 18:42 ` Alex Williamson
2013-08-05 19:37 ` [PATCH v4 9/9] pci: Remove aer_do_secondary_bus_reset() Alex Williamson
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=20130805193715.9260.21461.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=indou.takao@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).