kernel_samsung_smdk4412/drivers/input, branch replicant-6.0 kernel/samsung/smdk4412 smdk4412: remove all touchscreen binary firmware from the kernel 2021-03-27T18:20:36+00:00 belgin belginstirbu@hotmail.com 2021-03-26T08:33:06+00:00 33b30af91e1a9858b2fa6dc87be00d3428bf18b7 The removed files have unclear licensing statements and don't come with the corresponding source code. So it's easier to just remove them than getting legal advice and trying to reconstruct their source code. These files are #include'd in touchscreen drivers (even the .c files), but as it happens, it was not necessary to touch those drivers because Replicant doesn't use them (they are not checked in the defconfig of any of the supported devices). That said, if anyone ever does use one of those drivers, it won't compile without changes. So basically, none of the binary firmwares that are deleted by this patch ever ended up on a device running Replicant anyway. Signed-off-by: belgin <belginstirbu@hotmail.com> Acked-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> 
The removed files have unclear licensing statements
and don't come with the corresponding source code.

So it's easier to just remove them than getting legal advice
and trying to reconstruct their source code.

These files are #include'd in touchscreen drivers
(even the .c files), but as it happens, it was not
necessary to touch those drivers because Replicant
doesn't use them (they are not checked in the defconfig
of any of the supported devices).

That said, if anyone ever does use one of those drivers,
it won't compile without changes.

So basically, none of the binary firmwares that are deleted
by this patch ever ended up on a device running Replicant
anyway.

Signed-off-by: belgin <belginstirbu@hotmail.com>
Acked-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
smdk4412: remove embedded synaptics touchscreen firmware 2020-12-17T05:09:06+00:00 belgin belginstirbu@hotmail.com 2020-12-09T16:31:09+00:00 43720e41c7f36873718fc24746277bbf7d24e6f1 The CMD_LIST commands implementations that enabled userspace to load firmwares were replaced by prints in order to be able to detect if userspace is using them or not. If they are used, then nonfree firmwares might also be shipped in userspace code. Signed-off-by: belgin <belginstirbu@hotmail.com> GNUtoo: re-added CMD_LIST commands and added related explanation. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> 
The CMD_LIST commands implementations that enabled
userspace to load firmwares were replaced by prints
in order to be able to detect if userspace is using
them or not. If they are used, then nonfree firmwares
might also be shipped in userspace code.

Signed-off-by: belgin <belginstirbu@hotmail.com>
GNUtoo: re-added CMD_LIST commands and added related explanation.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
input: cypress touchkey: cypressbln: also remove unused firmware loading code 2019-07-24T12:38:22+00:00 Denis 'GNUtoo' Carikli GNUtoo@cyberdimension.org 2019-04-08T17:47:11+00:00 e40b2fa239e15c3ea8ea9407be704882916bcacc Some of the files (issp_*) that are involved in the firmware loading have unclear licensing statements. Removing the problematic files and adapting the code to compile without them is easier and faster than getting legal advise to understand if the files are under a free software license or not. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> 
Some of the files (issp_*) that are involved in the firmware
loading have unclear licensing statements.

Removing the problematic files and adapting the code to compile
without them is easier and faster than getting legal advise to
understand if the files are under a free software license or not.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
input: cypress touchkey: cleanups: remove unused TEST_JIG_MODE 2019-07-24T12:38:21+00:00 Denis 'GNUtoo' Carikli GNUtoo@cyberdimension.org 2019-04-02T14:18:40+00:00 0ee78af736ce947d286d21b5fdc2c0212b2f8d38 TEST_JIG_MODE is not defined anywhere, so we can safely remove that code. The define name suggest that it was probably used during manufacturing tests. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> 
TEST_JIG_MODE is not defined anywhere, so we can safely remove
that code.

The define name suggest that it was probably used during
manufacturing tests.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
input: cypress touchkey: remove unused firmware loading code 2019-07-24T12:38:21+00:00 Denis 'GNUtoo' Carikli GNUtoo@cyberdimension.org 2019-03-26T20:24:39+00:00 1fe39350b36767cc60ae58c2b2ea5fa29d484be0 The firmware loading code is not used by any of the devices currently supported by Replicant. Some of the files (issp_*) that are involved in the firmware loading have unclear licensing statements. Removing the problematic files and adapting the code to compile without them is easier and faster than getting legal advise to understand if the files are under a free software license or not. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> 
The firmware loading code is not used by any of the devices
currently supported by Replicant.

Some of the files (issp_*) that are involved in the firmware
loading have unclear licensing statements.

Removing the problematic files and adapting the code to compile
without them is easier and faster than getting legal advise to
understand if the files are under a free software license or not.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
input: cypress touchkey: remove unused binary firmware data 2019-07-24T12:38:15+00:00 Fil Bergamo fil.bergamo@riseup.net 2019-01-14T23:04:10+00:00 160424ba716cde87e4ff213972a03388e90bf75e This removes some files that contain hex-encoded firmwares which lack their corresponding source code. They seem to only have been used during factory testing for the touch keys and they are are not needed during normal operation. Signed-off-by: Fil Bergamo <fil.bergamo@riseup.net> GNUtoo@cyberdimension.org: edited the commit message Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> 
This removes some files that contain hex-encoded firmwares
which lack their corresponding source code.

