Only certain eTPU channels can trigger DMAs or directly trigger eQADC conversions. In order to keep the host processor out of the loop, these eTPU channels would need to be used to generate your PWMs. For example, on the MPC5777C, only the following eTPU_A channels can trigger a DMA directly: 0, 1, 2, 12, 13, 14, 15, 28, 29. Or, the following MPC5777C eTPU_A channels can trigger an eQADC conversion:
eQADC (A or B), CFIFO0 : 28, 29, 30 31
eQADC (A or B), CFIFO1 : 7, 28, 29, 30 31
eQADC (A or B), CFIFO2 : 14, 28, 29, 30 31
eQADC (A or B), CFIFO3 : 22, 28, 29, 30 31
eQADC (A or B), CFIFO4 : 27, 28, 29, 30 31
eQADC (A or B), CFIFO5 : 26, 28, 29, 30 31
Assuming you are using the standard PWM eTPU function, it only generates a data transfer (DMA) interrupt on the frame edge (the edge that occurs every period, not the duty cycle edge that floats around). Thus to measure on every signal edge as you note, you would need to use the signal to trigger the eQADC, so a pretty limited set of channels can be utilized.
In order to use the data transfer interrupt capability (or channel interrupt, which would force the host processor to be in the loop) and still be able to measure on every PWM edge, would require a small change the PWM eTPU code (issue interrupts on the duty cycle edge).
John Diener