From: smuckle@codeaurora.org (Steve Muckle)
To: linux-arm-kernel@lists.infradead.org
Subject: IO access and *_relaxed macros
Date: Fri, 25 Mar 2011 16:55:16 -0700 [thread overview]
Message-ID: <4D8D2B64.9030709@codeaurora.org> (raw)
In-Reply-To: <1301047705.25814.4.camel@e102109-lin.cambridge.arm.com>
On 03/25/11 03:08, Catalin Marinas wrote:
> Are there other scenarios (in relation with coherent DMA buffers) where
> we need a DSB after writel() or before readl()?
I'm not sure about use with DMA buffers - I've just been looking at
these macros with respect to (non-DMA related) device accesses, since
they're heavily used for this purpose as well.
thanks,
Steve
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2011-03-25 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 18:22 IO access and *_relaxed macros Steve Muckle
2011-03-25 10:08 ` Catalin Marinas
2011-03-25 23:55 ` Steve Muckle [this message]
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=4D8D2B64.9030709@codeaurora.org \
--to=smuckle@codeaurora.org \
--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).