Add a remoteproc driver for OMAP4, so we can boot the dual-M3 and
and DSP subsystems.
Use the omap_device_* API to control the hardware state, and utilize
the OMAP mailbox to interrupt the remote processor when a new message
is pending (the mailbox payload is used to tell it which virtqueue was
the message placed in).
Conversely, when an inbound mailbox message arrives, tell the remoteproc
core which virtqueue is triggered.
Later we will also use the mailbox payload to signal omap-specific
events like remote crashes (which will be used to trigger remoteproc
recovery) and power management transitions. At that point we will also
extend the remoteproc core to support this.
Based on (but now quite far from) work done by Fernando Guzman Lugo
<email@example.com> and Hari Kanigeri <firstname.lastname@example.org>.
Designed with Brian Swetland <email@example.com>.
Signed-off-by: Ohad Ben-Cohen <firstname.lastname@example.org>
Acked-by: Tony Lindgren <email@example.com>
Cc: Brian Swetland <firstname.lastname@example.org>
Cc: Arnd Bergmann <email@example.com>
Cc: Grant Likely <firstname.lastname@example.org>
Cc: Russell King <email@example.com>
Cc: Rusty Russell <firstname.lastname@example.org>
Cc: Andrew Morton <email@example.com>
Cc: Greg KH <firstname.lastname@example.org>
Cc: Stephen Boyd <email@example.com>