From: ww-ml@gmx.de (Wolfgang Wegner)
To: linux-arm-kernel@lists.infradead.org
Subject: Kirkwood DMA engine transfer to PCI memory space?
Date: Wed, 6 Oct 2010 16:33:46 +0200 [thread overview]
Message-ID: <20101006143346.GA23416@debian-wegner1.datadisplay.de> (raw)
In-Reply-To: <20101006093134.GA32436@debian-wegner1.datadisplay.de>
Hi again,
I found the reason this why this could not work.
Somehow I overlooked the address windows of the XOR engine,
which are only set for the memory regions. I see no way to
cleanly set these windows in our case without some kind of
infrastructure in place, because we use PCI hotplug to rescan
the bus after the FPGA is loaded.
So for testing I just added this quick and dirty code to
mv_xor_conf_mbus_windows() right after setting the memory
windows:
if (i < 8) {
printk("setting up DMA window@0xe0000000 (64MB)\n");
writel(0xe0000000 | (0xe8 << 8) | 0x04, base + WINDOW_BASE(i));
writel((64*1024*1024 - 1) & 0xffff0000, base + WINDOW_SIZE(i));
win_enable |= (1 << i);
win_enable |= 3 << (16 + (2 * i));
}
Now I can get transfers to reach our FPGA, which then crashes
because it can not handle the bursts. Ouch. :)
The remaining question is if this is some special case for
Kirkwood, or is it a design feature/flaw that anything but
memory is not handled by current dmaengine code?
Regards,
Wolfgang
next prev parent reply other threads:[~2010-10-06 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 9:31 Kirkwood DMA engine transfer to PCI memory space? Wolfgang Wegner
2010-10-06 14:33 ` Wolfgang Wegner [this message]
2010-10-06 16:27 ` saeed bishara
2010-10-06 16:45 ` Wolfgang Wegner
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=20101006143346.GA23416@debian-wegner1.datadisplay.de \
--to=ww-ml@gmx.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).