[v1,0/3] ASoC: atmel: Fixes for AT91SAM9G20-EK audio driver

Message

Mark Brown March 25, 2022, 3:42 p.m. UTC

At some point the machine driver for the audio subsystem on the
AT91SAM9G20-EK appears to have bitrotted, no longer probing due to
effects of the transition to the common clock framework. The first patch
in this series fixes the initial probe problem, with the rest of the
series being random other fixes and cleanups I noticed while looking at
the driver.

Mark Brown (3):
  ASoC: atmel: Remove system clock tree configuration for at91sam9g20ek
  ASoC: atmel: Fix error handling in at91samg20ek probe()
  ASoC: atmel: Don't squash error codes from atmel_ssc_set_audio()

 sound/soc/atmel/sam9g20_wm8731.c | 74 ++++----------------------------
 1 file changed, 8 insertions(+), 66 deletions(-)


base-commit: f590797fa3c1bccdd19e55441592a23b46aef449

Comments

Mark Brown April 5, 2022, 9:31 a.m. UTC | #1

On Fri, 25 Mar 2022 15:42:38 +0000, Mark Brown wrote:
> At some point the machine driver for the audio subsystem on the
> AT91SAM9G20-EK appears to have bitrotted, no longer probing due to
> effects of the transition to the common clock framework. The first patch
> in this series fixes the initial probe problem, with the rest of the
> series being random other fixes and cleanups I noticed while looking at
> the driver.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: atmel: Remove system clock tree configuration for at91sam9g20ek
      commit: c775cbf62ed4911e4f0f23880f01815753123690
[2/3] ASoC: atmel: Fix error handling in at91samg20ek probe()
      commit: 28103509248b94392e04a8ffcbc47da5e3e31dfc
[3/3] ASoC: atmel: Don't squash error codes from atmel_ssc_set_audio()
      commit: 01251dd004d8e106295c3aa8e3ba890f0dd55e02

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