omapconf/omapconf — pull request #4 by fturgis (2012-10-08 11:32:27+00:00)
Title: API improvement to leverage 8 statcoll counters in flexible manner

- API:
* initiators names now accepted: alldmm, ma_mpu, dss, iva, ...
* configuration of filtering of transaction and emif is now possible through --t and --p options
* 8 counters from 0 to 7 can now be used (last 2 can't filter initiator and transaction r/w/r+w, use them for alldmm and ma_mpu)
* per counter API: --m7 dss --tr7 r+w --q7 emif2 ... including "all counters" API -m dss --tr r+w -q emif2
* parameters error checking added and detailed configuration description per counter printed at beginning of log

- Improvements
* Error checking:
+ tool detects when 1 counter overflowed at 2^32 and suggests user to not trust results
+ tool detects HW bug where next capture is < previous capture. Tool fixes it by setting next capture=previous capture (no info is lost, just accuracy of this capture)
* Post-processing: each counter can be drawn independently. Aggregates can also be drawn (EMIF1+EMIF2 -> All EMIF, R EMIF1, R EMIF2, W EMIF1, W EMIF2 -> Rd-Wr, All EMIF, ...). User can choose to display only counter graphs, only aggregates or all
* added missing USB initiators including USB3
* "-a 1" output log correctly dumps initiator names (and includes correct transaction qualifiers and probes)

- HW IP reset:
* HW IP is now reset by default every second (overflow can then happen only if 1 EMIF sustains 4GB/s during 1 second)
* --overflow_delay option can tune this reset rate
* -o -t options still available (allowing to reset less IP but with much more complexity), 2 counters can now be monitored with different thresholds
* removed trace that informs about HW IP reset