[PATCH v6 00/12] ASoC: qcom: Add support for SC7180 lpass variant

[Mark Brown]

On Fri, 14 Aug 2020 16:22:56 +0530, Rohit kumar wrote:
> This patch chain add audio support for SC7180 soc by doing the required
> modification in existing common lpass-cpu/lpass-platform driver.
> This also fixes some concurrency issue.
> 
> This patch series is already tested by Srinivas on Dragon Board 410c.
> Changes since v5:
>         - Fixed remove api in lpass-sc7180.c
>         - Addressed comments by Rob in yaml Documentation.
> 
> [...]

Applied to

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

Thanks!

[01/12] ASoC: qcom: Add common array to initialize soc based core clocks
        commit: 1220f6a76e77af8ac14fe67a11fcd7806764ea46
[02/12] ASoC: qcom: lpass-cpu: Move ahbix clk to platform specific function
        commit: a503567d70eca91796a4ab23053d4c70df8e1e3e
[03/12] ASoC: qcom: lpass-platform: Replace card->dev with component->dev
        commit: 784771863abae5f8878c62e9c624111c51bebe7c
[04/12] ASoC: qcom: lpass-platform: fix memory leak
        commit: 5fd188215d4eb52703600d8986b22311099a5940
[05/12] ASoC: qcom: lpass: Use regmap_field for i2sctl and dmactl registers
        commit: b5022a36d28f6a99c1a57f54246e8b566cf094d5
[06/12] ASoC: qcom: lpass-cpu: fix concurrency issue
        commit: 753a6e17942f6f425ca622e1610625998312ad89
[07/12] ASoC: Add sc7180 lpass cpu node
        commit: 2a7a3797ed2de6a55e1467bd11002fa7b13e12f3
[08/12] ASoC: Add sc7180-lpass bindings header
        commit: 68d8904b25df28821425753eaebc8fe992dde236
[09/12] ASoC: qcom: lpass-sc7180: Add platform driver for lpass audio
        commit: 24caf8d9eb108c52e144bcc7af94bb1edcb70700
[10/12] ASoC: qcom: lpass-cpu: Use platform_get_resource
        commit: 93dbbd657167a796583506834cc03950ce25bce1
[11/12] ASoC: qcom: lpass-platform: Use platform_get_irq
        commit: b05372c84d61ad2a905274db7e3d63a65c835463
[12/12] ASoC: lpass-cpu: Move to yaml format
        commit: 4b381d7e86fd0b767456e07c49982fb4896e1166

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