From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: On __raw_readl readl_relaxed and readl nocheinmal
Date: Fri, 27 May 2011 13:07:26 +0100 [thread overview]
Message-ID: <20110527120725.GV969@shareable.org> (raw)
In-Reply-To: <BANLkTimoRbokF4pnfMOf5WkPK+TyrHWwDg@mail.gmail.com>
Catalin Marinas wrote:
> With all of them, even writel(), you don't know when the actual
> hardware write happens. You can issue a DSB after to ensure write
> completion (I think defined as the device begins to change its state
> as a result of the write) but you can't tell whether the device
> finished changing its state. For that you would need other means like
> reading back from the device.
With PCI on x86, writel() may not reach the hardware immediately (PCI
queues the writes), so I believe you need readl() to some register on
the same device to ensure the write has been acknowledged by the
device.
Does DSB on ARM replace the need for that readl()?
-- Jamie
next prev parent reply other threads:[~2011-05-27 12:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 10:04 On __raw_readl readl_relaxed and readl nocheinmal Linus Walleij
2011-05-20 10:42 ` Russell King - ARM Linux
2011-05-20 10:50 ` Arnd Bergmann
2011-05-20 10:55 ` Catalin Marinas
2011-05-27 12:07 ` Jamie Lokier [this message]
2011-05-27 14:37 ` Catalin Marinas
2011-05-27 14:14 ` Joakim BECH
2011-05-27 15:02 ` Catalin Marinas
2011-05-27 16:16 ` Arnd Bergmann
2011-05-27 16:38 ` Catalin Marinas
2011-05-27 17:10 ` Arnd Bergmann
2011-05-27 18:06 ` Russell King - ARM Linux
2011-05-29 9:24 ` Catalin Marinas
2011-05-27 18:04 ` Russell King - ARM Linux
2011-05-31 7:12 ` viresh kumar
2011-05-31 8:53 ` Catalin Marinas
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=20110527120725.GV969@shareable.org \
--to=jamie@shareable.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 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.