[0/4] TAS2770 fixes

Message

Martin Povišer Aug. 8, 2022, 2:12 p.m. UTC

The first two fixes should be straightforward.

The latter two clean up what looks to me like a mess in the setting of
power levels. However we settle it, we should then do the same changes
to TAS2764, which has the same template (and maybe there are other
drivers).

Martin Povišer (4):
  ASoC: tas2770: Set correct FSYNC polarity
  ASoC: tas2770: Allow mono streams
  ASoC: tas2770: Drop conflicting set_bias_level power setting
  ASoC: tas2770: Fix handling of mute/unmute

 sound/soc/codecs/tas2770.c | 98 +++++++++++++++++---------------------
 sound/soc/codecs/tas2770.h |  5 ++
 2 files changed, 48 insertions(+), 55 deletions(-)

Comments

Mark Brown Aug. 10, 2022, 12:44 p.m. UTC | #1

On Mon, 8 Aug 2022 16:12:42 +0200, Martin Povišer wrote:
> The first two fixes should be straightforward.
> 
> The latter two clean up what looks to me like a mess in the setting of
> power levels. However we settle it, we should then do the same changes
> to TAS2764, which has the same template (and maybe there are other
> drivers).
> 
> [...]

Applied to

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

Thanks!

[1/4] ASoC: tas2770: Set correct FSYNC polarity
      commit: e9ac31f0a5d0e246b046c20348954519f91a297f
[2/4] ASoC: tas2770: Allow mono streams
      commit: bf54d97a835dfe62d4d29e245e170c63d0089be7
[3/4] ASoC: tas2770: Drop conflicting set_bias_level power setting
      commit: 482c23fbc7e9bf5a7a74defd0735d5346215db58
[4/4] ASoC: tas2770: Fix handling of mute/unmute
      commit: 1e5907bcb3a3b569be0a03ebe668bba2ed320a50

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