2023-09-20 04:00:46

by ChiYuan Huang

[permalink] [raw]
Subject: [PATCH v3 0/2] ASoC: Add rtq9128 audio amplifier

From: ChiYuan Huang <[email protected]>

This patch series adds Richtek rtq9128 automotive audio amplifier
support. It can deliver up to 4x75W into 4Ohm speaker from a 25V
supply in automotive applications.

Change log
v3
- Add Reviewed-by tag for dt binding patch
- Refine the source code by reviewer's comments
detail changes listed in the patch
- Add DVDD undervoltage threshold selection from HW guy's suggestion

v2
- dt document fix listed in patch extra comment

ChiYuan Huang (2):
ASoC: dt-bindings: Add Richtek rtq9128 audio amplifier
ASoC: codecs: Add Richtek rtq9128 audio amplifier support

.../bindings/sound/richtek,rtq9128.yaml | 54 ++
sound/soc/codecs/Kconfig | 15 +
sound/soc/codecs/Makefile | 2 +
sound/soc/codecs/rtq9128.c | 766 ++++++++++++++++++
4 files changed, 837 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound/richtek,rtq9128.yaml
create mode 100644 sound/soc/codecs/rtq9128.c

--
2.34.1


2023-09-21 18:58:59

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH v3 0/2] ASoC: Add rtq9128 audio amplifier

On Wed, 20 Sep 2023 11:50:32 +0800, [email protected] wrote:
> This patch series adds Richtek rtq9128 automotive audio amplifier
> support. It can deliver up to 4x75W into 4Ohm speaker from a 25V
> supply in automotive applications.
>
> Change log
> v3
> - Add Reviewed-by tag for dt binding patch
> - Refine the source code by reviewer's comments
> detail changes listed in the patch
> - Add DVDD undervoltage threshold selection from HW guy's suggestion
>
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: Add Richtek rtq9128 audio amplifier
commit: 0339eadb871ab1ebf249932fecb75ab13cc3c565
[2/2] ASoC: codecs: Add Richtek rtq9128 audio amplifier support
commit: 736064c64cf3fc51c6090884a9f4efe047f9f616

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