Evolution-X-Devices/kernel_xiaomi_violet
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
806,563 Commits 1 Branch 0 Tags
udc
Commit Graph

6247 Commits

Author SHA1 Message Date
chiteroman
f780c61489 drivers: Add KernelSU hooks 
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
 2024-07-07 19:26:15 +02:00
Mohammad Kibria
af6312da10 Merge branch 'linux-4.14.y' of https://github.com/openela/kernel-lts.git 2024-06-03 06:00:40 +00:00
Kunwu Chan
c6d084381d Input: synaptics-rmi4 - fail probing if memory allocation for "phys" fails 
[ Upstream commit bc4996184d56cfaf56d3811ac2680c8a0e2af56e ]

While input core can work with input->phys set to NULL userspace might
depend on it, so better fail probing if allocation fails. The system must
be in a pretty bad shape for it to happen anyway.

Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
Link: https://lore.kernel.org/r/20240117073124.143636-1-chentao@kylinos.cn
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
(cherry picked from commit 004402ec227732308871a6127f0b967cf2a293cd)
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
 2024-05-30 09:00:44 +00:00
kibria 5
62d0d5206b Merge branch 'linux-4.14.y' of https://github.com/openela/kernel-lts.git 2024-04-21 19:22:27 +00:00
Uwe Kleine-König
243004088d Input: gpio_keys_polled - suppress deferred probe error for gpio 
[ Upstream commit 963465a33141d0d52338e77f80fe543d2c9dc053 ]

On a PC Engines APU our admins are faced with:

	$ dmesg | grep -c "gpio-keys-polled gpio-keys-polled: unable to claim gpio 0, err=-517"
	261

Such a message always appears when e.g. a new USB device is plugged in.

Suppress this message which considerably clutters the kernel log for
EPROBE_DEFER (i.e. -517).

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
Link: https://lore.kernel.org/r/20240305101042.10953-2-u.kleine-koenig@pengutronix.de
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
(cherry picked from commit a215f042a7f57346fd5430e84f81f822e84975b5)
Signed-off-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
 2024-04-16 09:45:17 +00:00
kibria 5
c2c0eb0cd8 Merge branch 'linux-4.14.y' of https://github.com/openela/kernel-lts.git 2024-03-28 16:32:42 +00:00
Neeraj Upadhyay
82babd681b Makefile: Remove -fno-builtin cflag 
Remove -fno-builtin cflag, to fix performance regression,
observed with this flag enabled. Also, fix the compilation
errors observed after removing the flag.

Change-Id: I515a4d043639109298008f95a25d8ed70417bdd8
Signed-off-by: Neeraj Upadhyay <neeraju@codeaurora.org>
 2024-03-28 16:23:43 +00:00
kibria5
0a567c6183 [SQUASH] Remove KernelSU 
Revert "ARM64: configs: violet: Enable OverlayFS options"

This reverts commit e63541d772.

Revert "KSU: Clone KernelSU repository"

This reverts commit 279f3f5f6c.

Revert "drivers: input: add missing kernelsu hooks"

This reverts commit 246d06a7e8.

Revert "fs/stat.c: Added flags"

This reverts commit f4fe4e231c.

Revert "defconfig: disable kprobes"

This reverts commit a7ec739901.

Revert "KSU: added kernelSU support"

This reverts commit 0740fed05a.

Signed-off-by: kibria5 <mdkibria687@gmail.com>
 2024-03-17 06:22:14 +00:00
Hans de Goede
eebb66beca Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID 
commit 683cd8259a9b883a51973511f860976db2550a6e upstream.

After commit 936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in
translated mode") the keyboard on Dell XPS 13 9350 / 9360 / 9370 models
has stopped working after a suspend/resume.

The problem appears to be that atkbd_probe() fails when called
from atkbd_reconnect() on resume, which on systems where
ATKBD_CMD_GETID is skipped can only happen by ATKBD_CMD_SETLEDS
failing. ATKBD_CMD_SETLEDS failing because ATKBD_CMD_GETID was
skipped is weird, but apparently that is what is happening.

Fix this by also skipping ATKBD_CMD_SETLEDS when skipping
ATKBD_CMD_GETID.

