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.

DMTimerNModuleClkConfig - does the L3(S)/L4/etc clock setup part need to be done every time?

I've noticed that all the DMTimer Module Clock config functions share a bunch of the same code, which unless I am mistaken is bringing up the L3/L4/etc interface clocks. If I was to call more than one of these functions (to init the clocks for more than one timer), that code will be run more than once. Is that OK? What are the consequences of this? Must it be the case?

Also, after the timer clock source is set and the module enabled, there are a few more while loops which look like they are watching for the clocks/modules to become active. Should this be done specifically after configuring the DMTimer (or any peripheral) clock source? Or is this code that could be moved with other code I mentioned above (if they can be separated)?

It sort of looks like they might have moved the active checks for the interconnects until after the DMTimer specific configuration just because the DMTimer configuration doesn't have to wait for the other config to be done, but we do want it all to be done before the function returns.

I'm writing a micro-kernel and would like to configure all the PLL's in one place if that's possible. I'm writing for a beaglebone black.