linux-kernel - Re: [PATCH] ASoC: cs35l56: Patch soft registers to defaults

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: <168971902372.127447.16837220353075580193.b4-ty@kernel.org>
Date:   Tue, 18 Jul 2023 23:23:43 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Patch soft registers to defaults

On Tue, 18 Jul 2023 15:46:25 +0100, Richard Fitzgerald wrote:
> The soft (firmware) registers for volume/mute/posture are not reset by
> a chip soft-reset, so use a regmap patch to set them to defaults.
> 
> cs35l56_reread_firmware_registers() has been removed. Its intent was to
> use whatever the firmware set as a default. But the driver now patches the
> defaults to the registers.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Patch soft registers to defaults
      commit: df4167d658d45946677f91d84e9d40570c875cb8

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