Fixes: 936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")
Reported-by: Paul Menzel <pmenzel@molgen.mpg.de>
Closes: https://lore.kernel.org/linux-input/0aa4a61f-c939-46fe-a572-08022e8931c7@molgen.mpg.de/
Closes: https://bbs.archlinux.org/viewtopic.php?pid=2146300
Closes: https://bugzilla.kernel.org/show_bug.cgi?id=218424
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=2260517
Tested-by: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: stable@vger.kernel.org
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Link: https://lore.kernel.org/r/20240126160724.13278-2-hdegoede@redhat.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit 0be65249b72efb7d6eec6aabbb9901f22b4c9856)
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
 2024-03-08 08:21:37 +00:00
kibria5
dfae755e15 Revert "[SQUASH] Remove KernelSU" 
This reverts commit 13fab8de15.
 2024-02-14 17:09:23 +00:00
Hans de Goede
8f95561662 Input: atkbd - use ab83 as id when skipping the getid command 
commit 58f65f9db7e0de366a5a115c2e2c0703858bba69 upstream.

Barnabás reported that the change to skip the getid command
when the controller is in translated mode on laptops caused
the Version field of his "AT Translated Set 2 keyboard"
input device to change from ab83 to abba, breaking a custom
hwdb entry for this keyboard.

Use the standard ab83 id for keyboards when getid is skipped
(rather then that getid fails) to avoid reporting a different
Version to userspace then before skipping the getid.

Fixes: 936e4d49ecbc ("Input: atkbd - skip ATKBD_CMD_GETID in translated mode")
Reported-by: Barnabás Pőcze <pobrn@protonmail.com>
Closes: https://lore.kernel.org/linux-input/W1ydwoG2fYv85Z3C3yfDOJcVpilEvGge6UGa9kZh8zI2-qkHXp7WLnl2hSkFz63j-c7WupUWI5TLL6n7Lt8DjRuU-yJBwLYWrreb1hbnd6A=@protonmail.com/
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Link: https://lore.kernel.org/r/20240116204325.7719-1-hdegoede@redhat.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit 6c42ba1fc7d39b1d72c1adc43ea2e519f5450b3c)
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
 2024-02-02 11:33:44 +00:00
Luca Weiss
b2c25c249b Input: xpad - add Razer Wolverine V2 support 
[ Upstream commit c3d1610345b79cbe29ef6ca04a4780eff0d360c7 ]

Add the VID and PID of Razer Wolverine V2 to xpad_device.

Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
Link: https://lore.kernel.org/r/20231125-razer-wolverine-v2-v1-1-979fe9f9288e@z3ntu.xyz
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
(cherry picked from commit 01a92b3c981219d22f16bdc612e9a2afa515a5dd)
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
 2024-02-02 11:33:37 +00:00
Hans de Goede
f56eab3175 Input: atkbd - skip ATKBD_CMD_GETID in translated mode 
[ Upstream commit 936e4d49ecbc8c404790504386e1422b599dec39 ]

There have been multiple reports of keyboard issues on recent laptop models
which can be worked around by setting i8042.dumbkbd, with the downside
being this breaks the capslock LED.

It seems that these issues are caused by recent laptops getting confused by
ATKBD_CMD_GETID. Rather then adding and endless growing list of quirks for
this, just skip ATKBD_CMD_GETID alltogether on laptops in translated mode.

The main goal of sending ATKBD_CMD_GETID is to skip binding to ps/2
mice/touchpads and those are never used in translated mode.

Examples of laptop models which benefit from skipping ATKBD_CMD_GETID:

* "HP Laptop 15s-fq2xxx", "HP laptop 15s-fq4xxx" and "HP Laptop 15-dy2xxx"
  models the kbd stops working for the first 2 - 5 minutes after boot
  (waiting for EC watchdog reset?)

* On "HP Spectre x360 13-aw2xxx" atkbd fails to probe the keyboard

* At least 9 different Lenovo models have issues with ATKBD_CMD_GETID, see:
  https://github.com/yescallop/atkbd-nogetid

This has been tested on:

