Hi Paul, On 09/20/2012 12:13 PM, Paul Walmsley wrote: > On Wed, 19 Sep 2012, Paul Walmsley wrote: > >> On Mon, 10 Sep 2012, Jon Hunter wrote: >> >>> To enable PMU with runtime PM support on OMAP3 devices we need to be able to >>> dynamically enable and disable the debug sub-system at runtime. By adding HWMOD >>> data for the debug sub-system for OMAP3, we can build the PMU device using the >>> debug sub-system HWMOD and control this power domain using runtime PM. >>> >>> Reviewed-by: Benoit Cousson <b-cousson@xxxxxx> >>> Signed-off-by: Jon Hunter <jon-hunter@xxxxxx> >> >> Isn't this patch missing MPU address ranges? Looking at the OMAP4 TRM >> Table 2-2 "L3_EMU Memory Space Mapping" it should cover >> 0x54000000-0x541fffff? > > Looks like Jon is out of the office at the moment. So this one has been > updated locally to add the _OMAP3_ address space from the TRM (my earlier > message referred incorrectly to the OMAP4 address space). Updated patch > below. Thanks for catching that. Was not needed for PMU use-case but I should have added that for other use-cases. Cheers Jon -- 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
