From: bugzilla-daemon@bugzilla.kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 213579] Clevo NH55HJ (intel tigerlake) touchpad support (GPIO can't be used as IRQ)
Date: Wed, 21 Jul 2021 13:07:30 +0000 [thread overview]
Message-ID: <bug-213579-215701-s597Ad8ldb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213579-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213579
--- Comment #19 from Andy Shevchenko (andy.shevchenko@gmail.com) ---
(In reply to wse from comment #17)
> pin 57 (SLP_S0B) 44:INT34C6:00 mode 1 0x84000500 0x00000051 0x00000000 [ACPI]
What I'm wondering is if the pin list is broken and actual pin 57 is something
else (+- few pins according to the current driver). May be someone can install
libgpiod tools (such as `gpiomon`) and run with pins that are already in GPIO
mode without [ACPI] bit set. Something like `gpiomon gpiochip0 43` (for pin
#56) and `gpiomon gpiochip0 47` (for pin #60). Then if touchpad (when being
touched I presume) generates the interrupts this will show them. But it's
unlikely as
per success story described in the bug #211957 where pin under question has
much higher number and any pin list disturbance will be noticed immediately.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-07-21 13:07 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-213579-215701@https.bugzilla.kernel.org/>
2021-06-29 23:38 ` [Bug 213579] Clevo NH55HJ (intel tigerlake) touchpad support (GPIO can't be used as IRQ) bugzilla-daemon
2021-07-04 11:39 ` bugzilla-daemon
2021-07-04 14:33 ` bugzilla-daemon
2021-07-04 14:35 ` bugzilla-daemon
2021-07-04 15:05 ` bugzilla-daemon
2021-07-21 2:55 ` bugzilla-daemon
2021-07-21 7:33 ` bugzilla-daemon
2021-07-21 8:52 ` bugzilla-daemon
2021-07-21 9:13 ` bugzilla-daemon
2021-07-21 9:14 ` bugzilla-daemon
2021-07-21 9:17 ` bugzilla-daemon
2021-07-21 12:32 ` bugzilla-daemon
2021-07-21 12:56 ` bugzilla-daemon
2021-07-21 13:07 ` bugzilla-daemon [this message]
2021-07-21 13:40 ` bugzilla-daemon
2021-07-21 13:45 ` bugzilla-daemon
2021-07-21 14:32 ` bugzilla-daemon
2021-07-21 15:55 ` bugzilla-daemon
2021-07-21 16:01 ` bugzilla-daemon
2021-07-21 16:04 ` bugzilla-daemon
2021-07-21 16:07 ` bugzilla-daemon
2021-07-21 16:13 ` bugzilla-daemon
2021-07-21 17:24 ` bugzilla-daemon
2021-07-21 17:51 ` bugzilla-daemon
2021-07-21 17:59 ` bugzilla-daemon
2021-07-21 18:24 ` bugzilla-daemon
2021-07-21 19:58 ` bugzilla-daemon
2021-07-21 21:38 ` bugzilla-daemon
2021-07-21 21:45 ` bugzilla-daemon
2021-07-22 7:48 ` bugzilla-daemon
2021-07-22 8:22 ` bugzilla-daemon
2021-07-22 12:08 ` bugzilla-daemon
2021-07-22 13:30 ` bugzilla-daemon
2021-07-22 14:14 ` bugzilla-daemon
2021-07-22 17:27 ` bugzilla-daemon
2021-07-23 5:47 ` bugzilla-daemon
2021-07-23 6:29 ` bugzilla-daemon
2021-07-27 23:43 ` bugzilla-daemon
2021-08-02 14:02 ` bugzilla-daemon
2021-08-02 14:05 ` bugzilla-daemon
2021-08-02 17:16 ` bugzilla-daemon
2021-08-03 11:32 ` bugzilla-daemon
2021-08-03 11:44 ` bugzilla-daemon
2021-08-03 12:55 ` bugzilla-daemon
2021-08-03 13:03 ` bugzilla-daemon
2021-08-03 13:27 ` bugzilla-daemon
2021-08-03 13:42 ` bugzilla-daemon
2021-08-03 14:59 ` bugzilla-daemon
2021-08-04 12:12 ` bugzilla-daemon
2021-08-04 12:12 ` bugzilla-daemon
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=bug-213579-215701-s597Ad8ldb@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.