Re: [REGRESSION][BISECTED] Dell Precision 7780 wakes up on its own from suspend

Mario Limonciello (AMD) (kernel.org)
2025-12-05T05:21:35Z

On 12/4/2025 10:01 PM, Askar Safin wrote:
> "Mario Limonciello (AMD) (kernel.org)" <superm1@kernel.org>:
>> Random thought - is this happening specifically when the lid is closed
>> and you're applying "pressure" to cause the touchpad to click with the
>> lid closed?
>
> No.
>
> I already sent script, which calls rtcwake in a loop. This script reproduces
> the bug. I don't touch anything when it is running.

Right; sorry about that I forgot with this thread starting such a long
time ago.

>
>> If that's not it, I would check if you have the latest firmware for the
>> touchpad. Unfortunately this isn't something "commonly" flashable with
>> Linux like is the case with BIOS and other components.
>
> I already downloaded "touchpad firmware update utility" and did run it
> within Windows. So, yes, I have latest firmware.
>
>> Maybe @DellClientKernel could provide some guidance.
>
> Dell.Client.Kernel@dell.com was in CC all this time.
>
> Also, I contacted support via web chat (and said my service tag, of course).
> (My laptop comes with Ubuntu preinstalled.)
> They said I have basic support only,
> so they will not look into the issue too deeply. We had lengthy chat,
> and in some moment they said that they will not debug OS-related issues.
> I. e. if I want help with this bug, I should reproduce it without OS,
> i. e. in BIOS setup utility. Of course, this is not possible, because
> one cannot suspend BIOS setup utility.
>
> I sent them link to this thread and said that the bug is probably in firmware.
> But they seem to ignore this.
>
> Also, they said I can send the laptop to them, they will try to fix it and
> send it back. I don't want this.

OK. It sounds like you have exhausted relevant avenues, I'm aligned on
a quirk.

>
>> But yes; failing all that it's viable to make a quirk. You can follow
>> any of the ones I've submitted for modeling how to do it. Here's the
>> most recent one I've done.
>>
>> https://github.com/torvalds/linux/commit/23800ad1265f10c2bc6f42154ce4d20e59f2900e
>
> Thank you! I will write something like this:
>
> + .matches = {
> + DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> + DMI_MATCH(DMI_PRODUCT_FAMILY, "Precision"),
> + },
> + .driver_data = &(struct acpi_gpiolib_dmi_quirk) {
> + .ignore_wake = "VEN_0488:00@355",
> + },
>
> I will test it and then properly send (hopefully today or tomorrow).
>

This match it too liberal. We don't have any evidence it applies to
anything more than your single system. I'd pick some different strings.
For example Product SKU is probably a good string to use because
that's very unique.