mbox series

[v2,0/3] ASoC: nau8822: add MCLK support

Message ID 20240613084652.13113-1-andrejs.cainikovs@gmail.com (mailing list archive)
Headers show
Series ASoC: nau8822: add MCLK support | expand

Message

Andrejs Cainikovs June 13, 2024, 8:46 a.m. UTC
From: Andrejs Cainikovs <andrejs.cainikovs@toradex.com>

This change adds local MCLK handling, which would cover a case when a
reference audio clock is present in a system, but is not allowed to be
changed, see [1].

[1]: https://lore.kernel.org/all/ZfBdxrzX3EnPuGOn@ediswmail9.ad.cirrus.com/

v1:
  - https://lore.kernel.org/all/20240409121719.337709-1-andrejs.cainikovs@gmail.com/

v2:
  - Fixes the issue of unbalanced clock enable and disable which resulted
    in a negative clock reference count. This triggered "already disabled"
    warning when the system was suspended.

Andrejs Cainikovs (3):
  ASoC: nau8822: move nau8822_set_dai_sysclk()
  ASoC: nau8822: set NAU8822_REFIMP_80K only once
  ASoC: nau8822: add MCLK support

 sound/soc/codecs/nau8822.c | 76 +++++++++++++++++++++++++++++---------
 sound/soc/codecs/nau8822.h |  1 +
 2 files changed, 60 insertions(+), 17 deletions(-)

Comments

Mark Brown June 23, 2024, 5:21 p.m. UTC | #1
On Thu, 13 Jun 2024 10:46:49 +0200, Andrejs Cainikovs wrote:
> This change adds local MCLK handling, which would cover a case when a
> reference audio clock is present in a system, but is not allowed to be
> changed, see [1].
> 
> [1]: https://lore.kernel.org/all/ZfBdxrzX3EnPuGOn@ediswmail9.ad.cirrus.com/
> 
> v1:
>   - https://lore.kernel.org/all/20240409121719.337709-1-andrejs.cainikovs@gmail.com/
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: nau8822: move nau8822_set_dai_sysclk()
      commit: 9292013bd3738bd00ee78bf1705620a9881031b5
[2/3] ASoC: nau8822: set NAU8822_REFIMP_80K only once
      commit: 9c3b21cc8528d52321c66236c3b794300c78d9e6
[3/3] ASoC: nau8822: add MCLK support
      commit: 2604faa7b71291b0ccd17f8d6009f3ff6dae287b

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