linux-kernel - Re: [PATCH] ASoC: cs35l56: Handle OTP read latency over SoundWire

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: <172288603184.71820.8835151203364100477.b4-ty@kernel.org>
Date: Mon, 05 Aug 2024 20:27:11 +0100
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Handle OTP read latency over SoundWire

On Mon, 05 Aug 2024 15:08:39 +0100, Richard Fitzgerald wrote:
> Use the late-read buffer in the CS35L56 SoundWire interface to
> read OTP memory.
> 
> The OTP memory has a longer access latency than chip registers
> and cannot guarantee to return the data value in the SoundWire
> control response if the bus clock is >4.8 MHz. The Cirrus
> SoundWire peripheral IP exposes the bridge-to-bus read buffer
> and status bits. For a read from OTP the bridge status bits are
> polled to wait for the OTP data to be loaded into the read buffer
> and the data is then read from there.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Handle OTP read latency over SoundWire
      commit: e42066df07c0fcedebb32ed56f8bc39b4bf86337

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