1. A MSI B550M PRO-VDH WIFI desktop, where the i8042 controller is not
   in translated mode when no keyboard is plugged in and with a ps/2 kbd
   a "AT Translated Set 2 keyboard" /dev/input/event# node shows up

2. A Lenovo ThinkPad X1 Yoga gen 8 (always has a translated set 2 keyboard)

Reported-by: Shang Ye <yesh25@mail2.sysu.edu.cn>
Closes: https://lore.kernel.org/linux-input/886D6167733841AE+20231017135318.11142-1-yesh25@mail2.sysu.edu.cn/
Closes: https://github.com/yescallop/atkbd-nogetid
Reported-by: gurevitch <mail@gurevit.ch>
Closes: https://lore.kernel.org/linux-input/2iAJTwqZV6lQs26cTb38RNYqxvsink6SRmrZ5h0cBUSuf9NT0tZTsf9fEAbbto2maavHJEOP8GA1evlKa6xjKOsaskDhtJWxjcnrgPigzVo=@gurevit.ch/
Reported-by: Egor Ignatov <egori@altlinux.org>
Closes: https://lore.kernel.org/all/20210609073333.8425-1-egori@altlinux.org/
Reported-by: Anton Zhilyaev <anton@cpp.in>
Closes: https://lore.kernel.org/linux-input/20210201160336.16008-1-anton@cpp.in/
Closes: https://bugzilla.redhat.com/show_bug.cgi?id=2086156
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Link: https://lore.kernel.org/r/20231115174625.7462-1-hdegoede@redhat.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
(cherry picked from commit eb59410d1cca3f1223b65e7562dc0d9acae26b39)
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
 2024-02-02 11:33:36 +00:00
kibria 5
5b841b2619 Merge tag 'v4.14.335' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git 
This is the 4.14.335 stable release
 2024-01-08 19:51:18 +00:00
Haoran Liu
3730466598 Input: ipaq-micro-keys - add error handling for devm_kmemdup 
[ Upstream commit 59b6a747e2d39227ac2325c5e29d6ab3bb070c2a ]

Check the return value of i2c_add_adapter. Static analysis revealed that
the function did not properly handle potential failures of
i2c_add_adapter, which could lead to partial initialization of the I2C
adapter and unstable operation.

Signed-off-by: Haoran Liu <liuhaoran14@163.com>
Link: https://lore.kernel.org/r/20231203164653.38983-1-liuhaoran14@163.com
Fixes: d7535ffa42 ("Input: driver for microcontroller keys on the iPaq h3xxx")
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
 2024-01-08 11:25:03 +01:00
adi8900
b8c1fa12af treewide: Add moar prototypes to functions 
* New clang moment

Signed-off-by: adi8900 <adrianszymanski242@gmail.com>
 2023-12-19 16:26:22 +00:00
adi8900
bb696ecdf7 treewide: Add prototypes to function declarations to fix build errors 
Signed-off-by: adi8900 <adrianszymanski242@gmail.com>
 2023-12-19 16:26:22 +00:00
kibria5
13fab8de15 [SQUASH] Remove KernelSU 
Revert "ARM64: configs: violet: Enable OverlayFS options"

This reverts commit e63541d772.

Revert "KSU: Clone KernelSU repository"

This reverts commit 279f3f5f6c.

Revert "drivers: input: add missing kernelsu hooks"

This reverts commit 246d06a7e8.

Revert "fs/stat.c: Added flags"

This reverts commit f4fe4e231c.

Revert "defconfig: disable kprobes"

This reverts commit a7ec739901.

Revert "KSU: added kernelSU support"

This reverts commit 0740fed05a.

Signed-off-by: kibria5 <mdkibria687@gmail.com>
 2023-12-16 16:44:10 +00:00
kibria 5
c1f4cdfcde Merge tag 'v4.14.329' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git 
This is the 4.14.329 stable release
 2023-11-08 17:10:57 +00:00
AiLiTa
2c048e5a5e touchscreen: nvt_touch_*: Fix size argument too large 
From clang warns:

../drivers/input/touchscreen/nvt_touch_f7b/nt36xxx_mp_ctrlram.c:1426:3: warning: 'snprintf' size argument is too large; destination buffer has size 32, but size argument is 4096 [-Wfortify-source]
                snprintf(mpcriteria, PAGE_SIZE, "novatek-mp-criteria-%04X", ts->nvt_pid);
                ^
