linux.git/drivers/input/joystick, branch v5.3-rc2

Input: iforce - remove empty multiline comments

2019-07-15T16:43:13+00:00

Those are remnants of the SPDX identifier migration, which haven't been
removed properly.

Signed-off-by: Tim Schumacher 
Signed-off-by: Dmitry Torokhov

Merge tag 'v5.2' into next

2019-07-15T16:42:32+00:00

Sync up with mainline to resolve conflicts in iforce driver.

Input: iforce - add the Saitek R440 Force Wheel

2019-06-23T06:55:50+00:00

This is added based on the fact that this is an iforce-based device and
that the Windows driver for the R440 works for the Logitech WingMan Formula
Force after replacing the device/vendor IDs.

Signed-off-by: Tim Schumacher 
Signed-off-by: Dmitry Torokhov

Input: iforce - use unaligned accessors, where appropriate

2019-06-23T06:55:49+00:00

Instead of open-coding conversion from/to little-endian, let's
use proper accessors.

Tested-by: Tim Schumacher 
Signed-off-by: Dmitry Torokhov

Input: iforce - drop couple of temps from transport code

2019-06-23T06:55:49+00:00

Transport initialization code now deals mostly with transport-specific
data, so we can drop couple of temporary variables.

Tested-by: Tim Schumacher 
Signed-off-by: Dmitry Torokhov

Input: iforce - drop bus type from iforce structure

2019-06-23T06:55:48+00:00

It is not needed anymore as behavior is controlled by the transport
operations set up for given device.

Tested-by: Tim Schumacher 
Signed-off-by: Dmitry Torokhov

Input: iforce - use DMA-safe buffores for USB transfers

2019-06-23T06:55:48+00:00

USB transport has to use cache line-aligned buffers for transfers to avoid
DMA issues; serio doe snot have such restrictions. Let's move "data_in"
buffer from main driver structure into transport modules and make sure USB
requirements are respected.

Tested-by: Tim Schumacher 
Signed-off-by: Dmitry Torokhov

Input: iforce - allow callers supply data buffer when fetching device IDs

2019-06-23T06:55:23+00:00

We want to move buffer handling into transport layers as the properties of
buffers (DMA-safety, alignment, etc) are different for different
transports. To allow this, let's allow caller to specify their own buffers
for the results of iforce_get_id_packet() and let transport drivers to
figure what buffers they need to use for transfers.

Tested-by: Tim Schumacher 
Signed-off-by: Dmitry Torokhov

Input: iforce - only call iforce_process_packet() if initialized

2019-06-23T06:55:23+00:00

It is excessive to check if device is fully initialized in
iforce_process_packet(), as for USB-conected devices we do not start
collecting reports until the device is fully initialized.

Let's change serio transport code to not call iforce_process_packet()
until device initialization is done.

Tested-by: Tim Schumacher 
Signed-off-by: Dmitry Torokhov

Input: iforce - signal command completion from transport code

2019-06-23T06:55:22+00:00

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 
Signed-off-by: Dmitry Torokhov