• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 378 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP - AUTOIDLE bit

Yuvaraj Velumani
Intellectual 580 points
Other Parts Discussed in Thread: SYSCONFIG

I have found that there are several AUTOIDLE bit to control the clock & perform the modules in LOW - POWER State. Do we need to configure the individual modules AUTOIDLE bis in their respective Modules SYSCONFIG register or we can configure it in CM_AUTOIDLE_<power domain> register or we need to do on both. What is the difference in configuring the SYSCONFIG individually & the CM_AUTOIDLE register?

Ex: What is the difference in enabling PRCM.CM_AUTOIDLE1_CORE[15] AUTO_I2C1bit  & I2C1.I2C_SYSC[0] AUTOIDLE bit? or do we need to enable both?

  • 0
    Prodigy 140 points

    The Sysconfig register is specific to the IP(Peripheral). You must configure it for SmartIdle and configure the XX_ClockActivity (or whatever it is called) to turn off both FCLK and ICLK whenever PRCM executes the target-slave IDLEACK protocol.

    Therefore, in order to turn OFF a clock, configure SYSCONFIG as explained above and then turn OFF the FCLKEN/ ICLKEN at PRCM.

    The CM_AUTOIDLE is used when it is desired that PRCM itself powers down a domain. FCLKs must be turned OFF, ICLKs can stay on, but the AUTOIDLE of all ICLKS of a domain must remain set to 1. Thus when CLKSTCTRL is configured for h/w supervised transition, PRCM will transition the domain to a low power state as defined in PWRSTCTRL whenever it can.

    Good luck.

    SS