Hi Juan,
On Mon, May 7, 2012 at 5:38 PM, Gutierrez, Juan jgutier...@ti.com wrote:
@@ -40,6 +41,7 @@ struct omap_rproc_pdata {
const struct rproc_ops *ops;
int (*device_enable) (struct platform_device *pdev);
int (*device_shutdown) (struct platform_device *pdev);
+
Hi Ohad
Thanks for reviewing.
On Sun, May 6, 2012 at 6:21 AM, Ohad Ben-Cohen o...@wizery.com wrote:
Hi Juan,
Thanks for the patches ! it's exciting to see that support for OMAP's
DSP is (relatively) easily achieved now. I hope your work can be a
good basis for an OMAP3 port, too.
Overall
Hi Juan,
Thanks for the patches ! it's exciting to see that support for OMAP's
DSP is (relatively) easily achieved now. I hope your work can be a
good basis for an OMAP3 port, too.
Overall the patches look good, I have only some minor comments inline.
And - sorry for the late response. I've
Some remote processors (like Omap4's DSP) need to explicitly
configure a boot address in a special register or memory
location, and this is the address from which they start
executing code when taken out of reset.
Support for this infrastructure has been added to remoteproc
code. The memory or
