> however, the CLOCKACTIVITY change on clk_enable()/clk_disable() in that
> code currently seems pointless, so it has been excluded until more
> information is available from TI or until problems are encountered.
IIRC CLOCKACTIVITY settings mainly had to do with if I2C was master or slave. Part of TI patch set allows slave mode. Seems like some GPS chip needed to be master or something along those lines. One of the TI-ASP groups needed it.
Guidance was you should treat internal clocks differently at ocp-segment-idle-request time if you were the one generating the clock or it was coming in from the outside world. It was reported not doing this correctly would result in possible data being lost.
McBSP and audio have a similar relationship when you do master/slave and your sample clock comes from the outside.
------------
GPTIMER CLOCKACTIVTY is more easily understood. At ocp-segment-idle-request for the system heart beat you want to keep that FCLK running so you set it so. There could be a case with other timers that you just let them be shut down.
Regards,
Richard W.
��.n��������+%������w��{.n�����{�������ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
