summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorWolfram Sang <wsa+renesas@sang-engineering.com>2015-11-19 16:56:46 +0100
committerWolfram Sang <wsa@the-dreams.de>2015-11-30 14:21:29 +0100
commitcc21d0b4b62e41e5013d763adade5ea4462c33a4 (patch)
tree215899eda93f0eab8c4fc75902b50d56e34f8b68 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentb9d0684c79c4b9d30ce0d47d3270493dd0e76e59 (diff)
i2c: rcar: init new messages in irq
Setting up new messages was done in process context while handling a message was in interrupt context. Because of the HW design, this IP core is sensitive to timing, so the context switches were too expensive. Move this setup to interrupt context as well. In my test setup, this fixed the occasional 'data byte sent twice' issue which a number of people have seen. It also fixes to send REP_START after a read message which was wrongly send as a STOP + START sequence before. Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions