path: root/drivers/remoteproc/omap_remoteproc.c
diff options
authorJuan Gutierrez <jgutierrez@ti.com>2012-08-15 10:25:48 -0500
committerOhad Ben-Cohen <ohad@wizery.com>2012-09-11 15:24:14 +0300
commit4980f465d21400303b234bcc3d082916f19f11ff (patch)
tree1c427b92a94c5911f3a5745f7ee09efb3634c200 /drivers/remoteproc/omap_remoteproc.c
parent55d512e245bc7699a8800e23df1a24195dd08217 (diff)
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>
Diffstat (limited to 'drivers/remoteproc/omap_remoteproc.c')
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/remoteproc/omap_remoteproc.c b/drivers/remoteproc/omap_remoteproc.c
index a1f7ac1f8cf6..a0c168cde90d 100644
--- a/drivers/remoteproc/omap_remoteproc.c
+++ b/drivers/remoteproc/omap_remoteproc.c
@@ -116,6 +116,9 @@ static int omap_rproc_start(struct rproc *rproc)
struct omap_rproc_pdata *pdata = pdev->dev.platform_data;
int ret;
+ if (pdata->set_bootaddr)
+ pdata->set_bootaddr(rproc->bootaddr);
oproc->nb.notifier_call = omap_rproc_mbox_callback;
/* every omap rproc is assigned a mailbox instance for messaging */

Privacy Policy