[v2,0/2] ASoC: tlv320aic32x4: Bugfixes for tlv320aic32x4 driver

Message

Annaliese McDermond March 31, 2021, 6:21 p.m. UTC

These are a couple of bugfixes for the tlv320aic32x4 driver
that we discovered after the Raspberry Pi Foundation's move to
the 5.10 kernel.

The first increases the maximum value in the regmap configuration
so that the powerup command actually works.

The second changes the ordering of the clock registration in the
module probe function so that the clocks are properly registered
before the component probe function runs.

Changes in v2:
- Corrected commit hashes in Fixes lines to be proper length
- Including inadvertently omitted maintainers on To list.

Annaliese McDermond (2):
  ASoC: tlv320aic32x4: Increase maximum register in regmap
  ASoC: tlv320aic32x4: Register clocks before registering component

 sound/soc/codecs/tlv320aic32x4.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

Comments

Mark Brown April 6, 2021, 5:39 p.m. UTC | #1

On Wed, 31 Mar 2021 18:21:36 +0000, Annaliese McDermond wrote:
> These are a couple of bugfixes for the tlv320aic32x4 driver
> that we discovered after the Raspberry Pi Foundation's move to
> the 5.10 kernel.
> 
> The first increases the maximum value in the regmap configuration
> so that the powerup command actually works.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: tlv320aic32x4: Increase maximum register in regmap
      commit: 29654ed8384e9dbaf4cfba689dbcb664a6ab4bb7
[2/2] ASoC: tlv320aic32x4: Register clocks before registering component
      commit: 1ca1156cfd69530e6b7cb99943baf90c8bd871a5

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