From: Oza Pawandeep <oza.oza@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Jon Mason <jonmason@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Oza Pawandeep <oza.oza@broadcom.com>,
Andy Gospodarek <gospo@broadcom.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Oza Pawandeep <oza.pawandeep@gmail.com>
Subject: [PATCH v4 0/2] PCI: iproc: SOC specific fixes
Date: Wed, 5 Jul 2017 08:38:57 +0530 [thread overview]
Message-ID: <1499224139-10746-1-git-send-email-oza.oza@broadcom.com> (raw)
PCI: iproc: Retry request when CRS returned from EP
Above patch adds support for CRS in PCI RC driver, otherwise if not
handled at lower level, the user space PMD (poll mode drivers) can
timeout.
PCI: iproc: add device shutdown for PCI RC
This fixes the issue where certian PCI endpoints are not getting
detected on Stingray SOC after reboot.
Changes Since v4:
Bjorn's comments addressed.
Changes Since v3:
[re-send]
Changes Since v2:
Fix compilation errors for pcie-iproc-platform.ko which was caught by
kbuild.
Oza Pawandeep (2):
PCI: iproc: Retry request when CRS returned from EP
PCI: iproc: add device shutdown for PCI RC
drivers/pci/host/pcie-iproc-platform.c | 8 ++
drivers/pci/host/pcie-iproc.c | 134 ++++++++++++++++++++++++++++-----
drivers/pci/host/pcie-iproc.h | 1 +
3 files changed, 124 insertions(+), 19 deletions(-)
--
1.9.1
next reply other threads:[~2017-07-05 3:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 3:08 Oza Pawandeep [this message]
2017-07-05 3:08 ` [PATCH v4 1/2] PCI: iproc: Retry request when CRS returned from EP Oza Pawandeep
2017-07-05 3:08 ` [PATCH v4 2/2] PCI: iproc: add device shutdown for PCI RC Oza Pawandeep
2017-07-05 3:51 ` Ray Jui
2017-07-05 8:37 ` Oza Oza
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=1499224139-10746-1-git-send-email-oza.oza@broadcom.com \
--to=oza.oza@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=gospo@broadcom.com \
--cc=jonmason@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=oza.pawandeep@gmail.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
/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
all inboxes | Powered by JetHome®