A.1.2 Clock control Q-Channel signals

For each of the output clocks, except for FCLK and SYSCLK, the subsystem provides a Q-Channel interface to allow expansion logic to control the availability of each clock output. These are used to support hierarchical clock gating and are backed up by EXPCLKRDY.

The following list shows the Q-Channel interface for the output clocks, and their signals:

  • Base element SYSCLK Q-Channel interface for SYSSYSCLK which includes:

    • SYSSYSCLKQREQn output,

    • SYSSYSCLKQACCEPTn input,
    • SYSSYSCLKQDENY input,
    • SYSSYSCLKQACTIVE input.
  • Base element FCLK Q-Channel interface for SYSFCLK which includes:

    • SYSFCLKQREQn output,

    • SYSFCLKQACCEPTn input,
    • SYSFCLKQDENY input,
    • SYSFCLKQACTIVE input.
  • Crypto element SYSCLK Q-Channel interface for CRYPTOSYSCLK which includes:

    • CRYPTOSYSCLKQREQn output,

    • CRYPTOSYSCLKQACCEPTn input,
    • CRYPTOSYSCLKQDENY input,
    • CRYPTOSYSCLKQACTIVE input.
  • CPU and Debug element Power Integration Q-Channel interface for CPUDEBUGPIKCLK which includes:

    • CPUDEBUGPIKCLKQREQn output,

    • CPUDEBUGPIKCLKQACCEPTn input,
    • CPUDEBUGPIKCLKQDENY input,
    • CPUDEBUGPIKCLKQACTIVE input.
  • Base, Crypto and System Power Integration Q-Channel interface for BCRYPTOSPIKCLK which includes:

    • BCRYPTOSPIKCLKQREQn output,

    • BCRYPTOSPIKCLKQACCEPTn input,
    • BCRYPTOSPIKCLKQDENY input,
    • BCRYPTOSPIKCLKQACTIVE input.

If an interface is not used, then QACTIVE and QDENY signals must be tied LOW and the QREQn output looped back into its QACCEPTn input.

The subsystem does not provide a Q-Channel interface to control DEBUGSYSCLK and DEBUGFCLK. These clocks are controlled by the debug power domain, PD_DEBUG, and as long as the debug power domain is enabled, DEBUGSYSCLK and DEBUGFCLK are active.

Note:

The Q-Channel interfaces do not support waking the system from hibernation. To wake from hibernation, you must use the EWC, power control Q-Channel interfaces, or the PDEXPIN inputs.

The following interfaces are each synchronous to the clock that it controls, with only their respective QACTIVE signal being asynchronous:

  • Base Element SYSCLK Q-Channel interface for SYSSYSCLK.
  • Base Element FCLK Q-Channel interface for SYSFCLK.
  • Crypto Element SYSCLK Q-Channel interface for CRYPTOSYSCLK.

The following interfaces are asynchronous:

  • CPU and Debug Element Power Integration Q-Channel interface for CPUDEBUGPIKCLK.
  • Base, Crypto and System Power Integration Q-Channel interface for BCRYPTOSPIKCLK.

For more details on the Q-Channel protocol, see the AMBA® Low Power Interface Specification Arm® Q-Channel and P-Channel Interfaces.

Non-ConfidentialPDF file icon PDF version101104_0200_00_en
Copyright © 2016–2018 Arm Limited or its affiliates. All rights reserved.