diff options
| author | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2018-08-10 10:21:13 -0700 |
|---|---|---|
| committer | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2019-06-22 23:55:22 -0700 |
| commit | 2880dcf9cfc28a3803aee4c964743adbb66b0f1a (patch) | |
| tree | 7a226c1fdf2e92b52d3ea374926cb6d275c28fca /tools/perf/scripts/python | |
| parent | d3cc100069f945a392d6cde5ea326bb686418193 (diff) | |
Input: iforce - signal command completion from transport code
Signalling command completion from iforce_process_packet() does
not make sense, as not all transport use the same data path for
both commands and motion data form the device, that is why USB
code already has to signal command completion iforce_usb_out().
Let's move signalling completion into individual transport
modules.
Tested-by: Tim Schumacher <timschumi@gmx.de>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions