linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Coiby Xu <coiby.xu@gmail.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	wang jun <availa@outlook.com>,
	Nehal Shah <Nehal-bakulchandra.Shah@amd.com>,
	Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
	linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: Any other ways to debug GPIO interrupt controller (pinctrl-amd) for broken touchpads of a new laptop model?
Date: Tue, 3 Nov 2020 06:56:00 +0800	[thread overview]
Message-ID: <20201102225600.nngn7lahtonni3sk@Rk> (raw)
In-Reply-To: <CAHp75Vej=LT06MEmoAvAxrHY7zzvPKEJLe03C3BN5X4EZos_JA@mail.gmail.com>

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@gmail.com> 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@redhat.com> 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

  reply	other threads:[~2020-11-02 22:56 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-01 13:22 Any other ways to debug GPIO interrupt controller (pinctrl-amd) for broken touchpads of a new laptop model? Coiby Xu
2020-10-01 20:57 ` Linus Walleij
2020-10-02  9:40   ` Hans de Goede
2020-10-02 12:42     ` Coiby Xu
2020-10-02 13:36       ` Hans de Goede
2020-10-02 14:51         ` Coiby Xu
2020-10-02 19:44           ` Hans de Goede
2020-10-02 22:45             ` Coiby Xu
2020-10-03 13:22               ` Hans de Goede
2020-10-03 23:03                 ` Coiby Xu
2020-10-04  5:16                   ` Coiby Xu
2020-10-06  4:49                     ` Coiby Xu
2020-10-06  6:28                       ` Hans de Goede
2020-10-06  8:31                         ` Coiby Xu
2020-10-06  8:55                           ` Hans de Goede
2020-10-06  9:28                             ` Hans de Goede
2020-10-06  9:29                               ` Hans de Goede
2020-10-08 16:32                                 ` Coiby Xu
2020-10-14  4:24                                 ` Coiby Xu
2020-10-14 11:34                                   ` Coiby Xu
2020-10-14 11:46                                   ` Hans de Goede
2020-10-15  3:27                                     ` Coiby Xu
2020-10-15  4:06                                     ` Coiby Xu
2020-10-26 22:54                                     ` Coiby Xu
2020-10-27  9:52                                       ` Andy Shevchenko
2020-10-30  4:58                                         ` Coiby Xu
2020-10-27 10:09                                       ` Hans de Goede
2020-10-27 15:13                                         ` Andy Shevchenko
2020-10-27 16:00                                           ` Hans de Goede
2020-10-27 16:09                                             ` Andy Shevchenko
2020-10-29  8:04                                               ` Mika Westerberg
2020-10-30  4:54                                               ` Coiby Xu
2020-11-02 19:06                                                 ` Andy Shevchenko
2020-11-02 22:56                                                   ` Coiby Xu [this message]
2020-11-03  0:05                                         ` Coiby Xu
2020-11-03 10:12                                           ` Hans de Goede
2020-11-03 10:49                                             ` Andy Shevchenko
2020-11-03 11:00                                               ` Hans de Goede
2020-10-08 16:26                               ` Coiby Xu
2020-10-06  9:16                           ` Linus Walleij
2020-10-08 16:40                             ` Coiby Xu
2020-10-02 10:59   ` Coiby Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201102225600.nngn7lahtonni3sk@Rk \
    --to=coiby.xu@gmail.com \
    --cc=Nehal-bakulchandra.Shah@amd.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=availa@outlook.com \
    --cc=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=mika.westerberg@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).