linux-kernel - Re: [PATCH] ASoC: cs42l42: Use two thresholds and increased wait time for manual type detection

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 for Android: free password hash cracker in your pocket

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

Message-Id: <163276442024.18200.9987078305118050259.b4-ty@kernel.org>
Date:   Mon, 27 Sep 2021 18:45:29 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        James Schulman <james.schulman@...rus.com>,
        Takashi Iwai <tiwai@...e.com>,
        Vitaly Rodionov <vitalyr@...nsource.cirrus.com>,
        David Rhodes <david.rhodes@...rus.com>,
        Jaroslav Kysela <perex@...ex.cz>
Cc:     Mark Brown <broonie@...nel.org>, patches@...nsource.cirrus.com,
        linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        Stefan Binding <sbinding@...nsource.cirrus.com>
Subject: Re: [PATCH] ASoC: cs42l42: Use two thresholds and increased wait time for manual type detection

On Mon, 27 Sep 2021 12:14:37 +0100, Vitaly Rodionov wrote:
> From: Stefan Binding <sbinding@...nsource.cirrus.com>
> 
> Some headsets require very different comparator thresholds for type detection,
> as well as longer settling times. In order to detect a larger number of headsets,
> use 2 thresholds to give maximum coverage (1.25V and 1.75V), as well as a longer
> settling time of 100ms. This will not affect default audotodetect mode
> and applies to manual mode type detection only.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs42l42: Use two thresholds and increased wait time for manual type detection
      commit: edd6dffdc6670836909972b32a324dbf6c150757

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