[0/2] ASoC: mediatek: mt8183-mt6358: support machine driver for rt1015p

Message

Tzung-Bi Shih March 11, 2021, 3:31 a.m. UTC

The series reuses mt8183-mt6358-ts3a227-max98357.c for supporting
machine driver with rt1015p speaker amplifier.

The 1st patch adds document for the new proposed compatible string.

The 2nd patch changes the machine driver to support "RT1015P" codec.

Tzung-Bi Shih (2):
  ASoC: dt-bindings: mt8183: add compatible string for using rt1015p
  ASoC: mediatek: mt8183: support machine driver with rt1015p

 .../sound/mt8183-mt6358-ts3a227-max98357.txt  |  1 +
 sound/soc/mediatek/Kconfig                    |  1 +
 .../mt8183/mt8183-mt6358-ts3a227-max98357.c   | 29 +++++++++++++++++++
 3 files changed, 31 insertions(+)

Comments

Mark Brown March 11, 2021, 4:18 p.m. UTC | #1

On Thu, 11 Mar 2021 11:31:49 +0800, Tzung-Bi Shih wrote:
> The series reuses mt8183-mt6358-ts3a227-max98357.c for supporting
> machine driver with rt1015p speaker amplifier.
> 
> The 1st patch adds document for the new proposed compatible string.
> 
> The 2nd patch changes the machine driver to support "RT1015P" codec.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: mt8183: add compatible string for using rt1015p
      commit: 5fd6b9b8b1c477fb695e3ae313ffb70b3cc88dc9
[2/2] ASoC: mediatek: mt8183: support machine driver with rt1015p
      commit: 9dc21a066bb6bff55d889f22460f1bf236a9a4a3

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