linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7] dma: Add Xilinx AXI Direct Memory Access Engine driver support
Date: Sun, 28 Jun 2015 20:15:29 +0530	[thread overview]
Message-ID: <20150628144529.GZ19530@localhost> (raw)
In-Reply-To: <CAH=tA9F3=oqWi66EpkG-ecWHuVbOua+ceeiQD03WjiA=QdgA-g@mail.gmail.com>

On Sat, Jun 27, 2015 at 05:44:38PM +0300, Nicolae Rosia wrote:
> On Sat, Jun 27, 2015 at 5:40 PM, Vinod Koul <vinod.koul@intel.com> wrote:
> [...]
> >> Please let me know if you are not clear.
> > No sorry am not...
> >
> > I asked how the device address in configured. For both MM2S S2MM you are
> > using sg for memory address, where are you getting device adress, are you
> > assuming/hardcoding or getting somehow, if so how?
> As the name says, one end is memory (MM) and the other end is an AXI4
> Stream Bus (S) which has no concept of memory address.
> So yes, it is hardcoded at design time.
So where does the data go at the end of stream bus, who configures that?
Shouldnt all this be at least documented...

-- 
~Vinod

  reply	other threads:[~2015-06-28 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  6:35 [PATCH v7] dma: Add Xilinx AXI Direct Memory Access Engine driver support Kedareswara rao Appana
2015-06-16 19:19 ` Nicolae Rosia
2015-06-18 10:16   ` Appana Durga Kedareswara Rao
2015-06-19 16:49 ` Jeremy Trimble
2015-06-24 17:12   ` Appana Durga Kedareswara Rao
2015-06-22 10:49 ` Vinod Koul
2015-06-24 17:12   ` Appana Durga Kedareswara Rao
2015-06-27 14:40     ` Vinod Koul
2015-06-27 14:44       ` Nicolae Rosia
2015-06-28 14:45         ` Vinod Koul [this message]
2015-06-28 15:06           ` Nicolae Rosia
2015-07-07 15:31       ` Appana Durga Kedareswara Rao

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=20150628144529.GZ19530@localhost \
    --to=vinod.koul@intel.com \
    --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).