From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dma: Add Xilinx AXI Video Direct Memory Access Engine driver support
Date: Mon, 20 Jan 2014 19:41:07 +0100 [thread overview]
Message-ID: <201401201941.07633.arnd@arndb.de> (raw)
In-Reply-To: <CA+mB=1+mrWAzBCxdMEji2MDRzHajmnxuWtz7iu96ML0DuAB3RQ@mail.gmail.com>
On Monday 20 January 2014, Srikanth Thokala wrote:
> >
> >> > * data width should be a property of the slave driver that is configured
> >> > through dma_slave_config(), unless you can have dma engines that only
> >> > support certain a width.
> >>
> >> Yes, this VDMA engine soft IP support only certain widths, which is
> >> configurable during IP synthesis.
> >
> > But what is this property used for in that case? Surely you can't
> > connect a slave device to a dmaengine if the bus width doesn't match.
> > You probably have a point here, but I don't understand it yet.
>
> There is a Data-Realignment Engine (DRE) in the IP which is only available for
> data width setting of 64-bits and less. So, we use the data-width DT parameter
> to verify this condition and we update alignment shift accordingly.
Ok, I have to admit I didn't understand all of that, but you clearly
know what you are talking about here, so I assume you are correct.
Arnd
next prev parent reply other threads:[~2014-01-20 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 17:53 [PATCH] Add Xilinx AXI Video DMA Engine driver Srikanth Thokala
2014-01-16 17:53 ` [PATCH] dma: Add Xilinx AXI Video Direct Memory Access Engine driver support Srikanth Thokala
2014-01-16 18:27 ` Levente Kurusa
2014-01-20 7:26 ` Srikanth Thokala
2014-01-17 14:36 ` Philip Balister
2014-01-20 7:27 ` Srikanth Thokala
2014-01-17 16:13 ` Arnd Bergmann
2014-01-20 8:00 ` Srikanth Thokala
2014-01-20 11:39 ` Arnd Bergmann
2014-01-20 13:35 ` Srikanth Thokala
2014-01-20 18:41 ` Arnd Bergmann [this message]
2014-01-17 15:32 ` [PATCH] Add Xilinx AXI Video DMA Engine driver Andy Shevchenko
2014-01-21 10:21 ` Srikanth Thokala
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=201401201941.07633.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).