linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: "Zhi Li" <lznuaa@gmail.com>, "Vinod Koul" <vkoul@kernel.org>,
	"Frank Li" <Frank.Li@nxp.com>,
	"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
	hongxing.zhu@nxp.com, "Lucas Stach" <l.stach@pengutronix.de>,
	dl-linux-imx <linux-imx@nxp.com>,
	linux-pci@vger.kernel.org, dmaengine@vger.kernel.org,
	"Kishon Vijay Abraham I" <kishon@ti.com>,
	"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Serge Semin" <Sergey.Semin@baikalelectronics.ru>
Subject: Re: [PATCH v11 0/8] Enable designware PCI EP EDMA locally
Date: Tue, 24 May 2022 10:52:01 -0500	[thread overview]
Message-ID: <20220524155201.GA247821@bhelgaas> (raw)
In-Reply-To: <20220524054850.vrchh6icwfriszhn@mobilestation>

On Tue, May 24, 2022 at 08:48:50AM +0300, Serge Semin wrote:
> On Mon, May 23, 2022 at 05:12:56PM -0500, Bjorn Helgaas wrote:
> > On Mon, May 23, 2022 at 01:41:48PM -0500, Zhi Li wrote:
> > > On Mon, May 23, 2022 at 1:02 PM Bjorn Helgaas <helgaas@kernel.org> wrote:
> > > > On Mon, May 23, 2022 at 02:06:47PM +0300, Serge Semin wrote:
> > > > > Hello Vinod,
> > > > >
> > > > > On Tue, May 17, 2022 at 10:19:07AM -0500, Frank Li wrote:
> > > > > > Default Designware EDMA just probe remotely at host side.
> > > > > > This patch allow EDMA driver can probe at EP side.
> > > > > >
> > > > > > 1. Clean up patch
> > > > > >    dmaengine: dw-edma: Detach the private data and chip info structures
> > > > > >    dmaengine: dw-edma: Remove unused field irq in struct dw_edma_chip
> > > > > >    dmaengine: dw-edma: Change rg_region to reg_base in struct
> > > > > >    dmaengine: dw-edma: rename wr(rd)_ch_cnt to ll_wr(rd)_cnt in struct
> > > > > >
> > > > > > 2. Enhance EDMA driver to allow prode eDMA at EP side
> > > > > >    dmaengine: dw-edma: Add support for chip specific flags
> > > > > >    dmaengine: dw-edma: Add DW_EDMA_CHIP_32BIT_DBI for chip specific
> > > > > > flags (this patch removed at v11 because dma tree already have fixed
> > > > > > patch)
> > > > > >
> > > > > > 3. Bugs fix at EDMA driver when probe eDMA at EP side
> > > > > >    dmaengine: dw-edma: Fix programming the source & dest addresses for
> > > > > > ep
> > > > > >    dmaengine: dw-edma: Don't rely on the deprecated "direction" member
> > > > > >
> > > > > > 4. change pci-epf-test to use EDMA driver to transfer data.
> > > > > >    PCI: endpoint: Add embedded DMA controller test
> > > > > >
> > > > > > 5. Using imx8dxl to do test, but some EP functions still have not
> > > > > > upstream yet. So below patch show how probe eDMA driver at EP
> > > > > > controller driver.
> > > > > > https://lore.kernel.org/linux-pci/20220309120149.GB134091@thinkpad/T/#m979eb506c73ab3cfca2e7a43635ecdaec18d8097
> > > > >
> > > > > The series has been hanging out on review for over three months now.
> > > > > It has got to v11 and has been tested on at least two platforms. The
> > > > > original driver maintainer has been silent for all that time (most
> > > > > likely Gustavo dropped the driver maintaining role). Could you please
> > > > > merge it in seeing no comments have been posted for the last several
> > > > > weeks? The PCI Host/EP controller drivers maintainer suggested to get
> > > > > this series via the DMA-engine tree:
> > > > > https://lore.kernel.org/linux-pci/YnqlRShJzvma2SKM@lpieralisi/
> > > > > which is obviously right seeing it mainly concerns the DW eDMA driver.
> > > > > Though after that Lorenzo disappeared as quickly as popped up.)
> > > > >
> > > > > There is one more series depending on the changes in this
> > > > > patchset:
> > > > > https://lore.kernel.org/linux-pci/20220503225104.12108-1-Sergey.Semin@baikalelectronics.ru/
> > > > > Me and Frank already settled all the conflicts and inter-dependencies,
> > > > > so at least his series is more than ready to be merged in into the
> > > > > kernel repo. It would be very good to get it accepted on this merge
> > > > > window so to have the kernel v5.19 with all this changes available.
> > > >
> 
> > > > Since the v5.19 merge window is already open, it seems doubtful that
> > > > anybody would merge this so late in the cycle.
> 
> In this case it would be safer to merge this whole series through your
> repo. See my series:
> "[PATCH v2 00/26] dmaengine: dw-edma: Add RP/EP local DMA controllers support"
> https://lore.kernel.org/linux-pci/20220503225104.12108-1-Sergey.Semin@baikalelectronics.ru/
> depends in the Frank' patchset. Meanwhile my patchset is also based on the
> DW PCIe modifications introduced in the set of the series:
> "[PATCH v2 00/17] PCI: dwc: Add dma-ranges/YAML-schema/Baikal-T1 support"
> https://lore.kernel.org/linux-pci/20220503214638.1895-1-Sergey.Semin@baikalelectronics.ru/
> and
> "[PATCH v3 00/13] PCI: dwc: Various fixes and cleanups"
> https://lore.kernel.org/linux-pci/20220517125058.18488-1-Sergey.Semin@baikalelectronics.ru/
> 
> So to speak in order to have more coherent repos with least merge,
> logical problems the next order of the merging would be preferable:
> 1) Frank's patchset (ready to be merged in):
> [PATCH v11 0/8] Enable designware PCI EP EDMA locally
> https://lore.kernel.org/linux-pci/20220517151915.2212838-1-Frank.Li@nxp.com
> 2) My series (ready to be merged in):
> [PATCH v3 00/13] PCI: dwc: Various fixes and cleanups
> https://lore.kernel.org/linux-pci/20220517125058.18488-1-Sergey.Semin@baikalelectronics.ru/
> 3) My series (still in review, I need to fix some Rob' and Manivannan' notes)
> [PATCH v2 00/17] PCI: dwc: Add dma-ranges/YAML-schema/Baikal-T1 support
> https://lore.kernel.org/linux-pci/20220503214638.1895-1-Sergey.Semin@baikalelectronics.ru/
> 4) Me series (ready to be merged in, but depends on the prev patchsets):
> https://lore.kernel.org/linux-pci/20220503225104.12108-1-Sergey.Semin@baikalelectronics.ru/
> 
> Seeing the Frank patches won't make it into the mainline repo on
> this merge window, it would be great to collect all the changes in a
> single repository. Seeing Lorenzo disappeared as fast as popped up
> your repo is the best candidate since the DW eDMA block is a part of
> the DW PCIe controller.

