linux-kernel - Re: [PATCH v3] ASoC: qcom: Fix for DMA interrupt clear reg overwriting

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <162369994007.34524.2234994672815898510.b4-ty@kernel.org>
Date:   Mon, 14 Jun 2021 20:53:55 +0100
From:   Mark Brown <broonie@...nel.org>
To:     agross@...nel.org, rohitkr@...eaurora.org,
        srinivas.kandagatla@...aro.org,
        Srinivasa Rao Mandadapu <srivasam@...eaurora.org>,
        plai@...eaurora.org, tiwai@...e.com, linux-kernel@...r.kernel.org,
        robh+dt@...nel.org, swboyd@...omium.org,
        linux-arm-msm@...r.kernel.org, lgirdwood@...il.com,
        devicetree@...r.kernel.org, bgoswami@...eaurora.org,
        bjorn.andersson@...aro.org, judyhsiao@...omium.org,
        alsa-devel@...a-project.org, perex@...ex.cz
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH v3] ASoC: qcom: Fix for DMA interrupt clear reg overwriting

On Wed, 9 Jun 2021 12:53:10 +0530, Srinivasa Rao Mandadapu wrote:
> The DMA interrupt clear register overwritten during
> simultaneous playback and capture in lpass platform
> interrupt handler. It's causing playback or capture stuck
> in similtaneous plaback on speaker and capture on dmic test.
> Update appropriate reg fields of corresponding channel instead
> of entire register write.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: qcom: Fix for DMA interrupt clear reg overwriting
      commit: da0363f7bfd3c32f8d5918e40bfddb9905c86ee1

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark