From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Dilip Kota <eswara.kota@linux.intel.com>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
andriy.shevchenko@intel.com, gustavo.pimentel@synopsys.com,
andrew.murray@arm.com, robh@kernel.org,
linux-kernel@vger.kernel.org, cheol.yong.kim@intel.com,
chuanhua.lei@linux.intel.com, qi-ming.wu@intel.com
Subject: Re: [PATCH v10 0/3] PCI: Add Intel PCIe Driver and respective dt-binding yaml file
Date: Fri, 6 Dec 2019 10:51:55 +0000 [thread overview]
Message-ID: <20191206105155.GA20804@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <cover.1575612493.git.eswara.kota@linux.intel.com>
On Fri, Dec 06, 2019 at 03:27:47PM +0800, Dilip Kota wrote:
> Intel PCIe is Synopsys based controller. Intel PCIe driver uses
> DesignWare PCIe framework for host initialization and register
> configurations.
>
> Changes on v10:
> Rebase the patches on mainline v5.4
I meant current mainline (given that the PCI PR for v5.5 is now
merged), not v5.4, patchset does not apply. Given that v5.5-rc1
is coming up, please rebase on top of v5.5-rc1 and repost it I
will try to merge it then.
Thanks,
Lorenzo
> Squashed the patch that fixes the below issue to this patch series.
>
> WARNING: unmet direct dependencies detected for PCIE_DW_HOST
> Depends on [n]: PCI [=y] && PCI_MSI_IRQ_DOMAIN [=n]
> Selected by [y]:
> - PCIE_INTEL_GW [=y] && PCI [=y] && OF [=y] && (X86 [=y] || COMPILE_TEST [=n])
> "reportedby Randy Dunlap <rdunlap@infradead.org>"
>
> Dilip Kota (3):
> dt-bindings: PCI: intel: Add YAML schemas for the PCIe RC controller
> PCI: dwc: intel: PCIe RC controller driver
> PCI: artpec6: Configure FTS with dwc helper function
>
> .../devicetree/bindings/pci/intel-gw-pcie.yaml | 138 ++++++
> drivers/pci/controller/dwc/Kconfig | 11 +
> drivers/pci/controller/dwc/Makefile | 1 +
> drivers/pci/controller/dwc/pcie-artpec6.c | 8 +-
> drivers/pci/controller/dwc/pcie-designware.c | 57 +++
> drivers/pci/controller/dwc/pcie-designware.h | 12 +
> drivers/pci/controller/dwc/pcie-intel-gw.c | 545 +++++++++++++++++++++
> include/uapi/linux/pci_regs.h | 1 +
> 8 files changed, 766 insertions(+), 7 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/pci/intel-gw-pcie.yaml
> create mode 100644 drivers/pci/controller/dwc/pcie-intel-gw.c
>
> --
> 2.11.0
>
prev parent reply other threads:[~2019-12-06 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 7:27 [PATCH v10 0/3] PCI: Add Intel PCIe Driver and respective dt-binding yaml file Dilip Kota
2019-12-06 7:27 ` [PATCH v10 1/3] dt-bindings: PCI: intel: Add YAML schemas for the PCIe RC controller Dilip Kota
2019-12-06 7:27 ` [PATCH v10 2/3] PCI: dwc: intel: PCIe RC controller driver Dilip Kota
2019-12-10 23:49 ` Bjorn Helgaas
2019-12-11 9:59 ` Dilip Kota
2019-12-11 14:20 ` Bjorn Helgaas
2019-12-11 23:46 ` Andrew Murray
2019-12-06 7:27 ` [PATCH v10 3/3] PCI: artpec6: Configure FTS with dwc helper function Dilip Kota
2019-12-06 10:51 ` Lorenzo Pieralisi [this message]
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=20191206105155.GA20804@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=andrew.murray@arm.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=chuanhua.lei@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=eswara.kota@linux.intel.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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).