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:     codrin.ciubotariu@microchip.com,
        Guiting Shen <aarongt.shen@gmail.com>
Cc:     lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
        nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
        claudiu.beznea@microchip.com, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org
In-Reply-To: <20230715030620.62328-1-aarongt.shen@gmail.com>
References: <20230715030620.62328-1-aarongt.shen@gmail.com>
Subject: Re: [PATCH] ASoC: atmel: Fix the 8K sample parameter in I2SC
 master
Message-Id: <169030765461.1533302.9555599767367617746.b4-ty@kernel.org>
Date:   Tue, 25 Jul 2023 18:54:14 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Sat, 15 Jul 2023 11:06:20 +0800, Guiting Shen wrote:
> The 8K sample parameter of 12.288Mhz main system bus clock doesn't work
> because the I2SC_MR.IMCKDIV must not be 0 according to the sama5d2
> series datasheet(I2SC Mode Register of Register Summary).
> 
> So use the 6.144Mhz instead of 12.288Mhz to support 8K sample.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: atmel: Fix the 8K sample parameter in I2SC master
      commit: f85739c0b2b0d98a32f5ca4fcc5501d2b76df4f6

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