remoteproc: don't use virtio's weak barriers
authorOhad Ben-Cohen <ohad@wizery.com>
Thu, 12 Jan 2012 07:26:57 +0000 (09:26 +0200)
committerOhad Ben-Cohen <ohad@wizery.com>
Wed, 22 Feb 2012 16:28:48 +0000 (18:28 +0200)
commitdd6da1c5e99a3b736b52370c504a2b8843cbfda6
treec6d08a5fb72f817d5071c1e9338e9fe5a98e5fad
parentb719587eb46c588fabc71de97c28bafcf827acf7
remoteproc: don't use virtio's weak barriers

When creating a virtqueue for rpmsg, tell virtio we're not interested
in "weak" smp barriers, since we're talking to a real device.

On ARM, this means using a DSB instead of a DMB, which is needed
for platforms that kick the remote processor using some kind of
a mailbox device mapped to Device memory (otherwise the kick can
jump ahead and wake the remote processor before it has observed
the changes to the vrings).

Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
drivers/remoteproc/remoteproc_rpmsg.c