Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Mark Brown <broonie@kernel.org>
To:     srinivas.kandagatla@linaro.org, bjorn.andersson@linaro.org,
        swboyd@chromium.org, tiwai@suse.com, vkoul@kernel.org,
        linux-arm-msm@vger.kernel.org, agross@kernel.org,
        quic_plai@quicinc.com, bgoswami@quicinc.com,
        devicetree@vger.kernel.org, judyhsiao@chromium.org,
        robh+dt@kernel.org, lgirdwood@gmail.com, quic_rohkumar@quicinc.com,
        perex@perex.cz, linux-kernel@vger.kernel.org,
        quic_srivasam@quicinc.com, alsa-devel@alsa-project.org
In-Reply-To: <1652877755-25120-1-git-send-email-quic_srivasam@quicinc.com>
References: <1652877755-25120-1-git-send-email-quic_srivasam@quicinc.com>
Subject: Re: [PATCH v2] ASoC: qcom: soundwire: Add support for controlling audio CGCR from HLOS
Message-Id: <165459871566.301808.10281011736457954166.b4-ty@kernel.org>
Date:   Tue, 07 Jun 2022 11:45:15 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 18 May 2022 18:12:35 +0530, Srinivasa Rao Mandadapu wrote:
> Add support for controlling soundwire audio CGCR interface using clock
> framework to make hclk ungating with software. As per new hardware
> changes, software has to always ungate hclk if soundwire is operational
> and keep it running. This requirement is for latest LPASS chipsets for
> RX, TX and WSA path to work.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: qcom: soundwire: Add support for controlling audio CGCR from HLOS
      commit: 32882881078bd8f8fae47ff69c102d9e691f5bb9

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