From: Sinan Kaya <okaya@codeaurora.org>
To: linux-pci@vger.kernel.org, timur@codeaurora.org,
alex.williamson@redhat.com
Cc: Sinan Kaya <okaya@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V12 2/5] PCI: add pci_bus_crs_visibility_pending() function to detect CRS response
Date: Wed, 23 Aug 2017 00:56:08 -0400 [thread overview]
Message-ID: <1503464171-6471-2-git-send-email-okaya@codeaurora.org> (raw)
In-Reply-To: <1503464171-6471-1-git-send-email-okaya@codeaurora.org>
We need a wrapper function to determine when a particular device is
returning Configuration Request Retry Status (CRS) response. This will only
happen if the root port supports CRS visibility.
Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
---
drivers/pci/pci.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
index 22e0617..7fa583a 100644
--- a/drivers/pci/pci.h
+++ b/drivers/pci/pci.h
@@ -235,6 +235,10 @@ enum pci_bar_type {
pci_bar_mem64, /* A 64-bit memory BAR */
};
+static inline bool pci_bus_crs_visibility_pending(u32 l)
+{
+ return (l & 0xffff) == 0x0001;
+}
bool pci_bus_read_dev_vendor_id(struct pci_bus *bus, int devfn, u32 *pl,
int crs_timeout);
int pci_setup_device(struct pci_dev *dev);
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Sinan Kaya <okaya@codeaurora.org>
To: linux-pci@vger.kernel.org, timur@codeaurora.org,
alex.williamson@redhat.com
Cc: Sinan Kaya <okaya@codeaurora.org>,
linux-arm-msm@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH V12 2/5] PCI: add pci_bus_crs_visibility_pending() function to detect CRS response
Date: Wed, 23 Aug 2017 00:56:08 -0400 [thread overview]
Message-ID: <1503464171-6471-2-git-send-email-okaya@codeaurora.org> (raw)
In-Reply-To: <1503464171-6471-1-git-send-email-okaya@codeaurora.org>
We need a wrapper function to determine when a particular device is
returning Configuration Request Retry Status (CRS) response. This will only
happen if the root port supports CRS visibility.
Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
---
drivers/pci/pci.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
index 22e0617..7fa583a 100644
--- a/drivers/pci/pci.h
+++ b/drivers/pci/pci.h
@@ -235,6 +235,10 @@ enum pci_bar_type {
pci_bar_mem64, /* A 64-bit memory BAR */
};
+static inline bool pci_bus_crs_visibility_pending(u32 l)
+{
+ return (l & 0xffff) == 0x0001;
+}
bool pci_bus_read_dev_vendor_id(struct pci_bus *bus, int devfn, u32 *pl,
int crs_timeout);
int pci_setup_device(struct pci_dev *dev);
--
1.9.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: okaya@codeaurora.org (Sinan Kaya)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V12 2/5] PCI: add pci_bus_crs_visibility_pending() function to detect CRS response
Date: Wed, 23 Aug 2017 00:56:08 -0400 [thread overview]
Message-ID: <1503464171-6471-2-git-send-email-okaya@codeaurora.org> (raw)
In-Reply-To: <1503464171-6471-1-git-send-email-okaya@codeaurora.org>
We need a wrapper function to determine when a particular device is
returning Configuration Request Retry Status (CRS) response. This will only
happen if the root port supports CRS visibility.
Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
---
drivers/pci/pci.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
index 22e0617..7fa583a 100644
--- a/drivers/pci/pci.h
+++ b/drivers/pci/pci.h
@@ -235,6 +235,10 @@ enum pci_bar_type {
pci_bar_mem64, /* A 64-bit memory BAR */
};
+static inline bool pci_bus_crs_visibility_pending(u32 l)
+{
+ return (l & 0xffff) == 0x0001;
+}
bool pci_bus_read_dev_vendor_id(struct pci_bus *bus, int devfn, u32 *pl,
int crs_timeout);
int pci_setup_device(struct pci_dev *dev);
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: Sinan Kaya <okaya@codeaurora.org>
To: linux-pci@vger.kernel.org, timur@codeaurora.org,
alex.williamson@redhat.com
Cc: linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Sinan Kaya <okaya@codeaurora.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH V12 2/5] PCI: add pci_bus_crs_visibility_pending() function to detect CRS response
Date: Wed, 23 Aug 2017 00:56:08 -0400 [thread overview]
Message-ID: <1503464171-6471-2-git-send-email-okaya@codeaurora.org> (raw)
In-Reply-To: <1503464171-6471-1-git-send-email-okaya@codeaurora.org>
We need a wrapper function to determine when a particular device is
returning Configuration Request Retry Status (CRS) response. This will only
happen if the root port supports CRS visibility.
Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
---
drivers/pci/pci.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
index 22e0617..7fa583a 100644
--- a/drivers/pci/pci.h
+++ b/drivers/pci/pci.h
@@ -235,6 +235,10 @@ enum pci_bar_type {
pci_bar_mem64, /* A 64-bit memory BAR */
};
+static inline bool pci_bus_crs_visibility_pending(u32 l)
+{
+ return (l & 0xffff) == 0x0001;
+}
bool pci_bus_read_dev_vendor_id(struct pci_bus *bus, int devfn, u32 *pl,
int crs_timeout);
int pci_setup_device(struct pci_dev *dev);
--
1.9.1
next prev parent reply other threads:[~2017-08-23 4:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 4:56 [PATCH V12 1/5] PCI: Don't ignore valid response before CRS timeout Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya [this message]
2017-08-23 4:56 ` [PATCH V12 2/5] PCI: add pci_bus_crs_visibility_pending() function to detect CRS response Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya
2017-08-23 4:56 ` [PATCH V12 3/5] PCI: Factor out pci_bus_wait_crs() Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya
2017-08-23 4:56 ` [PATCH V12 4/5] PCI: Handle CRS ("device not ready") returned by device after FLR Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya
2017-08-23 21:38 ` Bjorn Helgaas
2017-08-23 21:38 ` Bjorn Helgaas
2017-08-23 21:38 ` Bjorn Helgaas
2017-08-23 21:51 ` Sinan Kaya
2017-08-23 21:51 ` Sinan Kaya
2017-08-23 22:24 ` Bjorn Helgaas
2017-08-23 22:24 ` Bjorn Helgaas
2017-08-23 22:24 ` Bjorn Helgaas
2017-08-23 4:56 ` [PATCH V12 5/5] PCI: Warn periodically while waiting for device to become ready Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya
2017-08-23 4:56 ` Sinan Kaya
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=1503464171-6471-2-git-send-email-okaya@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=timur@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.