On Mon, Nov 02, 2020 at 09:06:23PM +0200, Andy Shevchenko wrote:
On Fri, Oct 30, 2020 at 6:54 AM Coiby Xu <coiby.xu@xxxxxxxxx> wrote:
On Tue, Oct 27, 2020 at 06:09:49PM +0200, Andy Shevchenko wrote:
>On Tue, Oct 27, 2020 at 6:01 PM Hans de Goede <hdegoede@xxxxxxxxxx> wrote:
>> On 10/27/20 4:13 PM, Andy Shevchenko wrote:
...
>> I see, so then the right thing to do for the bug which we are seeing
>> on some AMD platforms would be to honor the debounce setting I guess ?
>>
>> Can you and/or Mika write a patch(set) for this ?
>
>I will look at it, but meanwhile I would postpone until having a
>Mika's Ack on the action that my understanding and course of actions
>is correct.
I will soon send a support patch against ACPI GPIO library code.
If you don't mind, let me write this patch(set) instead:)
I leave to you whatever AMD code. It will suit our both interests :-)
Excellent! Thank you!
I feel itchy
to fix this touchpad issue by myself after spending about a month of
my internship at Linux Foundation investigating this touchpad issue.
There are many enthusiastic Linux users waiting to get their touchpads
fixed and I could prioritize this task since I don't have other
obligations. I have provided a fallback solution [1] to save their
touchpads but it seems patches on gpiolib-acpi.c and pinctrl-amd could
reach mainline kernel much earlier.
[1] https://lore.kernel.org/patchwork/patch/1323245/
--
With Best Regards,
Andy Shevchenko
--
Best regards,
Coiby
