Devicetree
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
	"Nuno Sá" <nuno.sa@analog.com>, "Fei Xie" <fei.xie@horizon.auto>
Subject: [PATCH 0/3] spi: cadence-xspi: add DMA support
Date: Sat,  7 Nov 2026 15:20:41 +0800	[thread overview]
Message-ID: <20261107072044.17574-1-jszhang@kernel.org> (raw)

This series tries to improve the cadence-xspi cpu usage and potential
performance if the allocated dmaengine is powerful.

But no matter the dmaengine performance is powerful or not, the cpu
usage is reduced a lot.

For example, on a dual CA55 platform, test with looping the following
cmd:
dd if=/dev/mtd0 of=/dev/null bs=8192

Before the patch:
cpu usage is nearly 50%, which means one CA55 is full loaded with
the sdma io copy.

After the patch:
cpu usage is between 0 ~ 1%

patch1 documents the dt-binding
patch2 adds the memcpy dmaengine support 
patch3 uses writel_relaxed for cmd regs.

Jisheng Zhang (3):
  spi: dt-bindings: cdns,xspi: Add DMA properties
  spi: cadence-xspi: Support dmaengine for sdma io copy
  spi: cadence-xspi: Use writel_relaxed() for cmd regs

 .../devicetree/bindings/spi/cdns,xspi.yaml    |  13 ++
 drivers/spi/spi-cadence-xspi.c                | 149 +++++++++++++++++-
 2 files changed, 155 insertions(+), 7 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-11-07  7:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07  7:20 Jisheng Zhang [this message]
2026-11-07  7:20 ` [PATCH 1/3] spi: dt-bindings: cdns,xspi: Add DMA properties Jisheng Zhang
2026-11-07  8:01   ` sashiko-bot
2026-11-07  7:20 ` [PATCH 2/3] spi: cadence-xspi: Support dmaengine for sdma io copy Jisheng Zhang
2026-11-07  7:51   ` sashiko-bot
2026-11-07  7:20 ` [PATCH 3/3] spi: cadence-xspi: Use writel_relaxed() for cmd regs Jisheng Zhang

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=20261107072044.17574-1-jszhang@kernel.org \
    --to=jszhang@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fei.xie@horizon.auto \
    --cc=krzk+dt@kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    /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