Hi Suman, On Tue, Jul 29, 2014 at 10:33 PM, Suman Anna <s-anna@xxxxxx> wrote: > We currently have two usecases. The primary usecase is the WkupM3 > processor on TI Sitara AM335x/AM437x SoCs used for suspend/resume > management. This series is a dependency for the WkupM3 remoteproc driver > that Dave posted [1]. More details are in section 8.1.4.6 of the AM335x > TRM [2]. The program/data sections for this processor all _needs_ to be > in the two internal memory RAMS (16K Unified RAM and 8K Data RAM), and > there is no MMU for this processor. The current RSC_CARVEOUT and > RSC_DEVMEM do not fit to describe this type of memory (we neither > allocate memory through dma api nor do we need to map these into an MMU). Thanks for the details. Can we define a CMA block for these regions, and then just use carveout resource entries instead of the ioremap approach? This may require some changes in remoteproc which we'll need to think about, but it sounds like it may fit the problem better instead of forcing ioremap to provide a regular pointer (we're supposed to use ioremaped memory only with memory primitives such as readl/writel/..). Thanks, Ohad. -- 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
