linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Vidya Sagar <vidyas@nvidia.com>,
	bhelgaas@google.com, robh+dt@kernel.org, jonathanh@nvidia.com,
	andrew.murray@arm.com, kishon@ti.com,
	gustavo.pimentel@synopsys.com, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, kthota@nvidia.com,
	mmaddireddy@nvidia.com, sagar.tv@gmail.com
Subject: Re: [PATCH V4 0/5] Add support for PCIe endpoint mode in Tegra194
Date: Tue, 3 Mar 2020 15:02:09 +0000	[thread overview]
Message-ID: <20200303150209.GA6334@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200303134053.GC2854899@ulmo>

On Tue, Mar 03, 2020 at 02:40:53PM +0100, Thierry Reding wrote:
> On Tue, Mar 03, 2020 at 04:24:13PM +0530, Vidya Sagar wrote:
> > Tegra194 has three (C0, C4 & C5) dual mode PCIe controllers that can operate
> > either in root port mode or in end point mode but only in one mode at a time.
> > Platform P2972-0000 supports enabling endpoint mode for C5 controller. This
> > patch series adds support for PCIe endpoint mode in both the driver as well as
> > in DT.
> > This patch series depends on the changes made for Synopsys DesignWare endpoint
> > mode subsystem that are recently accepted.
> > @ https://patchwork.kernel.org/project/linux-pci/list/?series=202211
> > which in turn depends on the patch made by Kishon
> > @ https://patchwork.kernel.org/patch/10975123/
> > which is also under review.
> > 
> > V4:
> > * Started using threaded irqs instead of kthreads
> > 
> > V3:
> > * Re-ordered patches in the series to make the driver change as the last patch
> > * Took care of Thierry's review comments
> > 
> > V2:
> > * Addressed Thierry & Bjorn's review comments
> > * Added EP mode specific binding documentation to already existing binding documentation file
> > * Removed patch that enables GPIO controller nodes explicitly as they are enabled already
> > 
> > Vidya Sagar (5):
> >   soc/tegra: bpmp: Update ABI header
> >   dt-bindings: PCI: tegra: Add DT support for PCIe EP nodes in Tegra194
> >   arm64: tegra: Add PCIe endpoint controllers nodes for Tegra194
> >   arm64: tegra: Add support for PCIe endpoint mode in P2972-0000
> >     platform
> >   PCI: tegra: Add support for PCIe endpoint mode in Tegra194
> 
> Hi Lorenzo,
> 
> I've acked patches 1, 2 and 5 of the series. I think you're going to
> need to apply patch 1 in order to satisfy a build-time dependency from
> patch 5. I can apply patches 3 and 4 to the Tegra tree since they're
> only adding device tree content that may conflict with some other
> patches that I have in the Tegra tree.
> 
> Does that sound reasonable?

Sure, that's absolutely fine by me, I will do.

Thanks,
Lorenzo

  reply	other threads:[~2020-03-03 15:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 10:54 [PATCH V4 0/5] Add support for PCIe endpoint mode in Tegra194 Vidya Sagar
2020-03-03 10:54 ` [PATCH V4 1/5] soc/tegra: bpmp: Update ABI header Vidya Sagar
2020-03-03 10:54 ` [PATCH V4 2/5] dt-bindings: PCI: tegra: Add DT support for PCIe EP nodes in Tegra194 Vidya Sagar
2020-03-03 13:39   ` Thierry Reding
2020-03-03 10:54 ` [PATCH V4 3/5] arm64: tegra: Add PCIe endpoint controllers nodes for Tegra194 Vidya Sagar
2020-03-03 10:54 ` [PATCH V4 4/5] arm64: tegra: Add support for PCIe endpoint mode in P2972-0000 platform Vidya Sagar
2020-03-03 10:54 ` [PATCH V4 5/5] PCI: tegra: Add support for PCIe endpoint mode in Tegra194 Vidya Sagar
2020-03-03 13:38   ` Thierry Reding
2020-03-03 13:40 ` [PATCH V4 0/5] " Thierry Reding
2020-03-03 15:02   ` Lorenzo Pieralisi [this message]
2020-03-03 17:01 ` Lorenzo Pieralisi
2020-03-03 18:13   ` Vidya Sagar
2020-03-10 17:42     ` Vidya Sagar
2020-03-10 17:58       ` Lorenzo Pieralisi

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=20200303150209.GA6334@e121166-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=andrew.murray@arm.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=jonathanh@nvidia.com \
    --cc=kishon@ti.com \
    --cc=kthota@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mmaddireddy@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=sagar.tv@gmail.com \
    --cc=thierry.reding@gmail.com \
    --cc=vidyas@nvidia.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).