+Vinod Koul Hi, On 30/05/19 4:07 AM, Alan Mikhak wrote: > On Mon, May 27, 2019 at 2:09 AM Gustavo Pimentel > <Gustavo.Pimentel@xxxxxxxxxxxx> wrote: >> >> On Fri, May 24, 2019 at 20:42:43, Alan Mikhak <alan.mikhak@xxxxxxxxxx> >> wrote: >> >> Hi Alan, >> >>> On Fri, May 24, 2019 at 1:59 AM Gustavo Pimentel >>> <Gustavo.Pimentel@xxxxxxxxxxxx> wrote: >>>> >>>> Hi Alan, >>>> >>>> This patch implementation is very HW implementation dependent and >>>> requires the DMA to exposed through PCIe BARs, which aren't always the >>>> case. Besides, you are defining some control bits on >>>> include/linux/pci-epc.h that may not have any meaning to other types of >>>> DMA. >>>> >>>> I don't think this was what Kishon had in mind when he developed the >>>> pcitest, but let see what Kishon was to say about it. >>>> >>>> I've developed a DMA driver for DWC PCI using Linux Kernel DMAengine API >>>> and which I submitted some days ago. >>>> By having a DMA driver which implemented using DMAengine API, means the >>>> pcitest can use the DMAengine client API, which will be completely >>>> generic to any other DMA implementation. right, my initial thought process was to use only dmaengine APIs in pci-epf-test so that the system DMA or DMA within the PCIe controller can be used transparently. But can we register DMA within the PCIe controller to the DMA subsystem? AFAIK only system DMA should register with the DMA subsystem. (ADMA in SDHCI doesn't use dmaengine). Vinod Koul can confirm. If DMA within the PCIe controller cannot be registered in DMA subsystem, we should use something like what Alan has done in this patch with dma_read ops. The dma_read ops implementation in the EP controller can either use dmaengine APIs or use the DMA within the PCIe controller. I'll review the patch separately. Thanks Kishon
