From: Dilip Kota <eswara.kota@linux.intel.com>
To: jingoohan1@gmail.com, gustavo.pimentel@synopsys.com,
lorenzo.pieralisi@arm.com, robh@kernel.org,
martin.blumenstingl@googlemail.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 v3 0/2] PCI: Add Intel PCIe Driver and respective dt-binding yaml file
Date: Wed, 4 Sep 2019 18:10:29 +0800 [thread overview]
Message-ID: <cover.1567585181.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.
Changes on v3:
Compared to v2, map_irq() patch is removed as it is no longer
required for Intel PCIe driver. Intel PCIe driver does platform
specific interrupt configuration during core initialization. So
changed the subject line too.
Address v2 review comments for DT binding and PCIe driver
Dilip Kota (2):
dt-bindings: PCI: intel: Add YAML schemas for the PCIe RC controller
dwc: PCI: intel: Intel PCIe RC controller driver
.../devicetree/bindings/pci/intel,lgm-pcie.yaml | 137 ++++
drivers/pci/controller/dwc/Kconfig | 13 +
drivers/pci/controller/dwc/Makefile | 1 +
drivers/pci/controller/dwc/pcie-intel-axi.c | 840 +++++++++++++++++++++
4 files changed, 991 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pci/intel,lgm-pcie.yaml
create mode 100644 drivers/pci/controller/dwc/pcie-intel-axi.c
--
2.11.0
next reply other threads:[~2019-09-04 10:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 10:10 Dilip Kota [this message]
2019-09-04 10:10 ` [PATCH v3 1/2] dt-bindings: PCI: intel: Add YAML schemas for the PCIe RC controller Dilip Kota
2019-09-05 2:23 ` Chuan Hua, Lei
2019-09-06 10:39 ` Dilip Kota
2019-09-05 20:31 ` Martin Blumenstingl
2019-09-06 3:22 ` Chuan Hua, Lei
2019-09-06 17:17 ` Martin Blumenstingl
2019-09-06 17:48 ` Andy Shevchenko
2019-09-07 1:48 ` Ivan Gorinov
2019-09-06 9:19 ` Andy Shevchenko
2019-09-09 6:52 ` Dilip Kota
2019-09-17 18:33 ` Rob Herring
2019-09-18 6:48 ` Dilip Kota
2019-09-17 18:40 ` Rob Herring
2019-09-18 6:56 ` Dilip Kota
[not found] ` <b7e549bb-b46c-c393-50ac-9ef3b198fd49@linux.intel.com>
2019-10-03 6:35 ` Fwd: " Dilip Kota
2019-09-04 10:10 ` [PATCH v3 2/2] dwc: PCI: intel: Intel PCIe RC controller driver Dilip Kota
2019-09-04 13:05 ` Andy Shevchenko
2019-09-06 10:39 ` Dilip Kota
2019-09-05 2:30 ` Chuan Hua, Lei
2019-09-05 10:45 ` Andrew Murray
2019-09-05 11:26 ` Christoph Hellwig
2019-09-05 11:40 ` Andy Shevchenko
2019-09-12 7:01 ` Dilip Kota
2019-09-06 10:58 ` Dilip Kota
2019-09-06 11:20 ` Andrew Murray
2019-09-09 6:51 ` Dilip Kota
2019-09-09 8:31 ` Andrew Murray
2019-09-10 8:08 ` Dilip Kota
[not found] ` <22857835-1f98-b251-c94b-16b4b0a6dba2@linux.intel.com>
2019-09-11 10:30 ` Andrew Murray
2019-09-12 6:58 ` Dilip Kota
2019-09-12 8:25 ` Andrew Murray
2019-09-12 9:23 ` Dilip Kota
2019-09-12 10:49 ` Gustavo Pimentel
2019-09-13 9:20 ` Dilip Kota
2019-09-13 10:12 ` andriy.shevchenko
2019-09-16 3:03 ` Dilip Kota
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.1567585181.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=lorenzo.pieralisi@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=qi-ming.wu@intel.com \
--cc=robh@kernel.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 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).