14:19 <jmleo> jnettlet: back here, will probably be better you are right

14:20 <jnettlet> jmleo, great welcome

14:20 <jmleo> jnettlet: right now, there is no way to have VPU at 352MHz when CPU is at 792MHz or 1GHz on mainline ?

14:20 <jmleo> it woule be great to have it scaled in accordance with cpufreq

14:21 <jmleo> but I don't know how it works and what needs to be done in order to have this...

14:21 <jnettlet> well it should really scale based on content type, or based on workload

14:22 <jmleo> jnettlet: on workload, this sounds like cpufreq

14:23 <jnettlet> jmleo, well not really. In theory you can have the VPU decode and directly output to the IPU overlay all via DMA which requires little CPU

14:23 <jnettlet> or less CPU

14:23 <jnettlet> but if you are decoding 1080p60 content you will need to have the VPU clocked to 352Mhz

15:00 <jmleo> jnettlet: but you can't really know that from a kernel perspective... or in the coda driver maybe...

15:03 <jmleo> jnettlet: how can I test this, how can I change the VPU clock ? I don't know how it works exactly, what is the correct doc for this ?

15:52 <jnettlet> jmleo, sorry about that. I had to run out. You should reference the freescale kernel patch for 352mhz support. Then within the code driver you will be able to change the frequency via the common clock infrastructure with clk_set