From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: <vinod.koul@intel.com>, <dan.j.williams@intel.com>,
<tony@atomide.com>, <linux@armlinux.org.uk>
Cc: <dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-omap@vger.kernel.org>, <arnd@arndb.de>
Subject: Re: [PATCH v2 1/2] dmaengine: dma_slave_config: add support for slave port window
Date: Tue, 29 Nov 2016 12:47:48 +0200 [thread overview]
Message-ID: <1c9221e8-c2e9-4d87-4d74-670e1bc2fec1@ti.com> (raw)
In-Reply-To: <20161117125017.14954-2-peter.ujfalusi@ti.com>
Vinod,
On 11/17/2016 02:50 PM, Peter Ujfalusi wrote:
> Some slave devices uses address window instead of single register for read
> and/or write of data. With the src/dst_port_window_size the address window
> can be specified and the DMAengine driver should use this information to
> correctly set up the transfer to loop within the provided window.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
> include/linux/dmaengine.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> index cc535a478bae..689d44327ef3 100644
> --- a/include/linux/dmaengine.h
> +++ b/include/linux/dmaengine.h
> @@ -336,6 +336,12 @@ enum dma_slave_buswidth {
> * may or may not be applicable on memory sources.
> * @dst_maxburst: same as src_maxburst but for destination target
> * mutatis mutandis.
> + * @src_port_window_size: The length of the register area the data need to be
> + * written on the device side. It is only used for devices which is using an
> + * area instead of a single register to receive the data. Typically the DMA
> + * loops in this area in order to transfer the data.
> + * @dst_port_window_size: same as src_port_window_size but for the destination
> + * port.
I think this needs some clarification.
Should the src/dst_port_window_size be in bytes or in words? I think it would
make more sense to define it as number of words to be in sync with the
src/dst_maxburst.
I will need to resend the series either way. The omap-dma patch does not
handle this correctly.
> * @device_fc: Flow Controller Settings. Only valid for slave channels. Fill
> * with 'true' if peripheral should be flow controller. Direction will be
> * selected at Runtime.
> @@ -363,6 +369,8 @@ struct dma_slave_config {
> enum dma_slave_buswidth dst_addr_width;
> u32 src_maxburst;
> u32 dst_maxburst;
> + u32 src_port_window_size;
> + u32 dst_port_window_size;
> bool device_fc;
> unsigned int slave_id;
> };
>
--
Péter
next prev parent reply other threads:[~2016-11-29 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 12:50 [PATCH v2 0/2] dmaengine: core/omap-dma: Support for port window Peter Ujfalusi
2016-11-17 12:50 ` [PATCH v2 1/2] dmaengine: dma_slave_config: add support for slave " Peter Ujfalusi
2016-11-29 10:47 ` Peter Ujfalusi [this message]
2016-11-29 13:14 ` Vinod Koul
[not found] ` <20161117125017.14954-3-peter.ujfalusi@ti.com>
2016-11-25 6:12 ` [PATCH v2 2/2] dmaengine: omap-dma: Support for slave devices with data " Vinod Koul
2016-11-25 9:38 ` Peter Ujfalusi
2016-11-29 3:17 ` 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=1c9221e8-c2e9-4d87-4d74-670e1bc2fec1@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.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).