Asoc: qcom: lpass-cpu: Enable MI2S BCLK and LRCLK together
Subsystems (4)
PATCH 1/1 Asoc: qcom: lpass-cpu: Enable MI2S BCLK and LRCLK together
From: vsujithk <[email protected]>
Update lpass-cpu.c to enable I2S BCLK and LRCLK together. Remove BCLK enable in lpass_cpu_daiops_startup and add in lpass_cpu_daiops_trigger API.
--- sound/soc/qcom/lpass-cpu.c | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
sound/soc/qcom/lpass-cpu.c +8 -8
@@ -80,14 +80,6 @@ static int lpass_cpu_daiops_startup(struct snd_pcm_substream *substream,dev_err (dai->dev,"error in enabling mi2s osr clk: %d\n" , ret);return ret; } - - ret =clk_prepare_enable (drvdata->mi2s_bit_clk[dai->driver->id]); -if (ret) { -dev_err (dai->dev,"error in enabling mi2s bit clk: %d\n" , ret); -clk_disable_unprepare (drvdata->mi2s_osr_clk[dai->driver->id]); -return ret; - } -return 0 ; }
@@ -310,6 +302,14 @@ static int lpass_cpu_daiops_trigger(struct snd_pcm_substream *substream,if (ret)dev_err (dai->dev,"error writing to i2sctl reg: %d\n" , ret); + + ret =clk_prepare_enable (drvdata->mi2s_bit_clk[id]); +if (ret) { +dev_err (dai->dev,"error in enabling mi2s bit clk: %d\n" , ret); +clk_disable_unprepare (drvdata->mi2s_osr_clk[id]); +return ret; + } +break ;case SNDRV_PCM_TRIGGER_STOP :case SNDRV_PCM_TRIGGER_SUSPEND :
Signature · 2 lines
Qualcomm India Private Limited, on behalf of Qualcomm Innovation Center, Inc., is a member of Code Aurora Forum, a Linux Foundation Collaborative Project.
Mark Brown
maintainerQuoted 3 lines · Srinivasa Rao Mandadapu
Update
lpass-cpu.cto enable I2S BCLK and LRCLK together. Remove BCLK enable inlpass_cpu_daiops_startupand add inlpass_cpu_daiops_triggerAPI.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: qcom: lpass-cpu: Enable MI2S BCLK and LRCLK together
commit: 7e6799d8f87d7ab7ae55a229654d161b5bfae874
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