All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/2] Stop using AMD GUID/_REV 2 by default
@ 2022-12-15 19:16 Mario Limonciello
  2022-12-15 19:16 ` [PATCH 1/2] ACPI: x86: s2idle: Force AMD GUID/_REV 2 on HP Elitebook 865 Mario Limonciello
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Mario Limonciello @ 2022-12-15 19:16 UTC (permalink / raw)
  To: rafael, Philipp Zabel, Mario Limonciello, Rafael J. Wysocki
  Cc: anson.tsao, ben, paul, bilkow, Shyam-sundar.S-k, Len Brown,
	linux-acpi, linux-kernel

A number of laptops have been showing up where lots of EC controlled
features weren't working after resume.  They've varied from KBD
backlight, to fans, brightness control and lots more.
In kernel 6.1 we introduced a module parameter through
commit a0bc002393d4 ("ACPI: x86: s2idle: Add module parameter to
prefer Microsoft GUID") and a series of quirks in follow up commits
for systems that people reported the problems.

3 more systems recently reported issues; and so rather than increasing
the list /again/ to add these new systems we took a hard look at the
"why".

The AMD GUID/_REV 2 path was introduced for vendors to be able to
differentiate from the Microsoft path.  Vendors could populate this
with unique code for their designs.  Conceptually this was supposed
to help the ecosystem, however in practice we've found that there
are more machines that don't populate it than do.

The only models that have populated this with unique code for avoiding
a bug specific to their design is the HP Elitebook 835, 845, and 865 G9
systems.

To avoid growing the list further this series rips out the module
parameter support, all the quirks and sets the default policy to follow
the Microsoft GUID path for AMD Rembrandt or later.  We validated this
on OEM systems and we found this fixes them.

To avoid regressing the HP systems that use the AMD GUID/_REV 2
path, let them keep taking it. The reason they take it is believed to
be a bug with WLAN firmware.  If this is fixed in the future, we may
consider dropping the HP systems as well and having no quirks.

Mario Limonciello (2):
  ACPI: x86: s2idle: Force AMD GUID/_REV 2 on HP Elitebook 865
  ACPI: x86: s2idle: Stop using AMD specific codepath for Rembrandt+

 drivers/acpi/x86/s2idle.c | 87 ++++++---------------------------------
 1 file changed, 13 insertions(+), 74 deletions(-)

-- 
2.34.1


^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: [PATCH 2/2] ACPI: x86: s2idle: Stop using AMD specific codepath for Rembrandt+
@ 2022-12-20 17:54 francois
  0 siblings, 0 replies; 6+ messages in thread
From: francois @ 2022-12-20 17:54 UTC (permalink / raw)
  To: mario.limonciello
  Cc: Shyam-sundar.S-k, anson.tsao, ben, bilkow, lenb, linux-acpi,
	linux-kernel, paul, philipp.zabel, rafael.j.wysocki, rafael,
	stable

Am Thu, Dec 15, 2022 at 01:16:16PM -0600 schrieb Mario Limonciello:
> After we introduced a module parameter and quirk infrastructure for  > picking the Microsoft GUID over the SOC vendor GUID we discovered >
that lots and lots of systems are getting this wrong. > > The table
continues to grow, and is becoming unwieldy. > > We don't really have
any benefit to forcing vendors to populate the > AMD GUID. This is just
extra work, and more and more vendors seem > to mess it up. As the
Microsoft GUID is used by Windows as well, > it's very likely that it
won't be messed up like this. > > So drop all the quirks forcing it and
the Rembrandt behavior. This > means that Cezanne or later effectively
only run the Microsoft GUID > codepath with the exception of HP
Elitebook 8*5 G9. > > Fixes: fd894f05cf30 ("ACPI: x86: s2idle: If a new
AMD _HID is missing assume Rembrandt") > Cc: stable@vger.kernel.org #
6.1 > Reported-by: Benjamin Cheng <ben@bcheng.me> > Reported-by:
bilkow@tutanota.com > Reported-by: Paul <paul@zogpog.com> > Link:
https://gitlab.freedesktop.org/drm/amd/-/issues/2292 > Link:
https://bugzilla.kernel.org/show_bug.cgi?id=216768 > Signed-off-by:
Mario Limonciello <mario.limonciello@amd.com> Tested-by: François ARMAND <francois@fanf.eu>
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/2307

Regards - and thanks for the help Mario!
François




^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2022-12-22 16:41 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-12-15 19:16 [PATCH 0/2] Stop using AMD GUID/_REV 2 by default Mario Limonciello
2022-12-15 19:16 ` [PATCH 1/2] ACPI: x86: s2idle: Force AMD GUID/_REV 2 on HP Elitebook 865 Mario Limonciello
2022-12-15 19:16 ` [PATCH 2/2] ACPI: x86: s2idle: Stop using AMD specific codepath for Rembrandt+ Mario Limonciello
2022-12-17 12:52   ` Philipp Zabel
2022-12-22 16:41 ` [PATCH 0/2] Stop using AMD GUID/_REV 2 by default Rafael J. Wysocki
2022-12-20 17:54 [PATCH 2/2] ACPI: x86: s2idle: Stop using AMD specific codepath for Rembrandt+ francois

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.