Public Version
PRCM Basic Programming Model
www.ti.com
•
and
: CORE domain modules wake-up event status
•
: Peripheral domain modules wake-up event status
•
: WKUP domain modules wake-up event status
•
: HS USB Host subsystem wake-up control
The functional clock of the module causing the wakeup automatically restarts on the wakeup, but the
software must enable the functional clock (CM_FCLKEN_<domain_name> register) before clearing the
wake-up status bit.
NOTE:
•
Software must clear this register before a new sleep transition request; otherwise, the
register prevents the sleep transition from occurring.
•
If the PRM interrupt is enabled on a module wakeup, the PM_WKST_<domain_name>
must be cleared before clearing the PRM_IRQSTATUS_<processor_name> interrupt
status register.
3.6.2.5.3 PM_WKDEP_ <domain_name> (Wake-Up Dependency Register)
The wake-up dependency register allows the enabling/disabling of a wake-up dependency between power
domains. When a domain wakes up, it can wake up another domain.
The device has the following wake-up dependency registers:
•
: MPU power domain wake-up dependency with the following domains:
–
CORE
–
IVA2
–
WKUP
–
DSS
–
PER
•
: DSS power domain wake-up dependency with the following domains:
–
MPU
–
IVA2
–
WKUP
•
: The CAM power domain has programmable wake-up dependency with the
following domains:
–
MPU
–
IVA2
–
WKUP
•
: The PER power domain has programmable wake-up dependency with the
following domains:
–
MPU
–
IVA2
–
WKUP
–
CORE
The PER power domain can be wakened only by a wakeup of the L3 and D2D clock domains, not by
an L4 clock domain.
•
: The NEON power domain has programmable wake-up dependency with the
following domain:
–
MPU
•
: The IVA2 power domain has programmable wake-up dependency with the
following domains:
–
MPU
–
PER
–
WKUP
412
Power, Reset, and Clock Management
SWPU177N – December 2009 – Revised November 2010
Copyright © 2009–2010, Texas Instruments Incorporated