diff options
| author | Wolfram Sang <[email protected]> | 2015-09-03 22:20:09 +0200 |
|---|---|---|
| committer | Wolfram Sang <[email protected]> | 2015-10-09 22:30:53 +0100 |
| commit | 2bc3c5a8631db6d88f3a83188b069ca46b301315 (patch) | |
| tree | f13c2031a401eae4986a96dafe3631f8598fc862 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 344beeb23bfc11502fc54875f37ccdf51b6639b9 (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 <[email protected]>
Signed-off-by: Wolfram Sang <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions