Public Version
www.ti.com
PRCM Functional Description
Table 3-75. Sleep Dependencies
Sleep Dependency
Power Domain
Clock
MPU
NEON
IVA2
SGX
CAM
DSS
PER
CORE_
CORE_
CORE_
USB
WKUP
Domain
L3
L4
CM
HOST
MPU
MPU
N/A
0
0
0
0
0
0
0
0
0
0
0
NEON
MPU
1
N/A
0
0
0
0
0
0
0
0
0
0
IVA2
IVA2
0
0
N/A
0
0
0
0
0
0
0
0
0
SGX
SGX
RW
0
0
N/A
0
0
0
0
0
0
0
0
CAM
CAM
RW
0
0
0
N/A
0
0
0
0
0
0
0
DSS
DSS
RW
0
RW
0
0
N/A
0
RW
0
0
0
0
PER
PER
RW
0
RW
0
0
0
N/A
1
0
0
0
0
CORE
CORE_L3
1
0
1
1
1
1
1
N/A
1
0
1
1
CORE_L4
1
0
1
0
0
0
0
1
N/A
0
0
0
CORE_CM
1
1
1
1
1
1
1
1
1
N/A
1
1
USBHOST
USBHOST
RW
0
RW
0
0
0
0
0
N/A
0
WKUP
WKUP
1
0
1
0
0
0
0
1
0
0
0
N/A
Notes:
No software control (hardwired values):
0
Does not depend on
1
Depends on
Software controllable
RW
Read and write
N/A
Not applicable
3.5.4.5.2 Wake-Up Dependencies
A wake-up dependency allows a power domain to wake up (from off, retention or inactive state to on state) when another power domain wakes up
(from off, retention or inactive state to on state). For example, power domain one (PD1) provides a service to power domain two (PD2), which
creates a dependency between the two domains. When the dependent power domain (PD2) wakes up, it signals PD1 with a broadcasted wake-up
event, causing PD1 to wake up.
A broadcasted wake-up event can originate from one of two sources:
•
PD2 internal wake-up event (typically, a peripheral wake-up event)
•
Abortion of the mute mode (at least one initiator in the domain exits standby mode) of PD2 when both the sleep dependency and wake-up
dependency with PD1 are enabled.
363
SWPU177N – December 2009 – Revised November 2010
Power, Reset, and Clock Management
Copyright © 2009–2010, Texas Instruments Incorporated