From: Peter Hurley <peter@hurleysoftware.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Peter Hurley <peter@hurleysoftware.com>
Subject: [PATCH] firewire: Enable physical DMA above 4GB
Date: Tue, 26 Mar 2013 10:22:14 -0400 [thread overview]
Message-ID: <1364307734-27709-1-git-send-email-peter@hurleysoftware.com> (raw)
Quadlet reads to memory above 4GB is painfully slow when serviced
by the AR DMA context. In addition, the CPU(s) may be locked-up,
preventing any transfer at all.
Write the PhyUpperBound register with the end-of-memory value. If
end-of-memory is beyond the OHCI limit of 0x0000ffff00000000,
clamp to that value.
Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
---
drivers/firewire/ohci.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/firewire/ohci.c b/drivers/firewire/ohci.c
index 044ace3..b4135a5 100644
--- a/drivers/firewire/ohci.c
+++ b/drivers/firewire/ohci.c
@@ -2249,6 +2249,7 @@ static int ohci_enable(struct fw_card *card,
struct pci_dev *dev = to_pci_dev(card->device);
u32 lps, version, irqs;
int i, ret;
+ u32 phys_upper;
if (software_reset(ohci)) {
dev_err(card->device, "failed to reset ohci card\n");
@@ -2323,7 +2324,10 @@ static int ohci_enable(struct fw_card *card,
reg_write(ohci, OHCI1394_FairnessControl, 0);
card->priority_budget_implemented = ohci->pri_req_max != 0;
- reg_write(ohci, OHCI1394_PhyUpperBound, 0x00010000);
+ phys_upper = min(0xffff0000ULL,
+ (dma_get_required_mask(card->device) >> 16) + 1);
+ reg_write(ohci, OHCI1394_PhyUpperBound, max(phys_upper, 0x00010000U));
+
reg_write(ohci, OHCI1394_IntEventClear, ~0);
reg_write(ohci, OHCI1394_IntMaskClear, ~0);
--
1.8.1.2
next reply other threads:[~2013-03-26 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 14:22 Peter Hurley [this message]
2013-03-26 16:12 ` [PATCH] firewire: Enable physical DMA above 4GB Clemens Ladisch
2013-03-26 17:04 ` Peter Hurley
2013-03-26 18:22 ` Clemens Ladisch
2013-03-26 18:56 ` Stefan Richter
2013-03-26 19:08 ` Peter Hurley
2013-03-26 20:35 ` Stefan Richter
2013-03-29 10:44 ` Stefan Richter
2013-03-29 10:50 ` Peter Hurley
2013-03-29 11:19 ` Clemens Ladisch
2013-03-29 11:31 ` Peter Hurley
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=1364307734-27709-1-git-send-email-peter@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=stefanr@s5r6.in-berlin.de \
/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