remoteproc/omap: set bootaddr support
authorJuan Gutierrez <jgutierrez@ti.com>
Wed, 15 Aug 2012 15:25:48 +0000 (10:25 -0500)
committerOhad Ben-Cohen <ohad@wizery.com>
Tue, 11 Sep 2012 12:24:14 +0000 (15:24 +0300)
commit4980f465d21400303b234bcc3d082916f19f11ff
tree1c427b92a94c5911f3a5745f7ee09efb3634c200
parent55d512e245bc7699a8800e23df1a24195dd08217
remoteproc/omap: set bootaddr support

Some remote processors (like OMAP4's DSP) require we explicitly
set a boot address from which they'd start executing code when
taken out of reset.

Support for this is now being added to the omap-specific remoteproc
driver through a set_bootaddr function in the platform data which,
if needed, must be set according to the backend remote processor.

For OMAP4's dsp we can use the following control function:

  .set_bootaddr  = omap_ctrl_write_dsp_boot_addr

Signed-off-by: Juan Gutierrez <jgutierrez@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
[ohad: slight changes to the commit log]
Signed-off-by: Ohad Ben-Cohen <ohad@wizery.com>
arch/arm/plat-omap/include/plat/remoteproc.h
drivers/remoteproc/omap_remoteproc.c