* Suman Anna <s-anna@xxxxxx> [150903 16:01]: > >>>> On 07/23/2015 02:24 AM, Tony Lindgren wrote: > > OK maybe check the syss/sysc registers involved here for each hardware > > module here and which driver tinkers with which registers? This will > > make things a lot easier in the long run for sure. > > The OMAP remoteproc driver typically deals with only the reset registers > and another register in the Control module for programming the boot > address for the DSPs. You can look up the OMAP4 hwmod data for > reference. There is currently a .prcm.omap4.modulemode set for these, > and I have a patch to remove those. I haven't yet posted it yet [1], > because OMAP remoteprocs are still not bootable on mainline. Thanks for checking that. Like we chatted, let's make sure we don't end up with iommu and remoteproc "consumer device" specific data in the iommu and remoteproc code. Regards, Tony > [1] > http://git.ti.com/gitweb/?p=rpmsg/remoteproc.git;a=commit;h=0dd2a6a2d8869ee6cec92f75d70663259a41c11f -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
