All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Serge Semin <fancer.lancer@gmail.com>
Cc: Frank Li <Frank.Li@nxp.com>,
	gustavo.pimentel@synopsys.com, hongxing.zhu@nxp.com,
	l.stach@pengutronix.de, linux-imx@nxp.com,
	linux-pci@vger.kernel.org, dmaengine@vger.kernel.org,
	lznuaa@gmail.com, helgaas@kernel.org, kishon@ti.com,
	lorenzo.pieralisi@arm.com, robh@kernel.org, kw@linux.com,
	bhelgaas@google.com, manivannan.sadhasivam@linaro.org,
	Sergey.Semin@baikalelectronics.ru
Subject: Re: [PATCH v12 0/8] Enable designware PCI EP EDMA locally
Date: Thu, 16 Jun 2022 08:40:41 -0700	[thread overview]
Message-ID: <YqtO+bOFLlztBUAG@matsya> (raw)
In-Reply-To: <20220616152048.gcqacgs2ed66vsl4@mobilestation>

On 16-06-22, 18:20, Serge Semin wrote:
> On Thu, Jun 16, 2022 at 07:30:23AM -0700, Vinod Koul wrote:
> > On 16-06-22, 17:03, Serge Semin wrote:
> > > On Thu, Jun 16, 2022 at 05:02:00PM +0300, Serge Semin wrote:
> > > > On Thu, Jun 16, 2022 at 04:54:13PM +0300, Serge Semin wrote:
> > > > > On Thu, Jun 16, 2022 at 06:51:55AM -0700, Vinod Koul wrote:
> > > > > > On 24-05-22, 10:21, 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
> > > > > > 
> > > > > 
> > > > > > Applied to dmaengine-next, thanks
> > > > > 
> > > > 
> > > > > Vinod, this was supposed to be merged in through PCIe repo.( I asked
> > > > > many times of that. Bjorn also agreed to merge it in. Could drop it
> > > > > from yout repo?
> > > > 
> > > 
> > > > I asked it several time including in the framework of this thread:
> > > > https://lore.kernel.org/dmaengine/20220525092306.wuansog6fe2ika3b@mobilestation/
> > > > There are dependencies of my patchsets from this one. Please consider
> > > > dropping it from your dmaengine-next repo while it's still possible
> > > > since taking DW eDMA and PCie patches through the PCie repo would be
> > > > more natural.
> > > 
> > > The only thing we were waiting for was you ack tag...
> > 
> 
> > Is there any dependency, since this has many dmaengine patches and one
> > pcie patch which was acked by Kishon, so can go thru dmaengine tree...
> 
> Right. This one is fully suitable for the DMA-engine tree, but there
> are dependencies of my work from this series. My patchsets in its turn
> concern both PCIe and DMA-engine parts.
> 
> Here is the deal. My work consists of four patchsets:
> [PATCH v4 00/18] PCI: dwc: Various fixes and cleanups
> https://lore.kernel.org/linux-pci/20220610082535.12802-1-Sergey.Semin@baikalelectronics.ru/
> [PATCH v3 00/15] PCI: dwc: Add hw version and dma-ranges support
> https://lore.kernel.org/linux-pci/20220610084444.14549-1-Sergey.Semin@baikalelectronics.ru/
> [PATCH v3 00/17] PCI: dwc: Add generic resources and Baikal-T1 support
> https://lore.kernel.org/linux-pci/20220610085706.15741-1-Sergey.Semin@baikalelectronics.ru/
> [PATCH v3 00/24] dmaengine: dw-edma: Add RP/EP local DMA controllers support
> https://lore.kernel.org/dmaengine/20220610091459.17612-1-Sergey.Semin@baikalelectronics.ru/
> 
> The last patchset depends on the Frank series and my DW PCIe
> patchsets listed above. To cut it shortly here is the
> dependencies graph:
> 
>                 PCIe RP/EP            |               DMA engine
>                     ^                 |                   ^
>                     |                 |                   |
> 1. Semin: [PATCH v4 00/18] "PCI: dwc: |                   |
>    Various fixes and cleanups"        |                   |
>                     ^                 |                   |
>                     |                 |                   |
> 2. Semin: [PATCH v3 00/15] "PCI: dwc: |                   |
>    Add hw version and dma-ranges      |                   |
>    support"                           |                   |
>                     ^                 |                   |
>                     |                 |                   |
> 3. Semin: [PATCH v3 00/17] "PCI: dwc: | 4. Li: [PATCH v12 0/8] "Enable
>    Add generic resources and Baikal-T1|    designware PCI EP EDMA locally"
>    support"                           |                   ^
>                     ^                                     |
>                     |                                     |
>                     +-----------------+-------------------+
>                                       |
>              5. Semin: [PATCH v3 00/24] "dmaengine: dw-edma:
>                 Add RP/EP local DMA controllers support"
> 
> As you can see my series (5) depends on the Frank' series (4). My series
> in its turn depends on the PCI patchsets (3), (2) and (1). So if you get
> to merge the Frank' patchset into your tree we'll need to merge the
> rest of the patchsets through your repo too. Seeing the DW eDMA device
> is implemented as either a separate PCIe device or embedded into the
> DW PCIe RP/EP controller and there are many PCI-related patches in my
> work, it would be more suitable to merge all the patches through the
> PCIe tree. Bjorn already agreed to do that here:
> https://lore.kernel.org/linux-pci/20220524155201.GA247821@bhelgaas/
> We only waited for your ackes. BTW should you have some free time
> please review my series (5) too since it mainly concerns the DW eDMA
> driver (though Mani, in Cc, has already done it and even performed
> the testing).
> 
> > 
> > I can drop if that suits all...
> 
> Yes please. Please drop the Frank' series from your repo, give your
> explicit ack if you are ok with it and let's merge it and the rest of
> the work through the Bjorn' repo. Patchset (1) has been fully reviewed.
> Series (2) and (3) need one more iteration to be finished. So I very
> much hope they will be done in the next few weeks, before the next
> merge window.

Ok dropped now

-- 
~Vinod

  reply	other threads:[~2022-06-16 15:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 15:21 [PATCH v12 0/8] Enable designware PCI EP EDMA locally Frank Li
2022-05-24 15:21 ` [PATCH v12 1/8] dmaengine: dw-edma: Remove unused field irq in struct dw_edma_chip Frank Li
2022-05-24 15:21 ` [PATCH v12 2/8] dmaengine: dw-edma: Detach the private data and chip info structures Frank Li
2022-05-24 15:21 ` [PATCH v12 3/8] dmaengine: dw-edma: Change rg_region to reg_base in struct dw_edma_chip Frank Li
2022-05-24 15:21 ` [PATCH v12 4/8] dmaengine: dw-edma: Rename wr(rd)_ch_cnt to ll_wr(rd)_cnt " Frank Li
2022-05-24 15:21 ` [PATCH v12 5/8] dmaengine: dw-edma: Drop dma_slave_config.direction field usage Frank Li
2022-05-24 15:21 ` [PATCH v12 6/8] dmaengine: dw-edma: Fix eDMA Rd/Wr-channels and DMA-direction semantics Frank Li
2022-05-24 15:21 ` [PATCH v12 7/8] dmaengine: dw-edma: Add support for chip specific flags Frank Li
2022-05-24 15:21 ` [PATCH v12 8/8] PCI: endpoint: Enable DMA tests for endpoints with DMA capabilities Frank Li
2022-05-25  9:23 ` [PATCH v12 0/8] Enable designware PCI EP EDMA locally Serge Semin
2022-05-25 14:41   ` Zhi Li
2022-05-31 14:02     ` Zhi Li
2022-06-15 20:23       ` Zhi Li
2022-06-16 13:51 ` Vinod Koul
2022-06-16 13:54   ` Serge Semin
2022-06-16 14:01     ` Serge Semin
2022-06-16 14:03       ` Serge Semin
2022-06-16 14:30         ` Vinod Koul
2022-06-16 15:20           ` Serge Semin
2022-06-16 15:40             ` Vinod Koul [this message]
2022-06-16 18:39               ` Serge Semin
2022-06-16 15:41 ` Vinod Koul
2022-06-16 16:35 ` Bjorn Helgaas
2022-06-16 18:49   ` Serge Semin

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=YqtO+bOFLlztBUAG@matsya \
    --to=vkoul@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=helgaas@kernel.org \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.