From: Hans de Goede <johannes.goede@oss.qualcomm.com>
To: Sergey Lebedev <lsa.uz@pm.me>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, platform-driver-x86@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] Input: soc_button_array - fix MS Surface Pro 11 probe failure
Date: Thu, 10 Sep 2026 10:43:47 +0200 [thread overview]
Message-ID: <bb913cfc-288b-4ce6-befd-76c774de4d02@oss.qualcomm.com> (raw)
In-Reply-To: <20260909102521.67488-1-lsa.uz@pm.me>
Hi,
On 9-Sep-26 12:25, Sergey Lebedev wrote:
> Hans,
>
> It fixes it. Sixteen consecutive boots on the Surface Pro 11, every one with
> both gpio-keys devices present and MSHW0040:00 bound. The baseline in my
> report was 13 boots in 40.
>
> boots 16
> buttons appeared 16
> first input at 1.242 - 1.377 s
>
> For comparison the 13 stock successes ran 1.28 - 1.78 s, so no boot here was
> slower than stock managed when it worked, and the spread is tighter. The unit
> that binds this device by hand was disabled for the whole run, so nothing
> masked the result.
>
> Built on 7.0.0-30, Ubuntu 26.04; both patches apply to that kernel's copy of
> the file as-is, 2/2 at an offset. Ubuntu ships the file unmodified - an
> out-of-tree build of mainline v7.0's source carries the same srcversion as
> Ubuntu's own module - so the tested source differs from stock by your patches
> and nothing else.
>
> One note for whoever tests this driver next rather than about the patch: on
> this install soc_button_array is in the initramfs under MODULES=most, so
> replacing the module under /lib/modules does nothing until update-initramfs
> runs, and modinfo will report the new one while the old one is loaded. Three
> boots of mine were recorded before I noticed. I checked
> /sys/module/soc_button_array/srcversion on every boot above.
>
> Patch 2/2 was in the same build and caused no regression, but I am not
> claiming a test for it: the buttons appear here, so this machine's ACPI
> descriptor package is not empty and the new check is never reached. So for
> 1/2 only:
>
> Tested-by: Sergey Lebedev <lsa.uz@pm.me>
Great, thank you for testing!
Regards,
Hans
prev parent reply other threads:[~2026-09-10 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 9:39 [PATCH v3 1/2] Input: soc_button_array - fix MS Surface Pro 11 probe failure Hans de Goede
2026-09-09 9:39 ` [PATCH v3 2/2] Input: soc_button_array - check btns_desc->package.count Hans de Goede
2026-09-09 10:25 ` [PATCH v3 1/2] Input: soc_button_array - fix MS Surface Pro 11 probe failure Sergey Lebedev
2026-09-10 8:43 ` 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=bb913cfc-288b-4ce6-befd-76c774de4d02@oss.qualcomm.com \
--to=johannes.goede@oss.qualcomm.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=lsa.uz@pm.me \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox