remoteproc/omap: add a remoteproc driver for OMAP4
authorOhad Ben-Cohen <ohad@wizery.com>
Thu, 20 Oct 2011 16:53:35 +0000 (18:53 +0200)
committerOhad Ben-Cohen <ohad@wizery.com>
Wed, 8 Feb 2012 20:53:47 +0000 (22:53 +0200)
commit34ed5a33b1218efbe8b01e37738063800ccdcdcd
treeff9713a819e07756cb27c17b61cc779b299b9c2f
parentac8954a413930dae3c53f7e782f09a94e7eae88b
remoteproc/omap: add a remoteproc driver for OMAP4

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
<fernando.lugo@ti.com> and Hari Kanigeri <h-kanigeri2@ti.com>.

Designed with Brian Swetland <swetland@google.com>.

Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
Acked-by: Tony Lindgren <tony@atomide.com>
Cc: Brian Swetland <swetland@google.com>
Cc: Arnd Bergmann <arnd@arndb.de>
Cc: Grant Likely <grant.likely@secretlab.ca>
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>
Cc: Stephen Boyd <sboyd@codeaurora.org>
arch/arm/plat-omap/include/plat/remoteproc.h [new file with mode: 0644]
drivers/remoteproc/Kconfig
drivers/remoteproc/Makefile
drivers/remoteproc/omap_remoteproc.c [new file with mode: 0644]
drivers/remoteproc/omap_remoteproc.h [new file with mode: 0644]
This page took 0.036571 seconds and 5 git commands to generate.