linux-kernel - Re: [PATCH] ASoC: cs42l42: Ensure 0dB full scale volume is used for headsets

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: <163403898174.2091644.6707785151456646793.b4-ty@kernel.org>
Date:   Tue, 12 Oct 2021 12:45:18 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     Mark Brown <broonie@...nel.org>,
        Stefan Binding <sbinding@...nsource.cirrus.com>,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: cs42l42: Ensure 0dB full scale volume is used for headsets

On Mon, 11 Oct 2021 15:49:03 +0100, Richard Fitzgerald wrote:
> From: Stefan Binding <sbinding@...nsource.cirrus.com>
> 
> Ensure the default 0dB playback path is always used.
> 
> The code that set FULL_SCALE_VOL based on LOAD_DET_RCSTAT was
> spurious, and resulted in a -6dB attenuation being accidentally
> inserted into the playback path.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs42l42: Ensure 0dB full scale volume is used for headsets
      commit: aa18457c4af7a9dad1f2b150b11beae1d8ab57aa

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