[v4,0/3] ASoC: wm8782: Allow higher audio rates

Message

John Watts Sept. 18, 2023, 1:15 p.m. UTC

The wm8782 supports higher audio rates than just 48kHz. This is
configured by setting the FSAMPEN pin on the codec chip.

This patch series introduces the 'wlf,fsampen' device tree property
to indicate the pin status and control the maximum rate available
when using the codec.

v3 -> v4:
- Default value is specified in device tree documentation

v2 -> v3:
- Rate is now properly constrained using ALSA constraints

v1 -> v2:
- Switched from max-rate property to wlf,fsampen property
- Clarified property is optional, not required

John Watts (3):
  ASoC: wm8782: Constrain maximum audio rate at runtime
  ASoC: wm8782: Use wlf,fsampen device tree property
  ASoC: dt-bindings: wlf,wm8782: Add wlf,fsampen property

 .../devicetree/bindings/sound/wm8782.txt      |  7 +++
 sound/soc/codecs/wm8782.c                     | 63 +++++++++++++++----
 2 files changed, 57 insertions(+), 13 deletions(-)

Comments

Mark Brown Sept. 18, 2023, 4:06 p.m. UTC | #1

On Mon, 18 Sep 2023 23:15:29 +1000, John Watts wrote:
> The wm8782 supports higher audio rates than just 48kHz. This is
> configured by setting the FSAMPEN pin on the codec chip.
> 
> This patch series introduces the 'wlf,fsampen' device tree property
> to indicate the pin status and control the maximum rate available
> when using the codec.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: wm8782: Constrain maximum audio rate at runtime
      commit: 00524a8415aa400567538c0e75a463d517cded7f
[2/3] ASoC: wm8782: Use wlf,fsampen device tree property
      commit: 5d34887eab8daad8f63d584ae4d12d480beb9f0e
[3/3] ASoC: dt-bindings: wlf,wm8782: Add wlf,fsampen property
      commit: 5d5529b0057146043a4328aa194280299ba966c2

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