Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Jacek Łuczak" <difrost.kernel@gmail.com>
To: Mark Brown <broonie@kernel.org>,
	"Prasad, Prasad" <venkataprasad.potturu@amd.com>
Cc: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
	"Mukunda, Vijendar" <Vijendar.Mukunda@amd.com>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Resume from suspend broken in 6.15-rc due to ACP changes.
Date: Sat, 26 Apr 2025 21:01:12 +0200	[thread overview]
Message-ID: <cd66bf64-6da2-4550-afeb-cdc279da22d4@gmail.com> (raw)
In-Reply-To: <70293c18-f17d-48e4-94b9-4e7f62cfa45e@sirena.org.uk>


On 4/24/25 7:51 PM, Mark Brown wrote:
> On Thu, Apr 24, 2025 at 04:53:45PM +0000, Prasad, Prasad wrote:
>> On 4/24/2025 12:57 AM, Mario Limonciello wrote:
>>> Reverting a95a1dbbd3d64adf392fed13c8eef4f72b4e5b90 seems to help the
>>> issue on S16 here.
>>> Jacek - can you reproduce with that reverted?
>> We will send a fix patch to resolve this issue.
> Excellent, thanks for jumping on this.  There was an AMD CC on the
> original report so I'd thought it'd have been seen.


Mark,

thanks for taking care of this one!

Cheers,

-Jacek


  reply	other threads:[~2025-04-26 19:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-16 11:20 [REGRESSION] Resume from suspend broken in 6.15-rc due to ACP changes Jacek Luczak
2025-04-23 15:06 ` Mark Brown
2025-04-23 15:18   ` Mario Limonciello
2025-04-23 19:12     ` Mario Limonciello
2025-04-23 19:27       ` Mario Limonciello
2025-04-24 16:53         ` Prasad, Prasad
2025-04-24 17:51           ` Mark Brown
2025-04-26 19:01             ` Jacek Łuczak [this message]
2025-05-04 20:02           ` Jacek Łuczak
2025-04-26 19:00         ` Jacek Łuczak

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=cd66bf64-6da2-4550-afeb-cdc279da22d4@gmail.com \
    --to=difrost.kernel@gmail.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=venkataprasad.potturu@amd.com \
    /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