Thread (29 messages) 29 messages, 4 authors, 2012-10-01
STALE4993d
Revisions (6)
  1. v2 [diff vs current]
  2. v3 [diff vs current]
  3. v3 [diff vs current]
  4. v3 [diff vs current]
  5. v3 [diff vs current]
  6. v3 current

[PATCH V3 1/8] ARM: OMAP3: Add debugss HWMOD data

From: Jon Hunter <hidden>
Date: 2012-09-24 15:57:50
Also in: linux-omap

Hi Paul,

On 09/20/2012 12:13 PM, Paul Walmsley wrote:
On Wed, 19 Sep 2012, Paul Walmsley wrote:
quoted
On Mon, 10 Sep 2012, Jon Hunter wrote:
quoted
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 <redacted>
Signed-off-by: Jon Hunter <redacted>
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help