They seem to only have been used during factory testing for
the touch keys and they are are not needed during normal
operation.

Signed-off-by: Fil Bergamo <fil.bergamo@riseup.net>
GNUtoo@cyberdimension.org: edited the commit message
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Input: aiptek - fix crash on detecting device without endpoints 2016-05-17T12:11:13+00:00 Vladis Dronov vdronov@redhat.com 2015-12-01T21:09:17+00:00 55699ae6f09377fcce9af40f43b4e5e167421958 The aiptek driver crashes in aiptek_probe() when a specially crafted USB device without endpoints is detected. This fix adds a check that the device has proper configuration expected by the driver. Also an error return value is changed to more matching one in one of the error paths. Change-Id: I02fa4ffcbe9a71948947ef5baeb72632688d9d07 Reported-by: Ralf Spenneberg <ralf@spenneberg.net> Signed-off-by: Vladis Dronov <vdronov@redhat.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> 
The aiptek driver crashes in aiptek_probe() when a specially crafted USB
device without endpoints is detected. This fix adds a check that the device
has proper configuration expected by the driver. Also an error return value
is changed to more matching one in one of the error paths.

Change-Id: I02fa4ffcbe9a71948947ef5baeb72632688d9d07
Reported-by: Ralf Spenneberg <ralf@spenneberg.net>
Signed-off-by: Vladis Dronov <vdronov@redhat.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Input: aiptek - adjust error-handling code label 2016-05-17T12:11:13+00:00 Julia Lawall Julia.Lawall@lip6.fr 2012-04-24T05:26:58+00:00 24bbfe56b518e2a94c35a618becd7cd17ddc276a At the point of this error-handling code, aiptek->urb has been allocated, and it does not appear to be less necessary to free it here than in the error-handling code just below. Change-Id: I1b07d7cd62a3df78759dd5a9a5ad27e58350df01 Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> 
At the point of this error-handling code, aiptek->urb has been allocated,
and it does not appear to be less necessary to free it here than in the
error-handling code just below.

Change-Id: I1b07d7cd62a3df78759dd5a9a5ad27e58350df01
Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
cypress: Port BLN for smdk4210 2016-05-08T20:49:37+00:00 Arnab Chaudhuri coolguyforgenerationx@gmail.com 2016-05-04T10:10:00+00:00 dbabc204f2217b654d806a42163b46a6e77f0e7c BLN code originally by neldar. Adapted for SGSII by creams. Ported by gokhanmoral. Change-Id: I3e51026a9057be47586378994f61719177507b84 
BLN code originally by neldar. Adapted for SGSII by creams. Ported
by gokhanmoral.

Change-Id: I3e51026a9057be47586378994f61719177507b84
Input: add infrastructure for selecting clockid for event time stamps 2016-03-16T11:34:14+00:00 John Stultz john.stultz@linaro.org 2012-02-03T08:19:07+00:00 f0f6cbaf4d48a251a2a37078f82ae96c4f6079fe As noted by Arve and others, since wall time can jump backwards, it is difficult to use for input because one cannot determine if one event occurred before another or for how long a key was pressed. However, the timestamp field is part of the kernel ABI, and cannot be changed without possibly breaking existing users. This patch adds a new IOCTL that allows a clockid to be set in the evdev_client struct that will specify which time base to use for event timestamps (ie: CLOCK_MONOTONIC instead of CLOCK_REALTIME). For now we only support CLOCK_MONOTONIC and CLOCK_REALTIME, but in the future we could support other clockids if appropriate. The default remains CLOCK_REALTIME, so we don't change the ABI. Signed-off-by: John Stultz <john.stultz@linaro.org> Reviewed-by: Daniel Kurtz <djkurtz@google.com> Signed-off-by: Dmitry Torokhov <dtor@mail.ru> Conflicts: include/linux/input.h Change-Id: I7b9b442dcd7930a1e72c688327e6fb7275107128 
As noted by Arve and others, since wall time can jump backwards, it is
difficult to use for input because one cannot determine if one event
occurred before another or for how long a key was pressed.

However, the timestamp field is part of the kernel ABI, and cannot be
changed without possibly breaking existing users.

This patch adds a new IOCTL that allows a clockid to be set in the
evdev_client struct that will specify which time base to use for event
timestamps (ie: CLOCK_MONOTONIC instead of CLOCK_REALTIME).

For now we only support CLOCK_MONOTONIC and CLOCK_REALTIME, but
in the future we could support other clockids if appropriate.

The default remains CLOCK_REALTIME, so we don't change the ABI.

Signed-off-by: John Stultz <john.stultz@linaro.org>
Reviewed-by: Daniel Kurtz <djkurtz@google.com>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>

Conflicts:
	include/linux/input.h

Change-Id: I7b9b442dcd7930a1e72c688327e6fb7275107128