../drivers/input/touchscreen/nvt_touch_f7b/nt36xxx_mp_ctrlram.c:1637:3: warning: 'snprintf' size argument is too large; destination buffer has size 32, but size argument is 4096 [-Wfortify-source]
                snprintf(mpcriteria, PAGE_SIZE, "novatek-mp-criteria-%04X", ts->nvt_pid);
                ^
2 warnings generated.

Signed-off-by: Nur Tantio Pratomo <tantio86@gmail.com>
Signed-off-by: Reinazhard <reinazhard@gmail.com>
Signed-off-by: kibria5 <mdkibria687@gmail.com>
 2023-11-08 16:56:24 +00:00
Davide Garberi
e53a4161ee drivers: input: touchscreen: focal_ft8719_e7b: Fix Wfortify-source warnings 
../drivers/input/touchscreen/ft8719_touch_f7b/focaltech_ex_fun.c:159:9: warning: 'snprintf' size argument is too large; destination buffer has size 25, but size argument is 4096 [-Wfortify-source]
        snprintf(tmp, PAGE_SIZE, "%s", writebuf + 1);
        ^
../drivers/input/touchscreen/ft8719_touch_f7b/focaltech_ex_fun.c:833:5: warning: 'snprintf' size argument is too large; destination buffer has size 128, but size argument is 4096 [-Wfortify-source]
    snprintf(fwname, PAGE_SIZE, "%s", buf);
    ^
../drivers/input/touchscreen/ft8719_touch_f7b/focaltech_ex_fun.c:876:5: warning: 'snprintf' size argument is too large; destination buffer has size 128, but size argument is 4096 [-Wfortify-source]
    snprintf(fwname, PAGE_SIZE, "%s", buf);
    ^
3 warnings generated.

Change-Id: I7445a37c618e83209ec2b6cf2c00b64bd77b5f0b
Signed-off-by: HeroBuxx <me@herobuxx.me>
Signed-off-by: kibria5 <mdkibria687@gmail.com>
 2023-11-08 16:56:24 +00:00
Dmitry Torokhov
365fbb85bb Input: synaptics-rmi4 - handle reset delay when using SMBus trsnsport 
[ Upstream commit 5030b2fe6aab37fe42d14f31842ea38be7c55c57 ]

Touch controllers need some time after receiving reset command for the
firmware to finish re-initializing and be ready to respond to commands
from the host. The driver already had handling for the post-reset delay
for I2C and SPI transports, this change adds the handling to
SMBus-connected devices.

SMBus devices are peculiar because they implement legacy PS/2
compatibility mode, so reset is actually issued by psmouse driver on the
associated serio port, after which the control is passed to the RMI4
driver with SMBus companion device.

