Input: iforce - signal command completion from transport code
authorDmitry Torokhov <dmitry.torokhov@gmail.com>
Fri, 10 Aug 2018 17:21:13 +0000 (10:21 -0700)
committerDmitry Torokhov <dmitry.torokhov@gmail.com>
Sun, 23 Jun 2019 06:55:22 +0000 (23:55 -0700)
commit2880dcf9cfc28a3803aee4c964743adbb66b0f1a
tree7a226c1fdf2e92b52d3ea374926cb6d275c28fca
parentd3cc100069f945a392d6cde5ea326bb686418193
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>
drivers/input/joystick/iforce/iforce-packets.c
drivers/input/joystick/iforce/iforce-serio.c