I'll be happy to merge this via the PCI tree, given acks from Gustavo
and/or Vinod.

Bjorn

  reply	other threads:[~2022-05-24 15:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 15:19 [PATCH v11 0/8] Enable designware PCI EP EDMA locally Frank Li
2022-05-17 15:19 ` [PATCH v11 1/8] dmaengine: dw-edma: Remove unused field irq in struct dw_edma_chip Frank Li
2022-05-17 15:19 ` [PATCH v11 2/8] dmaengine: dw-edma: Detach the private data and chip info structures Frank Li
2022-05-17 15:19 ` [PATCH v11 3/8] dmaengine: dw-edma: Change rg_region to reg_base in struct dw_edma_chip Frank Li
2022-05-17 15:19 ` [PATCH v11 4/8] dmaengine: dw-edma: Rename wr(rd)_ch_cnt to ll_wr(rd)_cnt " Frank Li
2022-05-17 15:19 ` [PATCH v11 5/8] dmaengine: dw-edma: Drop dma_slave_config.direction field usage Frank Li
2022-05-17 15:19 ` [PATCH v11 6/8] dmaengine: dw-edma: Fix eDMA Rd/Wr-channels and DMA-direction semantics Frank Li
2022-05-17 15:19 ` [PATCH v11 7/8] dmaengine: dw-edma: Add support for chip specific flags Frank Li
2022-05-17 15:19 ` [PATCH v11 8/8] PCI: endpoint: Enable DMA tests for endpoints with DMA capabilities Frank Li
2022-05-23 18:22   ` Bjorn Helgaas
2022-05-23 19:19     ` Zhi Li
2022-05-23 22:18       ` Bjorn Helgaas
2022-05-24  1:54         ` Zhi Li
2022-05-24  5:09   ` Kishon Vijay Abraham I
2022-05-23 11:06 ` [PATCH v11 0/8] Enable designware PCI EP EDMA locally Serge Semin
2022-05-23 18:02   ` Bjorn Helgaas
2022-05-23 18:41     ` Zhi Li
2022-05-23 22:12       ` Bjorn Helgaas
2022-05-24  5:48         ` Serge Semin
2022-05-24 15:52           ` Bjorn Helgaas [this message]
2022-05-25  9:07             ` Serge Semin
2022-06-15 13:46               ` Zhi Li

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=20220524155201.GA247821@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=Sergey.Semin@baikalelectronics.ru \
    --cc=bhelgaas@google.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=kishon@ti.com \
    --cc=kw@linux.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=lznuaa@gmail.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh@kernel.org \
    --cc=vkoul@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).