Note that originally the delay was added to psmouse driver in
92e24e0e57f7 ("Input: psmouse - add delay when deactivating for SMBus
mode"), but that resulted in an unwanted delay in "fast" reconnect
handler for the serio port, so it was decided to revert the patch and
have the delay being handled in the RMI4 driver, similar to the other
transports.

Tested-by: Jeffery Miller <jefferymiller@google.com>
Link: https://lore.kernel.org/r/ZR1yUFJ8a9Zt606N@penguin
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
 2023-11-08 11:21:08 +01:00
Matthias Berndt
fe1d40fa6d Input: xpad - add PXN V900 support 
commit a65cd7ef5a864bdbbe037267c327786b7759d4c6 upstream.

Add VID and PID to the xpad_device table to allow driver to use the PXN
V900 steering wheel, which is XTYPE_XBOX360 compatible in xinput mode.

Signed-off-by: Matthias Berndt <matthias_berndt@gmx.de>
Link: https://lore.kernel.org/r/4932699.31r3eYUQgx@fedora
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 2023-10-25 11:13:30 +02:00
Javier Carrasco
8677575c4f Input: powermate - fix use-after-free in powermate_config_complete 
commit 5c15c60e7be615f05a45cd905093a54b11f461bc upstream.

syzbot has found a use-after-free bug [1] in the powermate driver. This
happens when the device is disconnected, which leads to a memory free from
the powermate_device struct.  When an asynchronous control message
completes after the kfree and its callback is invoked, the lock does not
exist anymore and hence the bug.

Use usb_kill_urb() on pm->config to cancel any in-progress requests upon
device disconnection.

[1] https://syzkaller.appspot.com/bug?extid=0434ac83f907a1dbdd1e

Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Reported-by: syzbot+0434ac83f907a1dbdd1e@syzkaller.appspotmail.com
Link: https://lore.kernel.org/r/20230916-topic-powermate_use_after_free-v3-1-64412b81a7a2@gmail.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 2023-10-25 11:13:30 +02:00
kibria 5
95e9585fdb Merge tag 'v4.14.322'of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git 
This is the 4.14.322 stable release
 2023-08-12 12:00:14 +00:00
Marek Vasut
89d454d5f4 Input: adxl34x - do not hardcode interrupt trigger type 
[ Upstream commit e96220bce5176ed2309f77f061dcc0430b82b25e ]

Instead of hardcoding IRQ trigger type to IRQF_TRIGGER_HIGH, let's
respect the settings specified in the firmware description.

Fixes: e27c729219 ("Input: add driver for ADXL345/346 Digital Accelerometers")
Signed-off-by: Marek Vasut <marex@denx.de>
Acked-by: Michael Hennerich <michael.hennerich@analog.com>
Link: https://lore.kernel.org/r/20230509203555.549158-1-marex@denx.de
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
 2023-08-11 11:33:36 +02:00
Luca Weiss
6939d5a953 Input: drv260x - sleep between polling GO bit 
[ Upstream commit efef661dfa6bf8cbafe4cd6a97433fcef0118967 ]

When doing the initial startup there's no need to poll without any
delay and spam the I2C bus.

Let's sleep 15ms between each attempt, which is the same time as used
in the vendor driver.

Fixes: 7132fe4f56 ("Input: drv260x - add TI drv260x haptics driver")
Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
Link: https://lore.kernel.org/r/20230430-drv260x-improvements-v1-2-1fb28b4cc698@z3ntu.xyz
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
 2023-08-11 11:33:36 +02:00
Kees Cook
d68627697d treewide: Remove uninitialized_var() usage 
commit 3f649ab728cda8038259d8f14492fe400fbab911 upstream.

Using uninitialized_var() is dangerous as it papers over real bugs[1]
(or can in the future), and suppresses unrelated compiler warnings
(e.g. "unused variable"). If the compiler thinks it is uninitialized,
either simply initialize the variable or make compiler changes.

In preparation for removing[2] the[3] macro[4], remove all remaining
needless uses with the following script:

git grep '\buninitialized_var\b' | cut -d: -f1 | sort -u | \
	xargs perl -pi -e \
		's/\buninitialized_var\(([^\)]+)\)/\1/g;
		 s:\s*/\* (GCC be quiet|to make compiler happy) \*/$::g;'

drivers/video/fbdev/riva/riva_hw.c was manually tweaked to avoid
pathological white-space.

No outstanding warnings were found building allmodconfig with GCC 9.3.0
for x86_64, i386, arm64, arm, powerpc, powerpc64le, s390x, mips, sparc64,
alpha, and m68k.

[1] https://lore.kernel.org/lkml/20200603174714.192027-1-glider@google.com/
[2] https://lore.kernel.org/lkml/CA+55aFw+Vbj0i=1TGqCR5vQkCzWJ0QxK6CernOU6eedsudAixw@mail.gmail.com/
[3] https://lore.kernel.org/lkml/CA+55aFwgbgqhbp1fkxvRKEpzyR5J8n1vKT1VZdz9knmPuXhOeg@mail.gmail.com/
[4] https://lore.kernel.org/lkml/CA+55aFz2500WfbKXAx8s67wrm9=yVJu65TpLgN_ybYNv0VEOKA@mail.gmail.com/

Reviewed-by: Leon Romanovsky <leonro@mellanox.com> # drivers/infiniband and mlx4/mlx5
Acked-by: Jason Gunthorpe <jgg@mellanox.com> # IB
Acked-by: Kalle Valo <kvalo@codeaurora.org> # wireless drivers
Reviewed-by: Chao Yu <yuchao0@huawei.com> # erofs
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 2023-08-11 11:33:32 +02:00
onettboots
246d06a7e8 drivers: input: add missing kernelsu hooks 
fixed some magisk modules not allowed when targeting to /system partitions

Signed-off-by: onettboots <blackcocopet@gmail.com>
Signed-off-by: clarencelol <clarencekuiek@icloud.com>
Signed-off-by: kibria5 <mdkibria687@gmail.com>
 2023-08-04 21:37:05 +00:00
kibria5
97547132c5 Merge tag 'v4.14.318'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git 
This is the 4.14.318 stable release
 2023-06-16 04:04:09 +00:00
Dmitry Torokhov
f1da7d7df5 Input: psmouse - fix OOB access in Elantech protocol 
commit 7b63a88bb62ba2ddf5fcd956be85fe46624628b9 upstream.

The kernel only allocate 5 MT slots; check that transmitted slot ID
falls within the acceptable range.

Link: https://lore.kernel.org/r/ZFnEL91nrT789dbG@google.com
Cc: stable@vger.kernel.org
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 2023-06-14 10:35:26 +02:00
Ismael Ferreras Morezuelas
171f6390c5 Input: xpad - delete a Razer DeathAdder mouse VID/PID entry 
commit feee70f4568650cf44c573488798ffc0a2faeea3 upstream.

While doing my research to improve the xpad device names I noticed
that the 1532:0037 VID/PID seems to be used by the DeathAdder 2013,
so that Razer Sabertooth instance looked wrong and very suspect to
me. I didn't see any mention in the official drivers, either.

After doing more research, it turns out that the xpad list
is used by many other projects (like Steam) as-is [1], this
issue was reported [2] and Valve/Sam Lantinga fixed it [3]:

[1]: dcc5eef0e2/src/joystick/controller_type.h (L251)
[2]: https://steamcommunity.com/app/353380/discussions/0/1743392486228754770/
[3]: https://hg.libsdl.org/SDL/rev/29809f6f0271

(With multiple Internet users reporting similar issues, not linked here)

After not being able to find the correct VID/PID combination anywhere
on the Internet and not receiving any reply from Razer support I did
some additional detective work, it seems like it presents itself as
"Razer Sabertooth Gaming Controller (XBOX360)", code 1689:FE00.

Leaving us with this:
 * Razer Sabertooth (1689:fe00)
 * Razer Sabertooth Elite (24c6:5d04)
 * Razer DeathAdder 2013 (1532:0037) [note: not a gamepad]

So, to sum things up; remove this conflicting/duplicate entry:

{ 0x1532, 0x0037, "Razer Sabertooth", 0, XTYPE_XBOX360 },

As the real/correct one is already present there, even if
the Internet as a whole insists on presenting it as the
Razer Sabertooth Elite, which (by all accounts) is not:

{ 0x1689, 0xfe00, "Razer Sabertooth", 0, XTYPE_XBOX360 },

Actual change in SDL2 referencing this kernel issue:
e5e5416975

For more information of the device, take a look here:
https://github.com/xboxdrv/xboxdrv/pull/59

You can see a lsusb dump here: https://github.com/xboxdrv/xboxdrv/files/76581/Qa6dBcrv.txt

Fixes: f554f619b7 ("Input: xpad - sync device IDs with xboxdrv")
Signed-off-by: Ismael Ferreras Morezuelas <swyterzone@gmail.com>
Reviewed-by: Cameron Gutman <aicommander@gmail.com>
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/5c12dbdb-5774-fc68-5c58-ca596383663e@gmail.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 2023-06-14 10:35:25 +02:00
kibria5
5cd51d29c2 Merge tag 'v4.14.316'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git 
This is the 4.14.316 stable release
 2023-06-03 20:31:07 +00:00
Vicki Pfau
ec8f45ed32 Input: xpad - add constants for GIP interface numbers 
[ Upstream commit f9b2e603c6216824e34dc9a67205d98ccc9a41ca ]

Wired GIP devices present multiple interfaces with the same USB identification
other than the interface number. This adds constants for differentiating two of
them and uses them where appropriate

Signed-off-by: Vicki Pfau <vi@endrift.com>
Link: https://lore.kernel.org/r/20230411031650.960322-2-vi@endrift.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
 2023-05-30 12:38:36 +01:00
NRanjan-17
90a10214e5 Merge tag 'v4.14.312' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.312 stable release
 2023-04-07 00:55:30 +00:00
Jason A. Donenfeld
6171c70c61 Input: focaltech - use explicitly signed char type 
commit 8980f190947ba29f23110408e712444884b74251 upstream.

The recent change of -funsigned-char causes additions of negative
numbers to become additions of large positive numbers, leading to wrong
calculations of mouse movement. Change these casts to be explicitly
signed, to take into account negative offsets.

Fixes: 3bc753c06dd0 ("kbuild: treat char as always unsigned")
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
Cc: stable@vger.kernel.org
Link: https://bugzilla.kernel.org/show_bug.cgi?id=217211
Link: https://lore.kernel.org/r/20230318133010.1285202-1-Jason@zx2c4.com
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
 2023-04-05 11:14:20 +02:00
NRanjan-17
3c2a197961 Merge tag 'v4.14.309' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.309 stable release
 2023-03-14 15:12:36 +00:00
Luca Ellero
536fbb4f53 Input: ads7846 - don't check penirq immediately for 7845 
[ Upstream commit fa9f4275b20ec7b2a8fb05c66362d10b36f9efec ]

To discard false readings, one should use "ti,penirq-recheck-delay-usecs".
Checking get_pendown_state() at the beginning, most of the time fails
causing malfunctioning.

Fixes: ffa458c1bd ("spi: ads7846 driver")
Signed-off-by: Luca Ellero <l.ellero@asem.it>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Link: https://lore.kernel.org/r/20230126105227.47648-4-l.ellero@asem.it
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
 2023-03-11 16:26:40 +01:00
Luca Ellero
ae1a6691b1 Input: ads7846 - don't report pressure for ads7845 
[ Upstream commit d50584d783313c8b05b84d0b07a2142f1bde46dd ]

ADS7845 doesn't support pressure.
Avoid the following error reported by libinput-list-devices:
"ADS7845 Touchscreen: kernel bug: device has min == max on ABS_PRESSURE".

Fixes: ffa458c1bd ("spi: ads7846 driver")
Signed-off-by: Luca Ellero <l.ellero@asem.it>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Link: https://lore.kernel.org/r/20230126105227.47648-2-l.ellero@asem.it
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
 2023-03-11 16:26:40 +01:00
NRanjan-17
d62fd4b6d4 Merge tag 'v4.14.305' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.305 stable release
 2023-02-16 13:23:22 +00:00
NRanjan-17
7abdd3f816 Merge tag 'v4.14.293' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.293 stable release
 2023-02-16 12:36:30 +00:00
NRanjan-17
b7bbbb260e Merge tag 'v4.14.283' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.283 stable release
 2023-02-14 13:52:43 +00:00
NRanjan-17
a9ab6111a5 Merge tag 'v4.14.281' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.281 stable release
 2023-02-13 15:09:02 +00:00
NRanjan-17
1e092267d7 Merge tag 'v4.14.276' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.276 stable release
 2023-02-13 14:35:44 +00:00
NRanjan-17
81eb8bcd75 Merge tag 'v4.14.273' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.273 stable release
 2023-02-11 08:13:10 +00:00
NRanjan-17
29c9974f8e Merge tag 'v4.14.270' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.270 stable release
 2023-02-10 06:16:22 +00:00
NRanjan-17
c2e2eb148e Merge tag 'v4.14.261' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.261 stable release
 2023-02-10 05:44:56 +00:00
NRanjan-17
786efeabbb Merge tag 'v4.14.260' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.260 stable release
 2023-02-10 05:44:18 +00:00
NRanjan-17
498a17bbb2 Merge tag 'v4.14.259' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.259 stable release
 2023-02-10 05:25:35 +00:00
NRanjan-17
841bbcb7c0 Merge tag 'v4.14.256' of https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git into thirteen 
This is the 4.14.256 stable release
 2023-02-10 05:13:28 +00:00