69rlq62d-f714peg4 * Memec (Headquar
ter
Tec
h,
Insight,
Impact
MAR
VELL CONFIDENTIAL,
UNDER ND
A# 12101050
69rlq62d-f714peg4 * Memec (Headquar
ter
s) - Unique
Tec
Insight,
Impact
MAR
VELL CONFIDENTIAL,
UNDER ND
A# 12101050
69r
lq62d-f714peg4 * Memec (Headquar
ters) - Unique
T
ech, Insight, Impact * UNDER ND
A# 12101050
MAR
VELL CONFIDENTIAL - UNA
UTHORIZED DISTRIB
UTION OR USE STRICTL
Y PR
OHIBITED
PXA300 Processor and PXA310 Processor
Vol. I: System and Timer Configuration Developers Manual
Doc. No. MV-TBD-00 Rev. A
CONFIDENTIAL
Copyright © 2006 Marvell
Page 118
Document Classification: Proprietary Information
December 13, 2006, Preliminary
Not approved by Document Control. For review only.
4.11
Wakeup Detection
There are three main sets of wakeup detection: services, peripheral controller, and generic wakeups. A wakeup in
this context is not necessarily the same as an interrupt.
4.11.1
Services Wakeups
These are separate wake-up signals that go directly into the services module. These wake-up signals include
EXT_WAKEUP<1:0> signals and internal RTC alarm wake ups, which are described and defined in the
Chapter 8, “Services Power Management Unit”
with detailed register information in
Wake-Up Enable Register (PWER)”
,
Chapter 8, “Power Manager Wake-Up Status Register (PWSR)”
, and
Chapter 8, “Power Manager EXT_WAKEUP<1:0> Control Register (PECR)”
.
4.11.2
Peripheral Controller Wakeups
There are multiple peripheral controller wakeup events (these include functions such as USB client, keypad,
USIM, plus others) that are described and defined in the
Chapter 9, “Slave Power Management Unit,”
with
detailed register information in
Chapter 9, “Application Subsystem Wake-Up from D3 Enable Register
through
Chapter 9, “Application Subsystem Wake-Up from D1 to D0 Status Register (AD1D0SR)”
provides a summary of the peripheral controller wake ups.
These peripheral controller wake ups are considered first-level wakeup sources because they require reading
only one register, ADxSR, to understand what caused the wakeup. For example: After waking from S2/D3/C4
mode, reading the AD3SR register and finding bit 19 set indicates that activity on the GPIO pin assigned to the
U_DETECT or U_IO alternate functions of the CARD1 controller caused the wakeup event (refer to
).
L
Table 4-9. Peripheral Controller Wake Ups (Sheet 1 of 2)
Unit
Events or Alternate Functions
Slave Power Management
Unit Dedicated Register
Bits
USBOTG
USB Host Port 2 integrated transceiver event
ADxER[16] and ADxSR[16]
CARD1
U_DETECT and U_IO
ADxER[19] and ADxSR[19]
CARD2
SC_DETECT and SCIO
ADxER[20] and ADxSR[20]
Direct Keypad
KP_DKIN<7:0>
ADxER[21] and ADxSR[21]
USB Host Port 2
PXA300 only
USB_P2_1, USB_P2_2, USB_P2_3, USB_P2_4,
USB_P2_5, and USB_P2_7
ADxER[22] and ADxSR[22]
USB Host Port 2
PXA310 only
USB_P2_1, USB_P2_3, USB_P2_4, USB_P2_5,
USB_P2_6,
ADxER[22] and ADxSR[22]
USB Host Port 3
USB_P3_1, USB_P3_3, and USB_P3_5
ADxER[23] and ADxSR[23]
USB 2.0 Client
PXA300 only
UTM_CLK, UTM_RXVALID, UTM_RXACTIVE, and
UTM_LINESTATE<1:0>
ADxER[26] and ADxSR[26]