remoteproc: safer boot/shutdown order
authorOhad Ben-Cohen <>
Mon, 13 Feb 2012 07:38:23 +0000 (09:38 +0200)
committerOhad Ben-Cohen <>
Tue, 6 Mar 2012 17:13:53 +0000 (19:13 +0200)
remoteproc: safer boot/shutdown order

Boot the remote processor only after setting up the virtqueues,
and shut it down before deleting them.

Remote processors should obey virtio status changes, and
therefore not manipulate/trigger the virtqueues while the virtio
driver isn't ready, but it's just safer not to rely on that
(plus a vq access might already be inflight while a vdev
status is changed).

We also don't have yet status change notifications, but that's
a temporary limitation.

Signed-off-by: Ohad Ben-Cohen <>
Cc: Brian Swetland <>
Cc: Iliyan Malchev <>
Cc: Arnd Bergmann <>
Cc: Grant Likely <>
Cc: Rusty Russell <>
Cc: Mark Grosen <>
Cc: John Williams <>
Cc: Michal Simek <>
Cc: Loic PALLARDY <>
Cc: Ludovic BARRE <>
Cc: Omar Ramirez Luna <>
Cc: Guzman Lugo Fernando <>
Cc: Anna Suman <>
Cc: Clark Rob <>
Cc: Stephen Boyd <>
Cc: Saravana Kannan <>
Cc: David Brown <>
Cc: Kieran Bingham <>
Cc: Tony Lindgren <>