From: Sachi King <nakato@nakato.io>
To: hdegoede@redhat.com, mgross@linux.intel.com,
mario.limonciello@amd.com, rafael@kernel.org, lenb@kernel.org,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] platform/x86: amd-pmc: Add alternative acpi id for PMC controller
Date: Tue, 05 Oct 2021 18:09:36 +1100 [thread overview]
Message-ID: <2915349.f8ii16yrt4@youmu> (raw)
In-Reply-To: <3ecd9046-ad0c-9c9a-9b09-bbab2f94b9f2@amd.com>
On Tuesday, 5 October 2021 16:16:18 AEDT Shyam Sundar S K wrote:
>
> On 10/2/2021 9:48 AM, Sachi King wrote:
> > The Surface Laptop 4 AMD has used the AMD0005 to identify this
> > controller instead of using the appropriate ACPI ID AMDI0005. Include
> > AMD0005 in the acpi id list.
>
> Can you provide an ACPI dump
The ACPI dump for this device is available here:
https://github.com/linux-surface/acpidumps/tree/master/surface_laptop_4_amd
> output of 'cat /sys/power/mem_sleep'
[s2idle]
Thanks,
Sachi
next prev parent reply other threads:[~2021-10-05 7:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-02 4:18 [PATCH 1/2] platform/x86: amd-pmc: Add alternative acpi id for PMC controller Sachi King
2021-10-02 4:18 ` [PATCH 2/2] ACPI: PM: Include alternate AMDI0005 id in special behaviour Sachi King
2021-10-08 18:57 ` Limonciello, Mario
2021-10-11 13:47 ` Hans de Goede
2021-10-12 14:01 ` Rafael J. Wysocki
2021-10-05 5:16 ` [PATCH 1/2] platform/x86: amd-pmc: Add alternative acpi id for PMC controller Shyam Sundar S K
2021-10-05 7:09 ` Sachi King [this message]
2021-10-07 20:00 ` Limonciello, Mario
2021-10-08 10:27 ` Shyam Sundar S K
2021-10-08 12:19 ` Sachi King
2021-10-08 15:57 ` Limonciello, Mario
2021-10-08 19:01 ` Limonciello, Mario
2021-10-09 2:05 ` Sachi King
2021-10-11 13:48 ` Hans de Goede
2021-10-11 13:46 ` Hans de Goede
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=2915349.f8ii16yrt4@youmu \
--to=nakato@nakato.io \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@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