On Thu 05 May 06:29 PDT 2016, Lee Jones wrote: > Normally used for management of; carveout, devmem and trace memory. > I like the gist of this, but I have two issues from the Qualcomm land that I think would tie into a slightly more generic version of this. 1) Registering carveouts from memory-regions, without having a resource table. 2) Tying the Qualcomm shared memory implementation to the appropriate remoteproc instance (e.g. for crash handling). I also think we should match the subdev with entries from the resource table based on some key, so that we don't add a limitation of only having a single carveout per rproc. I will do some prototyping based on your patch and will get back to you. Regards, Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-remoteproc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
