From: Oza Pawandeep <oza.oza@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
helgaas@kernel.org, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.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, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Oza Pawandeep <oza.pawandeep@gmail.com>
Subject: [PATCH v8 0/3] PCI: iproc: SOC specific fixes
Date: Thu, 24 Aug 2017 10:34:23 +0530 [thread overview]
Message-ID: <1503551066-23212-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 v7:
Factor out the ep config access code.
Changes Since v6:
Rebased patches on top of Lorenzo's patches.
Bjorn's comments addressed.
now the confg retry returns 0xffffffff as data.
Added reference to PCIe spec and iproc Controller spec in Changelog.
Changes Since v5:
Ray's comments addressed.
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 (3):
PCI: iproc: factor-out ep configuration access
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 | 143 ++++++++++++++++++++++++++-------
drivers/pci/host/pcie-iproc.h | 1 +
3 files changed, 124 insertions(+), 28 deletions(-)
--
1.9.1
next reply other threads:[~2017-08-24 5:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 5:04 Oza Pawandeep [this message]
2017-08-24 5:04 ` [PATCH v8 1/3] PCI: iproc: factor out ep configuration access Oza Pawandeep
2017-08-24 5:04 ` [PATCH v8 2/3] PCI: iproc: retry request when CRS returned from EP Oza Pawandeep
[not found] ` <1503551066-23212-3-git-send-email-oza.oza-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2017-08-28 19:17 ` Bjorn Helgaas
2017-08-28 19:39 ` Oza Oza
2017-08-28 19:54 ` Bjorn Helgaas
2017-08-28 20:45 ` Oza Oza
2017-08-28 21:47 ` Bjorn Helgaas
2017-08-29 5:32 ` Oza Oza
2017-08-29 20:02 ` Bjorn Helgaas
2017-08-30 9:18 ` Oza Oza
2017-08-24 5:04 ` [PATCH v8 3/3] PCI: iproc: add device shutdown for PCI RC Oza Pawandeep
2017-08-28 21:53 ` [PATCH v8 0/3] PCI: iproc: SOC specific fixes Bjorn Helgaas
[not found] ` <20170828215309.GM8154-1RhO1Y9PlrlHTL0Zs8A6p5iNqAH0jzoTYJqu5kTmcBRl57MIdRCFDg@public.gmane.org>
2017-08-29 5:25 ` 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=1503551066-23212-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=devicetree@vger.kernel.org \
--cc=gospo@broadcom.com \
--cc=helgaas@kernel.org \
--cc=jonmason@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oza.pawandeep@gmail.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).