Thread (101 messages) 101 messages, 11 authors, 2020-12-11

Re: [PATCH v4 0/7] Support inhibiting input devices

From: Andrzej Pietrasiewicz <hidden>
Date: 2020-08-03 14:41:06
Also in: linux-acpi, linux-arm-kernel, linux-iio, linux-pm, linux-samsung-soc, linux-tegra, lkml, platform-driver-x86

Hi Dmitry,

W dniu 12.06.2020 o 10:17, Hans de Goede pisze:
Hi,

On 6/8/20 1:22 PM, Andrzej Pietrasiewicz wrote:
quoted
This is a quick respin of v3, with just two small changes, please see
the changelog below.

Userspace might want to implement a policy to temporarily disregard input
from certain devices.
<snip>
quoted
v3..v4:
- updated the comment in input_open_device() (Hans)
- used more straightforward locking pattern in adc/exynos (Michał)

v2..v3:
- ignored autorepeat events in input_get_disposition() if a key is not
pressed (Hans)
- dropped inhibit()/uninhibit() driver callbacks (Hans)
- split ACPI button patch into taking the lock and using the helper (Rafael)
- dropped the elan_i2c conversion
- fixed typos in exynos adc

v1..v2:
- added input_device_enabled() helper and used it in drivers (Dmitry)
- the fact of open() and close() being called in inhibit/uninhibit paths has
been emphasized in the commit message of PATCH 6/7 (Dmitry)
<snip>
The entire series looks good to me:

Acked-by: Hans de Goede <redacted>
What are the prospects of this series being merged?

Regards,

Andrzej
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help