linux-kernel - Re: [PATCH 1/4] ASoC: tas2764: Add post reset delays

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <165659332651.455663.13893837473957568987.b4-ty@kernel.org>
Date:   Thu, 30 Jun 2022 13:48:46 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>, povik+lin@...ebit.org
Cc:     dmurphy@...com, alsa-devel@...a-project.org, steve@....org,
        linux-kernel@...r.kernel.org, ckeepax@...nsource.cirrus.com,
        asahi@...ts.linux.dev, marcan@...can.st
Subject: Re: [PATCH 1/4] ASoC: tas2764: Add post reset delays

On Thu, 30 Jun 2022 09:51:32 +0200, Martin Povišer wrote:
> Make sure there is at least 1 ms delay from reset to first command as
> is specified in the datasheet. This is a fix similar to commit
> 307f31452078 ("ASoC: tas2770: Insert post reset delay").
> 
> 

Applied to

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

Thanks!

[1/4] ASoC: tas2764: Add post reset delays
      commit: 4aeb04227eb4d5de83343cfbad00433019ccfdf5
[2/4] ASoC: tas2764: Fix and extend FSYNC polarity handling
      commit: a1b2cfda5616ddccd54fa10b9e72932b3f3bce8b
[3/4] ASoC: tas2764: Correct playback volume range
      commit: aea21dbec799d63393b615b73e4708a5d036df99
[4/4] ASoC: tas2764: Fix amp gain register offset & default
      commit: cabcd219cee142a0f55516d2e257c8833cbd14f6

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