[0/5] TAS2764 fixes/extensions

Message

Martin Povišer Aug. 25, 2022, 2:02 p.m. UTC

First three patches are fixes analogical to those recently done to
the TAS2770 driver.
Link: https://lore.kernel.org/asahi/[e-mail]/T/#t

The latter two add IRQ handler to log faults and expose a new control.

Martin Povišer (5):
  ASoC: tas2764: Allow mono streams
  ASoC: tas2764: Drop conflicting set_bias_level power setting
  ASoC: tas2764: Fix mute/unmute
  ASoC: tas2764: Add IRQ handling
  ASoC: tas2764: Export highpass filter setting

 sound/soc/codecs/tas2764.c | 181 ++++++++++++++++++++++++++-----------
 sound/soc/codecs/tas2764.h |  23 +++++
 2 files changed, 152 insertions(+), 52 deletions(-)

Comments

Mark Brown Aug. 29, 2022, 3:57 p.m. UTC | #1

On Thu, 25 Aug 2022 16:02:36 +0200, Martin Povišer wrote:
> First three patches are fixes analogical to those recently done to
> the TAS2770 driver.
> Link: https://lore.kernel.org/asahi/[e-mail]/T/#t
> 
> The latter two add IRQ handler to log faults and expose a new control.
> 
> Martin Povišer (5):
>   ASoC: tas2764: Allow mono streams
>   ASoC: tas2764: Drop conflicting set_bias_level power setting
>   ASoC: tas2764: Fix mute/unmute
>   ASoC: tas2764: Add IRQ handling
>   ASoC: tas2764: Export highpass filter setting
> 
> [...]

Applied to

   broonie/sound.git for-next

Thanks!

[1/5] ASoC: tas2764: Allow mono streams
      commit: 23204d928a27146d13e11c9383632775345ecca8
[2/5] ASoC: tas2764: Drop conflicting set_bias_level power setting
      commit: 09273f38832406db19a8907a934687cc10660a6b
[3/5] ASoC: tas2764: Fix mute/unmute
      commit: f5ad67f13623548e5aff847f89700c178aaf2a98
[4/5] ASoC: tas2764: Add IRQ handling
      commit: dae191fb957f82fbf570d13c060110eb278813ec
[5/5] ASoC: tas2764: Export highpass filter setting
      commit: aca86ec9a02a4d6099dbe23d1078faa005d58422

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