Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     lgirdwood@gmail.com, alsa-devel@alsa-project.org,
        shengjiu.wang@nxp.com, Xiubo.Lee@gmail.com,
        shengjiu.wang@gmail.com, nicoleotsuka@gmail.com, perex@perex.cz,
        festevam@gmail.com, tiwai@suse.com
Cc:     linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
In-Reply-To: <1657100575-8261-1-git-send-email-shengjiu.wang@nxp.com>
References: <1657100575-8261-1-git-send-email-shengjiu.wang@nxp.com>
Subject: Re: [PATCH] ASoC: imx-card: Fix DSD/PDM mclk frequency
Message-Id: <165711657225.3718491.10041938555621440041.b4-ty@kernel.org>
Date:   Wed, 06 Jul 2022 15:09:32 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 6 Jul 2022 17:42:55 +0800, Shengjiu Wang wrote:
> The DSD/PDM rate not only DSD64/128/256/512, which are the
> multiple rate of 44.1kHz,  but also support the multiple
> rate of 8kHz, so can't force all mclk frequency to be
> 22579200Hz, need to assign the frequency according to
> rate.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: imx-card: Fix DSD/PDM mclk frequency
      commit: c0fabd12a8570cb932f13d9388f3d887ad44369b

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