From: Andy Shevchenko via Bugspray Bot <bugbot@kernel.org>
To: linux-gpio@vger.kernel.org
Subject: Re: PixArt touchpad not detected due to wrong pinctrl
Date: Sun, 27 Apr 2025 19:05:21 +0000 [thread overview]
Message-ID: <20250427-b220056c17-9aa54300f731@bugzilla.kernel.org> (raw)
In-Reply-To: <20250427-b220056c14-65b296b1b462@bugzilla.kernel.org>
Andy Shevchenko writes via Kernel.org Bugzilla:
(In reply to Ariel Simulevski from comment #14)
> Yeah as it stands, this grouping is based on observation, not official
> documentation (I think I even wrote that in a comment in my first patch). As
> I don’t have access to the Intel PCH documentation (and am still getting
> into Kernel Hacking), these were more or less educated guesses.
>
> Andy if you prefer, I am happy to withdraw the patch and instead suggest
> documenting the need to use CONFIG_PINCTRL_TIGERLAKE for affected systems.
>
> I do agree with Guido tho that the status quo is sort of confusing.
To understand the issue, I need to hear how you reproduce it and how this patch makes it different. The drivers are bound to the devices based on ID tables (ACPI ID table in this case). Your change doesn't alter that and hence it can't be involved in anything related to this case, it can't *fix* anything.
View: https://bugzilla.kernel.org/show_bug.cgi?id=220056#c17
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2025-04-27 19:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 18:25 PixArt touchpad not detected due to wrong pinctrl Guido Trentalancia via Bugspray Bot
2025-04-26 20:00 ` Ariel Simulevski via Bugspray Bot
2025-04-26 20:40 ` Guido Trentalancia via Bugspray Bot
2025-04-26 21:50 ` Guido Trentalancia via Bugspray Bot
2025-04-26 21:50 ` Guido Trentalancia via Bugspray Bot
2025-04-26 22:05 ` Ariel Simulevski via Bugspray Bot
2025-04-26 22:40 ` Guido Trentalancia via Bugspray Bot
2025-04-26 22:40 ` Guido Trentalancia via Bugspray Bot
2025-04-26 23:00 ` Ariel Simulevski via Bugspray Bot
2025-04-27 9:00 ` Andy Shevchenko via Bugspray Bot
2025-04-27 9:25 ` Andy Shevchenko via Bugspray Bot
2025-04-27 11:40 ` Ariel Simulevski via Bugspray Bot
2025-04-27 12:15 ` Guido Trentalancia via Bugspray Bot
2025-04-27 19:00 ` Andy Shevchenko via Bugspray Bot
2025-04-27 14:55 ` Guido Trentalancia via Bugspray Bot
2025-04-27 19:00 ` Andy Shevchenko via Bugspray Bot
2025-04-27 16:30 ` Ariel Simulevski via Bugspray Bot
2025-04-27 19:05 ` Andy Shevchenko via Bugspray Bot [this message]
2025-04-27 20:05 ` Guido Trentalancia via Bugspray Bot
2025-04-28 6:30 ` Andy Shevchenko via Bugspray Bot
2025-04-28 7:55 ` Guido Trentalancia via Bugspray Bot
2025-04-28 8:40 ` Andy Shevchenko via Bugspray Bot
2025-04-28 10:05 ` Guido Trentalancia via Bugspray Bot
2025-04-28 10:55 ` Andy Shevchenko via Bugspray Bot
2025-04-28 11:00 ` Ariel Simulevski via Bugspray Bot
2025-04-28 16:40 ` Andy Shevchenko via Bugspray Bot
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=20250427-b220056c17-9aa54300f731@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=linux-gpio@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.