Hi Russell, [CC Paul Mundt] On Sat, Apr 16, 2011 at 12:41 AM, Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> wrote: > On Fri, Apr 15, 2011 at 09:32:01AM -0600, Grant Likely wrote: >> Yes, once the infrastructure is in place, powerpc can do its own >> migration to the new code. I vote for putting it in lib at the >> outset. > > I don't agree with stuffing non-arch directories with code which people > haven't already agreed should be shared. As I've already said, in my > experience it's hard to get agreement in the first place and even when > you can the API generally needs to be changed from what you first think > would be reasonable. > > So, lets wait to see whether the SH folk reply. The SH arch is using NUMA for on-chip SRAM on some CPUs, but for SH-Mobile ARM we have no software support at this point. The SH/ARM hardware has a bunch of different on-chip memories in place, and they all have individual power management support through both clock gating and power domains. I assume other vendors have similar setups. I'd like to have some refcounting in place for the SRAM code if possible, which would trickle down to runtime pm get/put which in turn would allow us to control the power dynamically. Not sure how easy that would be to accomplish though. Paul may have some ideas on how to share the code between ARM and SH. Thanks, / magnus -- 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