linux-kernel - Re: [PATCH 3/3] ASoC: dwc: always enable/disable i2s irqs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <98b92d09-435b-4aa4-9b21-496b51ce7d5f@sirena.org.uk>
Date: Wed, 26 Mar 2025 13:25:12 +0000
From: Mark Brown <broonie@...nel.org>
To: Brady Norander <bradynorander@...il.com>
Cc: linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
	u.kleine-koenig@...libre.com, Wu Bo <bo.wu@...o.com>
Subject: Re: [PATCH 3/3] ASoC: dwc: always enable/disable i2s irqs

On Tue, Mar 25, 2025 at 05:18:05PM -0400, Brady Norander wrote:

> Commit a42e988 ("ASoC: dwc: add DMA handshake control") changed the
> behavior of the driver to not enable or disable i2s irqs if using DMA. This
> breaks platforms such as AMD ACP. Revert to the old behavior by always
> enabling and disabling i2s irqs while keeping DMA handshake control.
> 
> Fixes: a42e988 ("ASoC: dwc: add DMA handshake control")
> Signed-off-by: Brady Norander <bradynorander@...il.com>

Same issue with dependencies here - what's going on?  It also doesn't
seem like the changelog is describing what's goin on well, if all AMD
systems were broken by a change from 2023 I'd really expect to have
heard about it by now.  We've had AMD themselves doing fairly extensive
work without reporting any issues.  What specifically is the problem you
are seeing?

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)