From: Oza Pawandeep <oza.oza@broadcom.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
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, linux-kernel@vger.kernel.org,
Oza Pawandeep <oza.pawandeep@gmail.com>
Subject: [PATCH 0/2] PCI hotplug feature
Date: Tue, 8 Aug 2017 10:14:13 +0530 [thread overview]
Message-ID: <1502167455-10516-1-git-send-email-oza.oza@broadcom.com> (raw)
These patches bring in PCI hotplug support for iproc family chipsets.
It includes DT binding documentation update and, implementation in
iproc pcie RC driver.
These patch set is made on top of following patches.
[PATCH v6 2/2] PCI: iproc: add device shutdown for PCI RC
[PATCH v6 1/2] PCI: iproc: Retry request when CRS returned from EP
Oza Pawandeep (2):
PCI: iproc: Implement PCI hotplug support
PCI: iproc: Add optional brcm,pci-hotplug
.../devicetree/bindings/pci/brcm,iproc-pcie.txt | 23 ++++
drivers/pci/host/pcie-iproc-platform.c | 3 +
drivers/pci/host/pcie-iproc.c | 130 ++++++++++++++++++++-
drivers/pci/host/pcie-iproc.h | 7 ++
4 files changed, 157 insertions(+), 6 deletions(-)
--
1.9.1
next reply other threads:[~2017-08-08 4:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 4:44 Oza Pawandeep [this message]
2017-08-08 4:44 ` [PATCH 1/2] PCI: iproc: Implement PCI hotplug support Oza Pawandeep
2017-08-08 4:44 ` [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug Oza Pawandeep
2017-08-08 14:20 ` Rob Herring
2017-08-09 5:22 ` Oza Oza
2017-08-09 5:27 ` Ray Jui
2017-08-09 5:43 ` Oza Oza
2017-08-09 5:52 ` Oza Oza
2017-08-10 18:00 ` Rob Herring
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=1502167455-10516-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=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).