aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorGrygorii Strashko <[email protected]>2016-12-06 18:00:45 -0600
committerDavid S. Miller <[email protected]>2016-12-07 11:13:48 -0500
commit20138cf9efc1a761a17839581b0130d8e4209882 (patch)
tree922593476d473306781aeed5be9ded19b0ce81f1 /tools/perf/util/scripting-engines/trace-event-python.c
parent88f0f0b0bebfbe086dda853f591ae3a014b19e40 (diff)
net: ethernet: ti: cpts: fix overflow check period
The CPTS drivers uses 8sec period for overflow checking with assumption that CPTS retclk will not exceed 500MHz. But that's not true on some TI platforms (Kesytone 2). As result, it is possible that CPTS counter will overflow more than once between two readings. Hence, fix it by selecting overflow check period dynamically as max_sec_before_overflow/2, where max_sec_before_overflow = max_counter_val / rftclk_freq. Cc: John Stultz <[email protected]> Cc: Thomas Gleixner <[email protected]> Signed-off-by: Grygorii Strashko <[email protected]> Acked-by: Richard Cochran <[email protected]> Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions