> From: Arnd Bergmann > Sent: Thursday, June 23, 2011 11:47 AM > Subject: Re: [RFC 0/8] Introducing a generic AMP/IPC framework > > On Thursday 23 June 2011 18:27:10 Grosen, Mark wrote: > > First, we are not abandoning DSPLINK. We have many users of this, even > > though it is out-of-tree, and we will continue to support it. That said, we > > do intend to make this new design the basis for DSPLINK-like > > functionality. It's designed to be done "the right way" for Linux (and we > > are looking for feedback to make it better). It is also designed to be more > > scalable and extensible in userspace. With a solid kernel foundation, we can > > provide lots of functionality in userspace, or users can implement their own > > custom solutions. One of the key things to do is map our existing DSPLINK > > APIs, like MessageQ, to the new rpmsg transport. > > Sounds all good. What about the PRUSS code? Does that fit into the new > model as well? > > Arnd Arnd, Yes, I have been following some of the PRUSS discussion. I think the remoteproc driver could be used to manage the basic load/start/stop of the PRUSS processor. I am not sure if the virio/rpmsg part would be a good fit. The PRUSS processor is pretty limited, so the generality of virtio might be too much to fit and too much overhead. However, one of the good things about remoteproc currently is that it is standalone, so other transports could use it via the rproc_get/put methods. Mark -- 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
