mbox series

[v2,0/2] ASoC: stm32: i2s: add stm32mp25 support

Message ID 20241107144712.1305638-1-olivier.moysan@foss.st.com (mailing list archive)
Headers show
Series ASoC: stm32: i2s: add stm32mp25 support | expand

Message

Olivier Moysan Nov. 7, 2024, 2:47 p.m. UTC
Update STM32 I2S driver and binding to support STM32MP25 SoCs.

Changes in v2:
- Rearrange clocks and clock-names ranges depending on compatible.

Olivier Moysan (2):
  ASoC: dt-bindings: add stm32mp25 support for i2s
  ASoC: stm32: i2s: add stm32mp25 support

 .../bindings/sound/st,stm32-i2s.yaml          |  36 ++-
 sound/soc/stm/stm32_i2s.c                     | 211 ++++++++++++++++--
 2 files changed, 222 insertions(+), 25 deletions(-)


base-commit: 2fd094b86c8ae266b618359e4154ab94e806a412

Comments

Mark Brown Nov. 9, 2024, 3:13 a.m. UTC | #1
On Thu, 07 Nov 2024 15:47:10 +0100, Olivier Moysan wrote:
> Update STM32 I2S driver and binding to support STM32MP25 SoCs.
> 
> Changes in v2:
> - Rearrange clocks and clock-names ranges depending on compatible.
> 
> Olivier Moysan (2):
>   ASoC: dt-bindings: add stm32mp25 support for i2s
>   ASoC: stm32: i2s: add stm32mp25 support
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: add stm32mp25 support for i2s
      commit: c69b7edc10d2fff4bcb3dd464ee26cbf22818fec
[2/2] ASoC: stm32: i2s: add stm32mp25 support
      commit: 125d0f698ad500b0092812e52a6c342ba055ae68

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