mbox series

[v3,0/2] ASoC: meson: g12a-toacodec: add support for SM1

Message ID 20210511074829.4110036-1-narmstrong@baylibre.com (mailing list archive)
Headers show
Series ASoC: meson: g12a-toacodec: add support for SM1 | expand

Message

Neil Armstrong May 11, 2021, 7:48 a.m. UTC 
This patchset adds Amlogic SM1 support on the TOACODEC driver, first by switching
to regmap fields for some bit fields to avoid code duplication, and then by adding
the corresponding bits & struct for the SM1 changed bits.

Changes since v2 at [2]:
- use raw values instead of defines in REG_FIELD() for g12a_toacodec_match_data

Changes since v1 at [1]:
- switch to regmap field

[1] https://lore.kernel.org/r/20210429170147.3615883-1-narmstrong@baylibre.com
[2] https://lore.kernel.org/r/20210505072607.3815442-1-narmstrong@baylibre.com

Neil Armstrong (2):
  ASoC: meson: g12a-toacodec: use regmap fields to prepare SM1 support
  ASoC: meson: g12a-toacodec: add support for SM1 TOACODEC

 sound/soc/meson/g12a-toacodec.c | 143 +++++++++++++++++++++++++++-----
 1 file changed, 124 insertions(+), 19 deletions(-)

Comments

Mark Brown May 19, 2021, 4:10 p.m. UTC | #1 
On Tue, 11 May 2021 09:48:27 +0200, Neil Armstrong wrote:
> This patchset adds Amlogic SM1 support on the TOACODEC driver, first by switching
> to regmap fields for some bit fields to avoid code duplication, and then by adding
> the corresponding bits & struct for the SM1 changed bits.
> 
> Changes since v2 at [2]:
> - use raw values instead of defines in REG_FIELD() for g12a_toacodec_match_data
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: meson: g12a-toacodec: use regmap fields to prepare SM1 support
      commit: 172dd9216d2b8a3fa162039d89c4361ef35c85ae
[2/2] ASoC: meson: g12a-toacodec: add support for SM1 TOACODEC
      commit: 7487238c5f530b418745ce134d1b0a7fba3a0d8d

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