mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Glushkov <david.glushkov@sntiq.com>
To: Diogo Sousa <diogogsousa@gmail.com>
Cc: Mario Limonciello <superm1@kernel.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org,
	Vijendar Mukunda <Vijendar.Mukunda@amd.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: Disable async suspend for AMD rev 0x62 ACP and HD Audio
Date: Tue, 10 Nov 2026 13:50:24 +0100	[thread overview]
Message-ID: <20261110125025.2753861-1-david.glushkov@sntiq.com> (raw)
In-Reply-To: <5cdc7ef0-e18f-4afc-96b2-ee4e92bc29ee@gmail.com>

(Resending in plain text, my previous mail was rejected by the lists
because of an HTML part.)

Hi Mario, Bjorn,

I'm the author of the A9WJG subsystem-ID quirk that Diogo mentioned in his
commit message, so a data point from the MSI side.

I hit the same problem on an MSI Raider A18 HX A9WJG (MS-182L): the ACP is
rev 0x62 (1022:15e2 at 6a:00.5) with the Ryzen HD Audio controller
(1022:15e3) at 6a:00.6, and HD Audio stops working after resume, same as
Diogo describes. This is on the CachyOS 7.3 kernel.

Regarding the BIOS question: I'm on the latest BIOS for this model,
E182LAMS.31B (dated 05/26/2026), so a BIOS update isn't available as a
workaround here either. That makes at least two different vendors (ASUS
and MSI) with the latest firmware still affected.

Given that, a generic fix keyed on the ACP revision, as in Diogo's patch,
looks preferable to per-board subsystem-ID quirks. I'm happy to test any
follow-up version on this machine.

Thanks,
David

      reply	other threads:[~2026-11-10 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 13:50 Diogo Sousa
2026-10-16 21:43 ` Mario Limonciello
2026-10-17  8:39   ` Diogo Sousa
2026-11-10 12:19     ` Diogo Sousa
2026-11-10 12:50       ` David Glushkov [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=20261110125025.2753861-1-david.glushkov@sntiq.com \
    --to=david.glushkov@sntiq.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=bhelgaas@google.com \
    --cc=diogogsousa@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=superm1@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®