From: Dilip Kota <eswara.kota@linux.intel.com>
To: jingoohan1@gmail.com, gustavo.pimentel@synopsys.com,
linux-pci@vger.kernel.org, hch@infradead.org,
devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, andriy.shevchenko@intel.com,
cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com,
qi-ming.wu@intel.com, Dilip Kota <eswara.kota@linux.intel.com>
Subject: [PATCH v2 0/3] PCI: Add map irq callback in dwc framework and add Intel PCIe driver
Date: Tue, 20 Aug 2019 17:39:34 +0800 [thread overview]
Message-ID: <cover.1566208109.git.eswara.kota@linux.intel.com> (raw)
Intel PCIe is synopsys based controller utilizes the Designware
framework for host initialization and intel application
specific register configurations.
Intel PCIe driver also uses the Irq map callback for platform
specific register configurations while Irq mapping. So submitting
the Intel pcie driver series with dwc irq map callback change.
Changes on v2:
Submitting user(intel pcie driver) changes along with core changes.
Dilip Kota (3):
PCI: dwc: Add map irq callback
dt-bindings: PCI: intel: Add YAML schemas for the PCIe RC controller
dwc: PCI: intel: Intel PCIe RC controller driver
.../devicetree/bindings/pci/intel-pcie.yaml | 133 +++
drivers/pci/controller/dwc/Kconfig | 13 +
drivers/pci/controller/dwc/Makefile | 1 +
drivers/pci/controller/dwc/pcie-designware-host.c | 6 +-
drivers/pci/controller/dwc/pcie-designware.h | 1 +
drivers/pci/controller/dwc/pcie-intel-axi.c | 900 +++++++++++++++++
6 files changed, 1053 insertions(+), 1 deletion(-)
create mode 100644 Documentation/devicetree/bindings/pci/intel-pcie.yaml
create mode 100644 drivers/pci/controller/dwc/pcie-intel-axi.c
--
2.11.0
next reply other threads:[~2019-08-20 9:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 9:39 Dilip Kota [this message]
2019-08-20 9:39 ` [PATCH v2 1/3] PCI: dwc: Add map irq callback Dilip Kota
2019-08-20 9:39 ` [PATCH v2 2/3] dt-bindings: PCI: intel: Add YAML schemas for the PCIe RC controller Dilip Kota
2019-08-20 13:42 ` Rob Herring
2019-08-21 9:56 ` Dilip Kota
2019-08-20 9:39 ` [PATCH v2 3/3] dwc: PCI: intel: Intel PCIe RC controller driver Dilip Kota
2019-08-24 21:03 ` Martin Blumenstingl
2019-08-26 3:30 ` Chuan Hua, Lei
2019-08-26 6:48 ` Dilip Kota
[not found] ` <f1cb5ba9-b57a-971a-5a2f-1f13e0cc9507@linux.intel.com>
2019-08-26 20:14 ` Martin Blumenstingl
2019-08-27 9:14 ` Dilip Kota
2019-08-26 21:15 ` Martin Blumenstingl
2019-08-27 3:09 ` Chuan Hua, Lei
2019-08-27 8:47 ` Dilip Kota
2019-08-27 20:51 ` Martin Blumenstingl
2019-08-27 20:38 ` Martin Blumenstingl
2019-08-28 3:35 ` Chuan Hua, Lei
2019-08-28 19:36 ` Martin Blumenstingl
2019-08-29 2:54 ` Chuan Hua, Lei
[not found] ` <4bab775a-0e39-a187-0791-40050feb7d67@linux.intel.com>
2019-09-03 18:36 ` Martin Blumenstingl
2019-08-29 5:10 ` Kishon Vijay Abraham I
2019-08-29 21:01 ` Martin Blumenstingl
2019-08-27 14:28 ` Andy Shevchenko
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=cover.1566208109.git.eswara.kota@linux.intel.com \
--to=eswara.kota@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=hch@infradead.org \
--cc=jingoohan1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=qi-ming.wu@intel.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).