From: Hans de Goede <hansg@kernel.org>
To: Sergey Lebedev <lsa.uz@pm.me>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Maximilian Luz <luzmaximilian@gmail.com>
Cc: linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: soc_button_array: ignored -EPROBE_DEFER loses the buttons on 68% of boots (Surface Pro 11)
Date: Wed, 9 Sep 2026 11:41:33 +0200 [thread overview]
Message-ID: <8a8a0fcb-1c93-4f0d-bfcd-ae92af0376e0@kernel.org> (raw)
In-Reply-To: <0fe7a8b6-f3df-4822-a03a-d072b86cdfa8@kernel.org>
Hi,
On 8-Sep-26 23:46, Hans de Goede wrote:
<snip>
>> Why no patch
>> ------------
>>
>> The comment says -EPROBE_DEFER is discarded because Intel uses "virtual
>> GPIOs" that never materialise, so deferring on them would hang the probe
>> forever. A fix has to tell that case apart from a controller that simply has
>> not probed yet, and I do not know which signal you would want to use for
>> that. Guessing would risk reintroducing the problem the workaround exists
>> for.
>>> Happy to test whatever shape you would prefer - the machine is here and I
>> can build and boot kernels on it.
>
> Thank you for your detailed bug report. I've just submitted a patch which
> I believe should fix this:
>
> https://lore.kernel.org/platform-driver-x86/20260908214410.70422-1-johannes.goede@oss.qualcomm.com/
>
> Please give this a try and confirm if it fixes things.
Shashiko review has lead to a v2 and then a v3 of the fix, please
give v3 a try:
https://lore.kernel.org/linux-input/20260909093934.29411-1-johannes.goede@oss.qualcomm.com/
Regards,
Hans
prev parent reply other threads:[~2026-09-09 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 14:14 soc_button_array: ignored -EPROBE_DEFER loses the buttons on 68% of boots (Surface Pro 11) Sergey Lebedev
2026-09-08 21:46 ` Hans de Goede
2026-09-09 9:41 ` Hans de Goede [this message]
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=8a8a0fcb-1c93-4f0d-bfcd-ae92af0376e0@kernel.org \
--to=hansg@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsa.uz@pm.me \
--cc=luzmaximilian@gmail.com \
--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.