[v1,0/3] ASoC: codecs: ES8326

Message

Zhu Ning Nov. 1, 2023, 7:26 a.m. UTC

Hi ,

    3 patches here for the es8326 driver...
    
    We developed a new version of the chip. 3 Three patches are used for 
    compatibility with the old and new versions of the chip.We did tests 
    with the new driver at version_v0 and version_v3.The test results
    from the test department met our expectations.Both versions work well 
    with the new drivers.

Thanks,
Zhuning.

Zhu Ning (3):
  ASoC: codecs: ES8326: Add chip version flag
  ASoC: codecs: ES8326: Changing initialisation and broadcasting
  ASoC: codecs: ES8326: Changing the headset detection time

 sound/soc/codecs/es8326.c | 231 +++++++++++++++++++++++---------------
 1 file changed, 139 insertions(+), 92 deletions(-)
 mode change 100644 => 100755 sound/soc/codecs/es8326.c

Comments

Mark Brown Nov. 13, 2023, 7:40 p.m. UTC | #1

On Wed, 01 Nov 2023 15:26:59 +0800, Zhu Ning wrote:
>     3 patches here for the es8326 driver...
> 
>     We developed a new version of the chip. 3 Three patches are used for
>     compatibility with the old and new versions of the chip.We did tests
>     with the new driver at version_v0 and version_v3.The test results
>     from the test department met our expectations.Both versions work well
>     with the new drivers.
> 
> [...]

Applied to

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

Thanks!

[1/3] ASoC: codecs: ES8326: Add chip version flag
      commit: ee09084fbf9fdda6bf0179bcdca52196d0cde8a1
[2/3] ASoC: codecs: ES8326: Changing initialisation and broadcasting
      commit: fc702b2c04d778d7e3a4091ebe54a86c5d0a0d96
[3/3] ASoC: codecs: ES8326: Changing the headset detection time
      commit: 8a81491adbd9b25a648704c9825adaefb0c31868

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