From: troy.kisky@boundarydevices.com (Troy Kisky)
To: linux-arm-kernel@lists.infradead.org
Subject: dma_alloc_coherent and cache?
Date: Tue, 15 Apr 2014 14:54:22 -0700 [thread overview]
Message-ID: <534DAA8E.1090904@boundarydevices.com> (raw)
In-Reply-To: <45E047AA-4C3B-4645-A590-5B75A1729ADA@nowonline.co.uk>
On 4/14/2014 10:43 PM, Lee Essen wrote:
> Hi,
>
> I'm working on a driver for a Marvell switch device (98dx4122) where the basic interface closely resembles the mv643xx_eth device.
>
> (I should say this is a bit of a personal project to experiment with a trendnet switch, not affiliated with any commercial activities.)
>
> GPL code from Marvell is available for an old kernel, so I have been working to use the mv643xx_eth concepts and at least get basic functionality up an running on the current kernel version.
>
> At a high level I have it working, however I get regular (reproducible) hangs and I suspect it's to do with the writes to the descriptiors (from dma_alloc_coherent) being buffered or cached and not making it to the device when dma is triggered.
>
Have you verified that a wmb() precedes transferring ownership of the descriptor to the controller
and the cpu does not touch the descriptor afterwards?
Regards
Troy
next prev parent reply other threads:[~2014-04-15 21:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 5:43 dma_alloc_coherent and cache? Lee Essen
2014-04-15 8:10 ` Andrew Lunn
2014-04-17 14:35 ` Valentin Longchamp
2014-04-15 8:43 ` Arnd Bergmann
2014-04-15 10:01 ` Lee Essen
2014-04-15 10:49 ` Arnd Bergmann
2014-04-15 16:22 ` Lee Essen
2014-04-15 16:49 ` Andrew Lunn
2014-04-15 21:54 ` Troy Kisky [this message]
2014-04-16 15:55 ` Lee Essen
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=534DAA8E.1090904@boundarydevices.com \
--to=troy.kisky@boundarydevices.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.