linux-kernel - Re: [PATCH] ASoC: SOF: pm: Tear down pipelines only if DSP was active

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: <168069754270.50709.3405991457967735088.b4-ty@kernel.org>
Date:   Wed, 05 Apr 2023 13:25:42 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        Daniel Baluta <daniel.baluta@....nxp.com>
Cc:     linux-kernel@...r.kernel.org, cujomalainey@...omium.org,
        tiwai@...e.com, perex@...ex.cz, kai.vehmanen@...ux.intel.com,
        ranjani.sridharan@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
        peter.ujfalusi@...ux.intel.com, lgirdwood@...il.com,
        pierre-louis.bossart@...ux.intel.com
Subject: Re: [PATCH] ASoC: SOF: pm: Tear down pipelines only if DSP was
 active

On Wed, 05 Apr 2023 12:26:55 +0300, Daniel Baluta wrote:
> With PCI if the device was suspended it is brought back to full
> power and then suspended again.
> 
> This doesn't happen when device is described via DT.
> 
> We need to make sure that we tear down pipelines only if the device
> was previously active (thus the pipelines were setup).
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: pm: Tear down pipelines only if DSP was active
      commit: 0b186bb06198653d74a141902a7739e0bde20cf4

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