On Wed, Feb 15, 2023 at 03:26:36PM +0200, Andy Shevchenko wrote:on it
On Wed, Feb 15, 2023 at 12:59:46PM +0100, Werner Sembach wrote:Actually we have yet another little fix. So maybe I can create a tagged bundle.
Am 15.02.23 um 11:49 schrieb Andy Shevchenko:
On Tue, Feb 14, 2023 at 01:58:10PM +0100, Werner Sembach wrote:
commit 1796f808e4bb ("HID: i2c-hid: acpi: Stop setting wakeup_capable")Bart, I'm fine if it goes directly via your tree, or I can send it in usual
changed the policy such that I2C touchpads may be able to wake up the
system by default if the system is configured as such.
However for some devices there is a bug, that is causing the touchpad to
instantly wake up the device again once it gets deactivated. The root cause
is still under investigation:
https://lore.kernel.org/linux-acpi/2d983050-f844-6c5e-8ae9-9f87ac68dfdd@xxxxxxxxxxxxxxxxxxx/T/#mb2e738787f6b6208d17b92aa6e72d4de846d4e4d
bundle of fixes after rc1 (however it seems this deserves to make v6.2).
Perhaps v4 will be the best option here.
Just realized i did not add cc stable:We have at least the following options:
It is required for 6.1 also.
- you can send specific request for stable after it becomes a part of upstream
- you can send a v4 with it
Reviewed-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
To workaround this problem for the time being, introduce a quirk for this
model that will prevent the wakeup capability for being set for GPIO 16.