linux-kernel - Re: [PATCH v2] Asoc: qcom: lpass-cpu: Fix clock disable failure

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: <160397520897.55401.4677277662633686101.b4-ty@kernel.org>
Date:   Thu, 29 Oct 2020 12:40:15 +0000
From:   Mark Brown <broonie@...nel.org>
To:     devicetree@...r.kernel.org, perex@...ex.cz, robh+dt@...nel.org,
        linux-kernel@...r.kernel.org, rohitkr@...eaurora.org,
        Srinivasa Rao Mandadapu <srivasam@...eaurora.org>,
        srinivas.kandagatla@...aro.org, agross@...nel.org,
        plai@...eaurora.org, linux-arm-msm@...r.kernel.org,
        lgirdwood@...il.com, bgoswami@...eaurora.org, tiwai@...e.com,
        bjorn.andersson@...aro.org, alsa-devel@...a-project.org
Cc:     V Sujith Kumar Reddy <vsujithk@...eaurora.org>
Subject: Re: [PATCH v2] Asoc: qcom: lpass-cpu: Fix clock disable failure

On Mon, 19 Oct 2020 14:36:03 +0530, Srinivasa Rao Mandadapu wrote:
> Disable MI2S bit clock from PAUSE/STOP/SUSPEND usecase instead of
> shutdown time. Acheive this by invoking clk_disable API from
> cpu daiops trigger instead of cpu daiops shutdown.
> Change non-atomic API "clk_prepare_enable" to atomic API
> "clk_enable" in trigger, as trigger is being called from atomic context.
> 
> Fixes: commit 7e6799d8f87d ("ASoC: qcom: lpass-cpu: Enable MI2S BCLK and LRCLK together")

Applied to

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

Thanks!

[1/1] ASoC: qcom: lpass-cpu: Fix clock disable failure
      commit: 6ec6c3693a389841d8ca952072aea8020da54ef4

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