From: clemens@ladisch•de (Clemens Ladisch)
To: linux-arm-kernel@lists•infradead.org
Subject: About dma_sync_single_for_{cpu,device}
Date: Tue, 31 Jul 2012 08:59:21 +0200 [thread overview]
Message-ID: <50178249.7090306@ladisch.de> (raw)
In-Reply-To: <20120731064557.GA4676@gobelin>
Karl Beldan wrote:
> To tx a chunk of data from the SoC => network device, we :
> - prepare a buffer with a leading header embedding a pattern,
> - trigger the xfer and wait for an irq
> // The device updates the pattern and then triggers an irq
> - upon irq we check the pattern for the xfer completion
>
> I was expecting the following to work:
> addr = dma_map_single(dev, buffer, size, DMA_TO_DEVICE);
Of both the CPU and the device write to the buffer, you must use
DMA_BIDIRECTIONAL.
Regards,
Clemens
next prev parent reply other threads:[~2012-07-31 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120730202401.GA4947@gobelin>
2012-07-31 6:45 ` About dma_sync_single_for_{cpu,device} Karl Beldan
2012-07-31 6:59 ` Clemens Ladisch [this message]
2012-07-31 7:27 ` Karl Beldan
2012-07-31 7:34 ` Clemens Ladisch
2012-07-31 8:30 ` Karl Beldan
2012-07-31 9:09 ` Russell King - ARM Linux
2012-07-31 19:31 ` Karl Beldan
2012-07-31 20:08 ` Russell King - ARM Linux
2012-08-01 6:50 ` Karl Beldan
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=50178249.7090306@ladisch.de \
--to=clemens@ladisch$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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