ASoC: es8323: Playback enablement for Firefly ITX-3588J and similar hardware

[PATCH 0/2] ASoC: es8323: Playback enablement for Firefly ITX-3588J and similar hardware

Posted by Shimrra Shai 1 month, 3 weeks ago

This small pair of patches is needed to enable the audio output to
speaker using the ES8323 CODEC on boards like the Firefly ITX-3588J
that use the right-hand DAC mixer to connect the line out jack. I also
enable associated DAPM power widgets so that the volume can be
controlled in the ALSA mixer. This seems sufficient to me to produce
basic audio functionality on this board and any others that might use
the same features. I tested it with both ear buds and a pair of
speakers plugged into the green jack on the back of the board.

Shimrra Shai (2):
  ASoC: es8323: enable right-hand DAC-mixer connection on ES8323
  ASoC: es8323: enable DAPM power widgets for playback DAC and output

 sound/soc/codecs/es8323.c | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

-- 
2.48.1

Re: (subset) [PATCH 0/2] ASoC: es8323: Playback enablement for Firefly ITX-3588J and similar hardware

Posted by Mark Brown 1 month, 3 weeks ago

On Wed, 13 Aug 2025 20:26:49 -0500, Shimrra Shai wrote:
> This small pair of patches is needed to enable the audio output to
> speaker using the ES8323 CODEC on boards like the Firefly ITX-3588J
> that use the right-hand DAC mixer to connect the line out jack. I also
> enable associated DAPM power widgets so that the volume can be
> controlled in the ALSA mixer. This seems sufficient to me to produce
> basic audio functionality on this board and any others that might use
> the same features. I tested it with both ear buds and a pair of
> speakers plugged into the green jack on the back of the board.
> 
> [...]

Applied to

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

Thanks!

[2/2] ASoC: es8323: enable DAPM power widgets for playback DAC and output
      commit: 258384d8ce365dddd6c5c15204de8ccd53a7ab0a

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