From: Mario Limonciello <superm1@kernel.org>
To: Mike Lothian <mike@fireburn.co.uk>
Cc: amd-gfx@lists.freedesktop.org, alexander.deucher@amd.com,
christian.koenig@amd.com, dri-devel@lists.freedesktop.org,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
rafael@kernel.org
Subject: Re: [PATCH 2/2] drm/amdgpu: handle broken dGPU hotplug GPE on ASUS ROG Strix G513QY
Date: Sun, 22 Nov 2026 12:15:37 -0600 [thread overview]
Message-ID: <1fafa3c2-3f8d-4672-bf84-c474d0e4f7f7@kernel.org> (raw)
In-Reply-To: <20261122143557.2412982-1-mike@fireburn.co.uk>
On 11/22/26 08:35, Mike Lothian wrote:
> Mario,
>
> Thanks for the CPM _L05 quirk. I've tested it on the G513QY (BIOS G513QY.335) with the dGPU runtime-resume patch on top. The boot log shows `CPM: \_GPE._L05 notifies missing \_SB.PCI0.GPP0.VGA, using \_SB.PCI0.GPP0.SWUS.SWDS.VGA instead`, and the external displays come up after a dock attach with the dGPU in D3cold
>
> Feel free to add my Tested-by
>
> Mike
OK I've sent that out for review separately.
https://lore.kernel.org/linux-acpi/20261122-fdo-gitlab-6061-v1-1-8380b1ec4e09@amd.com/
prev parent reply other threads:[~2026-11-22 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 15:14 [PATCH 0/2] drm/amdgpu: wake a powered-off dGPU on a dock hotplug notify Mike Lothian
2026-10-29 15:14 ` [PATCH 1/2] drm/amdgpu: runtime resume dGPU on ACPI notify from its own node Mike Lothian
2026-10-29 15:20 ` Mario Limonciello
2026-10-29 16:05 ` Alex Deucher
2026-10-30 7:57 ` Mike Lothian
2026-10-30 14:52 ` Mario Limonciello
2026-10-29 15:14 ` [PATCH 2/2] drm/amdgpu: handle broken dGPU hotplug GPE on ASUS ROG Strix G513QY Mike Lothian
2026-10-29 15:24 ` Mario Limonciello
2026-10-30 7:57 ` Mike Lothian
2026-10-30 14:55 ` Mario Limonciello
2026-11-22 14:35 ` Mike Lothian
2026-11-22 18:15 ` Mario Limonciello [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=1fafa3c2-3f8d-4672-bf84-c474d0e4f7f7@kernel.org \
--to=superm1@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@fireburn.co.uk \
--cc=rafael@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
all inboxes | Powered by JetHome®