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;
From:   Mark Brown <broonie@kernel.org>
To:     festevam@gmail.com, lgirdwood@gmail.com,
        sebastian.krzyszkowiak@puri.sm, linux-kernel@vger.kernel.org,
        perex@perex.cz, ckeepax@opensource.cirrus.com,
        gustavoars@kernel.org, patches@opensource.cirrus.com,
        alsa-devel@alsa-project.org, tiwai@suse.com,
        kuninori.morimoto.gx@renesas.com,
        Shengjiu Wang <shengjiu.wang@nxp.com>
In-Reply-To: <1615170877-25918-1-git-send-email-shengjiu.wang@nxp.com>
References: <1615170877-25918-1-git-send-email-shengjiu.wang@nxp.com>
Subject: Re: [PATCH v2] ASoC: wm8962: Relax bit clock divider searching
Message-Id: <161521960849.9621.6433725701226320562.b4-ty@kernel.org>
Date:   Mon, 08 Mar 2021 16:06:48 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 8 Mar 2021 10:34:37 +0800, Shengjiu Wang wrote:
> With S20_3LE format case, the sysclk = rate * 384,
> the bclk = rate * 20 * 2, there is no proper bclk divider
> for 384 / 40, because current condition needs exact match.
> So driver fails to configure the clocking:
> 
> wm8962 3-001a: Unsupported BCLK ratio 9
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: wm8962: Relax bit clock divider searching
      commit: 51309c5bec7cfe567a00a667adbffea444845543

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