The SIMCOP supports the STANDBY power management protocol. It is used by the SIMCOP to indicate when it has no more interconnect transactions to perform. This information is used at the ISS level to control the SIMCOP and ISS shut-down sequence. The SIMCOP does not have any internal wake-up events. DISCONNECT and IDLE protocols are not supported.
The typical SIMCOP shut-down sequence is:
- Software disables all SIMCOP submodules. This ensures the SIMCOP does not:
- Generate any traffic on its master port; SIMCOP asserts the MStandby signal.
- Generate new events (IRQs).
- Software clears all pending events at the SIMCOP level; all interrupt lines become inactive.
- Software initiates the SIMCOP shut-down sequence by writing the appropriate bit at the ISS level.
- ISS hardware:
- Disconnects the SIMCOP configuration port. Any access attempts to the SIMCOP are blocked at the ISS level. The DISCONNECT protocol is handled at the ISS level; the SIMCOP does not provide any handshake signals to support it.
- Waits until MStandby from SIMCOP is asserted (always true in a normal case because SIMCOP submodules are inactive)
- Asserts the SWait input of SIMCOP
- Cuts the SIMCOP clock
The typical SIMCOP enable sequence is:
- Software initiates the SIMCOP enable sequence by writing the appropriate bit at the ISS level.
- ISS hardware:
- Enables the SIMCOP clock
- Deasserts the SWait input of SIMCOP
- Connects the SIMCOP configuration port