From: Adrian Larumbe <adrian.martinezlarumbe@imgtec.com> To: Lars-Peter Clausen <lars@metafoo.de> Cc: <vkoul@kernel.org>, <dmaengine@vger.kernel.org>, <michal.simek@xilinx.com>, <linux-arm-kernel@lists.infradead.org> Subject: Re: [EXTERNAL] Re: [PATCH 0/4] Expand Xilinx CDMA functions Date: Fri, 23 Apr 2021 12:38:59 +0100 [thread overview] Message-ID: <20210423113859.tdowrt5nx5bxb225@adrianlarumbe-HP-Elite-7500-Series-MT> (raw) In-Reply-To: <c2876f2c-beb2-f159-9b61-d69ae6b8275a@metafoo.de> On 23.04.2021 11:17, Lars-Peter Clausen wrote: > The device_config() and device_prep_slave_sg() APIs are meant for > memory-to-device or device-to-memory transfers. This means the device address > is fixed and usually maps to a FIFO in the device. > > What you are implementing is memory-to-memory, which means addresses are > incremented on both sides of transfer. And this works if you know what you are > doing, e.g. you know that you are using a specific dmaengine driver that > implements the dmaengine API in a way that does not comply with the > specification. But it breaks for generic dmaengine API clients that expect > compliant behavior. And it is the reason why we have an API in the first > place, to get consistent behavior. If you have to know about the driver > specific semantics you might as well just bypass the framework and use driver > specific functions. You're absolutely right about this. I think I might've been confused when picking the right DMA Engine API callback to write this new functionality into by the fact that, on our particular configuration, transfers were being done between main system memory and DDR memory on a PCI card. However, from the point of view of the semantics of the API, these are still memory-to-memory transfers, just like you said. > It seems to me what we are missing from the DMAengine API is the equivalent of > device_prep_dma_memcpy() that is able to take SG lists. There is already a > memset_sg, it should be possible to add something similar for memcpy. I wasn't aware of the existence of this callback. Grepping the sources reveals a single consumer at the moment, I guess this also might've led me to wrongly conclude device_prep_slave_sg was the right choice. Perhaps I can convert most of the code currently in xilinx_cdma_prep_slave_sg to fit the semantics of this DMAengine API function instead. Any thoughts on this? Cheers, Adrian
WARNING: multiple messages have this Message-ID (diff)
From: Adrian Larumbe <adrian.martinezlarumbe@imgtec.com> To: Lars-Peter Clausen <lars@metafoo.de> Cc: <vkoul@kernel.org>, <dmaengine@vger.kernel.org>, <michal.simek@xilinx.com>, <linux-arm-kernel@lists.infradead.org> Subject: Re: [EXTERNAL] Re: [PATCH 0/4] Expand Xilinx CDMA functions Date: Fri, 23 Apr 2021 12:38:59 +0100 [thread overview] Message-ID: <20210423113859.tdowrt5nx5bxb225@adrianlarumbe-HP-Elite-7500-Series-MT> (raw) In-Reply-To: <c2876f2c-beb2-f159-9b61-d69ae6b8275a@metafoo.de> On 23.04.2021 11:17, Lars-Peter Clausen wrote: > The device_config() and device_prep_slave_sg() APIs are meant for > memory-to-device or device-to-memory transfers. This means the device address > is fixed and usually maps to a FIFO in the device. > > What you are implementing is memory-to-memory, which means addresses are > incremented on both sides of transfer. And this works if you know what you are > doing, e.g. you know that you are using a specific dmaengine driver that > implements the dmaengine API in a way that does not comply with the > specification. But it breaks for generic dmaengine API clients that expect > compliant behavior. And it is the reason why we have an API in the first > place, to get consistent behavior. If you have to know about the driver > specific semantics you might as well just bypass the framework and use driver > specific functions. You're absolutely right about this. I think I might've been confused when picking the right DMA Engine API callback to write this new functionality into by the fact that, on our particular configuration, transfers were being done between main system memory and DDR memory on a PCI card. However, from the point of view of the semantics of the API, these are still memory-to-memory transfers, just like you said. > It seems to me what we are missing from the DMAengine API is the equivalent of > device_prep_dma_memcpy() that is able to take SG lists. There is already a > memset_sg, it should be possible to add something similar for memcpy. I wasn't aware of the existence of this callback. Grepping the sources reveals a single consumer at the moment, I guess this also might've led me to wrongly conclude device_prep_slave_sg was the right choice. Perhaps I can convert most of the code currently in xilinx_cdma_prep_slave_sg to fit the semantics of this DMAengine API function instead. Any thoughts on this? Cheers, Adrian _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-04-23 11:39 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-23 1:19 [PATCH 0/4] Expand Xilinx CDMA functions Adrian Larumbe 2021-04-23 1:19 ` Adrian Larumbe 2021-04-23 1:19 ` [PATCH 1/4] dmaengine: xilinx_dma: Add extended address support in CDMA Adrian Larumbe 2021-04-23 1:19 ` Adrian Larumbe 2021-04-23 1:19 ` [PATCH 2/4] dmaengine: xilinx_dma: Add channel configuration setting callback Adrian Larumbe 2021-04-23 1:19 ` Adrian Larumbe 2021-04-23 1:19 ` [PATCH 3/4] dmaengine: xilinx_dma: Add CDMA SG transfer support Adrian Larumbe 2021-04-23 1:19 ` Adrian Larumbe 2021-04-23 1:19 ` [PATCH 4/4] dmaengine: xilinx_dma: Add device synchronisation callback Adrian Larumbe 2021-04-23 1:19 ` Adrian Larumbe 2021-04-23 6:33 ` Lars-Peter Clausen 2021-04-23 6:33 ` Lars-Peter Clausen 2021-04-23 11:49 ` [EXTERNAL] " Adrian Larumbe 2021-04-23 11:49 ` Adrian Larumbe 2021-04-23 9:17 ` [PATCH 0/4] Expand Xilinx CDMA functions Lars-Peter Clausen 2021-04-23 9:17 ` Lars-Peter Clausen 2021-04-23 11:38 ` Adrian Larumbe [this message] 2021-04-23 11:38 ` [EXTERNAL] " Adrian Larumbe 2021-04-23 13:24 ` Vinod Koul 2021-04-23 13:24 ` Vinod Koul 2021-04-23 13:51 ` Lars-Peter Clausen 2021-04-23 13:51 ` Lars-Peter Clausen 2021-04-23 14:36 ` [EXTERNAL] " Adrian Larumbe 2021-04-23 14:36 ` Adrian Larumbe 2021-04-23 17:20 ` Vinod Koul 2021-04-23 17:20 ` Vinod Koul 2021-06-01 10:29 ` radhey pandey 2021-06-01 10:29 ` radhey pandey 2021-07-02 14:23 ` [EXTERNAL] " Adrian Larumbe 2021-07-02 14:23 ` Adrian Larumbe 2021-07-05 3:53 ` Vinod Koul 2021-07-05 3:53 ` Vinod Koul
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=20210423113859.tdowrt5nx5bxb225@adrianlarumbe-HP-Elite-7500-Series-MT \ --to=adrian.martinezlarumbe@imgtec.com \ --cc=dmaengine@vger.kernel.org \ --cc=lars@metafoo.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=michal.simek@xilinx.com \ --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: linkBe 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.