Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>
Cc: <tiwai@suse.com>, <linux-sound@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH 1/2] firmware: cs_dsp: Remove async regmap writes
Date: Tue, 25 Feb 2025 16:22:49 +0000	[thread overview]
Message-ID: <a027bb81-01a9-4658-a089-8035ae5f0815@opensource.cirrus.com> (raw)
In-Reply-To: <e2f3397b-05c0-42f7-9950-29c4d9b24350@sirena.org.uk>

On 25/02/2025 3:15 pm, Mark Brown wrote:
> On Tue, Feb 25, 2025 at 01:18:42PM +0000, Richard Fitzgerald wrote:
> 
>> The async writes are a 12-year-old workaround for inefficiency of
>> synchronous writes in the SPI subsystem. The SPI subsystem has since
>> been changed to avoid the overheads, so this workaround should not be
>> necessary.
> 
> That wasn't really the issue, it was that on systems with low numbers of
> slower cores (especially single core but there were some dual core
> systems too) there was a surprisingly low threashold where it was useful
> to overlap the marshalling of data to send to the device with
> transmitting already marshalled data.  SMP adds locking requirements
> which loose a lot of the gains, and it's controller dependent where the
> cuttoff points for interrupts and/or DMA are.

Ok. It was a very long time ago.
Do you want a V2 with a commit message that doesn't libel the SPI
framework?

FWIW switching to sync write reduced the download of small amp firmware
by 200ms on a 1.67MHz SPI bus.

  reply	other threads:[~2025-02-25 16:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 13:18 [PATCH 0/2] ALSA: cs35l56: Fix for races when soft-resetting on SPI Richard Fitzgerald
2025-02-25 13:18 ` [PATCH 1/2] firmware: cs_dsp: Remove async regmap writes Richard Fitzgerald
2025-02-25 15:15   ` Mark Brown
2025-02-25 16:22     ` Richard Fitzgerald [this message]
2025-02-25 16:37       ` Mark Brown
2025-02-25 13:18 ` [PATCH 2/2] ASoC: cs35l56: Prevent races when soft-resetting using SPI control Richard Fitzgerald
2025-02-25 17:04 ` [PATCH 0/2] ALSA: cs35l56: Fix for races when soft-resetting on SPI Mark Brown

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=a027bb81-01a9-4658-a089-8035ae5f0815@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=tiwai@suse.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