Re: [PATCH v2 0/4] ASoC: Add Richtek rt9123 and rt9123p support

[Mark Brown]

On Thu, 10 Apr 2025 08:58:09 +0800, cy_huang@xxxxxxxxxxx wrote:
> This patch series adds Richtek rt9123 and rt9123p support.
> It's a 3.2W mono Class-D audio amplifier.
> 
> Since v2
> [PATCH 2/4]
> - include bitfield header file to fix kernel test robot issue
>   https://lore.kernel.org/oe-kbuild-all/202504052206.HFqFRXUk-lkp@xxxxxxxxx/
> - Use #ifdef CONFIG_PM to only inlucde 'runtime_resume' and
>   'runtime_suspend', this will fix kernel test robot issue
>   https://lore.kernel.org/oe-kbuild-all/202504052244.bgS5yxev-lkp@xxxxxxxxx/
> - Check vendor-id before triggering SW_RST
> - Fix 'SW_RST' write date non swap issue and add the wait delay for sw_reset
> - Rename control name from 'SPK Gain Volume' to 'Speaker Volume'
> - Change regmap cache type to _MAPLE
> - Since ID check run once, to speed up regmap cache init, modify
>   num_reg_defaults_raw from 0xf2 'COMBOID' to 0x36 'ANAFLAG'
> - Add comments to describe why use pm runtime for RG special handling
> [PATCH 3/4]
> - Modify the property name from 'enable-delay' to 'enable-delay-ms' to make the
>   time unit more specific
> [PATCH 4/4]
> - Update the property parsing from 'enable-delay' to 'enable-delay-ms'
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: dt-bindings: Add bindings for Richtek rt9123
      commit: 667ebcc13dd63f59e2a1132e0f54d2f3067597db
[2/4] ASoC: codecs: Add support for Richtek rt9123
      commit: 8bffd24e45618b6c3d6ce11947193c6d8ba846a7
[3/4] ASoC: dt-bindings: Add bindings for Richtek rt9123p
      commit: 4a046b67d2d267daf884798ee8509a502abe7a58
[4/4] ASoC: codecs: Add support for Richtek rt9123p
      commit: 38c2585c7439cc678ae105dd826f10321db29552

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