From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Handle OTP read latency over SoundWire
Date: Mon, 05 Aug 2024 20:27:11 +0100 [thread overview]
Message-ID: <172288603184.71820.8835151203364100477.b4-ty@kernel.org> (raw)
In-Reply-To: <20240805140839.26042-1-rf@opensource.cirrus.com>
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
prev parent reply other threads:[~2024-08-05 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 14:08 Richard Fitzgerald
2024-08-05 19:27 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=172288603184.71820.8835151203364100477.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®