On Fri, Jul 16, 2010 at 8:01 PM, Larry Bassel <lbassel@xxxxxxxxxxxxxx> wrote: > On 16 Jul 10 08:58, Russell King - ARM Linux wrote: >> On Thu, Jul 15, 2010 at 08:48:36PM -0400, Tim HRM wrote: >> > Interesting, since I seem to remember the MSM devices mostly conduct >> > IO through regions of normal RAM, largely accomplished through >> > ioremap() calls. >> > >> > Without more public domain documentation of the MSM chips and AMSS >> > interfaces I wouldn't know how to avoid this, but I can imagine it >> > creates a bit of urgency for Qualcomm developers as they attempt to >> > upstream support for this most interesting SoC. >> >> As the patch has been out for RFC since early April on the linux-arm-kernel >> mailing list (Subject: [RFC] Prohibit ioremap() on kernel managed RAM), >> and no comments have come back from Qualcomm folk. > > We are investigating the impact of this change on us, and I > will send out more detailed comments next week. > >> >> The restriction on creation of multiple V:P mappings with differing >> attributes is also fairly hard to miss in the ARM architecture >> specification when reading the sections about caches. >> > > Larry Bassel > > -- > Sent by an employee of the Qualcomm Innovation Center, Inc. > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. > Hi Larry and Qualcomm people. I'm curious what your reason for introducing this new api (or adding to dma) is. Specifically how this would be used to make the memory mapping of the MSM chip dynamic in contrast to the fixed _PHYS defines in the Android and Codeaurora trees. I'm also interested in how this ability to map memory regions as files for devices like KGSL/DRI or PMEM might work and why this is better suited to that purpose than existing methods, where this fits into camera preview and other issues that have been dealt with in these trees in novel ways (from my perspective). Thanks, Timothy Meade tmzt #htc-linux -- 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
