Normally we enable the usage Peripheral at the start of application.
One question, can we disable the Peripheral at the runtime?
And enable the Peripheral at the runtime?
Take the ePWM module as example.

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.
Normally we enable the usage Peripheral at the start of application.
One question, can we disable the Peripheral at the runtime?
And enable the Peripheral at the runtime?
Take the ePWM module as example.

For the special purpose such as low power consideration, When one interrupt coming, then enable the ePWM module, after the operation, then diasble the ePWM module.
I have the concering, when disbale the ePWM module ,will the releated PWM registers reset to default value or will they keep the value before diable.
Hello,
TI does not recommend disabling the ePWM module during runtime, and this is generally not characterized. However, register contents shouldn't be erased by stopping the clock (which is what the SysCTL_disablePeripheral function does). Disabling the ePWM during runtime is most often performed using trip zone one-shot-trip configurations, in my experience.
For low power, have you considered using the device low power modes? Refer to the device TRM, section 3.11, which describes both of the device low power modes, one of which halts peripheral clocks as well.
Regards,
Jason Osborn
Note: Key takeaways from this post are bolded.