Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Mark Brown <broonie@kernel.org>
To:     thierry.reding@gmail.com, tiwai@suse.com, spujar@nvidia.com,
        robh+dt@kernel.org, catalin.marinas@arm.com, will@kernel.org,
        perex@perex.cz, krzysztof.kozlowski+dt@linaro.org
Cc:     linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
        jonathanh@nvidia.com, linux-arm-kernel@lists.infradead.org,
        alsa-devel@alsa-project.org, linux-tegra@vger.kernel.org
In-Reply-To: <1654238172-16293-1-git-send-email-spujar@nvidia.com>
References: <1654238172-16293-1-git-send-email-spujar@nvidia.com>
Subject: Re: (subset) [PATCH v3 0/6] OPE support on Tegra210 and later
Message-Id: <165459930944.399031.17402863866991236523.b4-ty@kernel.org>
Date:   Tue, 07 Jun 2022 11:55:09 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 3 Jun 2022 12:06:06 +0530, Sameer Pujar wrote:
> This series adds support for Output Prcoessing Module (OPE) module on
> Tegra210 and later generations of SoCs. OPE is a client of AHUB and
> it has sub blocks of PEQ (Parametric Equalizer) and MBDRC (Multi Band
> Dynamic Range Compressor) for data processing.
> 
> An ASoC component is registered for OPE, which includes PEQ and MBDRC
> functions as well. This can be plugged in audio path using ALSA mixer
> controls. The series adds necessary binding documentaion, driver and
> DT binding patches to enable OPE module on Jetson platforms.
> 
> [...]

Applied to

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

Thanks!

[1/6] ASoC: tegra: Add binding doc for OPE module
      commit: 45c6c5e052df2ee0d87e74743d8bb72e70fd0887
[2/6] ASoC: tegra: Add Tegra210 based OPE driver
      commit: 7358a803c778f28314721e78339f3fa5b787f55c
[3/6] ASoC: tegra: AHUB routes for OPE module
      commit: 7ee0910d03168535ffeea2f4ce924eebb3b24863

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