Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 01 Jul 2020 23:22:40 +0100
From:   Mark Brown <broonie@kernel.org>
To:     lgirdwood@gmail.com, Peter Ujfalusi <peter.ujfalusi@ti.com>,
        robh+dt@kernel.org
Cc:     alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
        devicetree@vger.kernel.org
In-Reply-To: <20200630125843.11561-1-peter.ujfalusi@ti.com>
References: <20200630125843.11561-1-peter.ujfalusi@ti.com>
Subject: Re: [PATCH v4 0/3] ASoC: ti: Add support for audio on J721e EVM
Message-Id: <159364215574.10630.2058528286314798186.b4-ty@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, 30 Jun 2020 15:58:40 +0300, Peter Ujfalusi wrote:
> Changes since v3:
> - Fix the single clock source handling and typo
> 
> Changes since v2:
> - DT binding:
>  - use proper (?) patch subject for the binding docuemtn patch
>  - drop pll4 and pll15 from DT - driver should check the rate via
>    clk_get_parent. If it is not available (as it is not currently) then use the
>    match_data provided rates.
>  - add simple explanation for the clocking setup
>  - Use descriptive names for clocks: cpb/ivi-mcasp-auxclk and cpb/ivi-codec-scki
>  - dt_binding_check shows no errors/warnings
> - ASoC machine driver:
>  - Try to read the PLL4/15 rate with clk API (parent of the two clock divider)
>    if it is not available then use the match_data provided numbers.
>  - Support for single PLL setup
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: ti: davinci-mcasp: Specify stream_name for playback/capture
      commit: ef3ab250aad9920fa7fd6280051c92a488109b87
[2/3] ASoC: dt-bindings: Add documentation for TI j721e EVM (CPB and IVI)
      commit: 8142500e7dc0d214e3c7a22788116f71cd84f07b
[3/3] ASoC: ti: Add custom machine driver for j721e EVM (CPB and IVI)
      commit: 6748d05590594837e42dfa975879fb275099f0b2

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