mbox series

[0/3] Improvements for mchp-pdmc

Message ID 20240911122909.133399-1-andrei.simion@microchip.com (mailing list archive)
Headers show
Series Improvements for mchp-pdmc | expand

Message

Andrei Simion Sept. 11, 2024, 12:29 p.m. UTC
This patch set is intended to enhance the functionality and maintainability
of the mchp-pdmc driver:
- Enhances performance by refining maxburst logic.
- Introduces a name for better identification and management.
- Ensures controls remain intact when streams start/finish,
  returning -EBUSY if the controller is busy.

Codrin Ciubotariu (3):
  ASoC: atmel: mchp-pdmc: Improve maxburst calculation for better
    performance
  ASoC: atmel: mchp-pdmc: Add snd_soc_dai_driver name
  ASoC: atmel: mchp-pdmc: Retain Non-Runtime Controls

 sound/soc/atmel/mchp-pdmc.c | 118 +++++++++++++++++++-----------------
 1 file changed, 63 insertions(+), 55 deletions(-)


base-commit: 6708132e80a2ced620bde9b9c36e426183544a23

Comments

Mark Brown Sept. 12, 2024, 4:42 p.m. UTC | #1
On Wed, 11 Sep 2024 15:29:06 +0300, Andrei Simion wrote:
> This patch set is intended to enhance the functionality and maintainability
> of the mchp-pdmc driver:
> - Enhances performance by refining maxburst logic.
> - Introduces a name for better identification and management.
> - Ensures controls remain intact when streams start/finish,
>   returning -EBUSY if the controller is busy.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: atmel: mchp-pdmc: Improve maxburst calculation for better performance
      commit: 8f0280c84607afe122788e508a171ba163d71be6
[2/3] ASoC: atmel: mchp-pdmc: Add snd_soc_dai_driver name
      commit: e6b95bdc1e333e14e4fdf71fd4e8962429d9b6cd
[3/3] ASoC: atmel: mchp-pdmc: Retain Non-Runtime Controls
      (no commit info)

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