linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Parshuram Thombare <pthombar@cadence.com>
To: <lukas@wunner.de>, <linux-spi@vger.kernel.org>
Cc: <miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>,
	<linux-kernel@vger.kernel.org>, <mparab@cadence.com>,
	<jpawar@cadence.com>, Parshuram Thombare <pthombar@cadence.com>
Subject: [PATCH v2 0/2] add support for Cadence's XSPI controller
Date: Wed, 21 Jul 2021 10:11:58 +0200	[thread overview]
Message-ID: <1626855118-25327-1-git-send-email-pthombar@cadence.com> (raw)

This patch series adds support for Cadence's XSPI controller.
This controller supports multiple work modes e.g.
STIG (Software Triggered Instruction Generator) mode, ACMD PIO
and CDMA modes, direct mode.
In STIG mode, controller sends low-level instructions to memory.
Each instruction is 128-bit width. There is special instruction
DataSequence which carries information about data phase.
Driver uses Slave DMA interface to transfer data as only this
interface can be used in STIG work mode.
The CDMA work mode is dedicated for high-performance application
where very low software overhead is required. In this mode the
Command Engine is programmed by the series of linked descriptors
stored in system memory. These descriptors provide commands to execute
and store status information for finished commands.
The PIO mode work mode is dedicated for single operation where
constructing a linked list of descriptors would require too
much effort.
Currently ACMD PIO mode is used for NOR flash read, program, erase
operations, all other operations are handled in STIG work mode.

Changes since v1:
1. Use ACMD PIO work mode for NOR read, program and erase operations,
   for everything else use STIG(Software Triggered Instruction
   Generator) work mode.
2. Changes suggested by Lukas.

Parshuram Thombare (2):
  spi: cadence: add dt-bindings documentation for Cadence XSPI
    controller
  spi: cadence: add support for Cadence XSPI controller

 .../devicetree/bindings/spi/cdns,xspi.yaml         |  169 +++
 drivers/spi/Kconfig                                |   11 +
 drivers/spi/Makefile                               |    1 +
 drivers/spi/spi-cadence-xspi.c                     | 1102 ++++++++++++++++++++
 4 files changed, 1283 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/spi/cdns,xspi.yaml
 create mode 100644 drivers/spi/spi-cadence-xspi.c

-- 
2.7.4


             reply	other threads:[~2021-07-21  8:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21  8:11 Parshuram Thombare [this message]
2021-07-21  8:13 ` [PATCH v2 1/2] spi: cadence: add dt-bindings documentation for Cadence XSPI controller Parshuram Thombare
2021-07-21  8:15 ` [PATCH v2 2/2] spi: cadence: add support " Parshuram Thombare
2021-07-21 11:00   ` Pratyush Yadav
2021-07-26 19:11     ` Parshuram Raju Thombare
2021-08-02 17:32 ` [PATCH v2 0/2] add support for Cadence's " Mark Brown
2021-08-03  5:01   ` Parshuram Raju Thombare

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=1626855118-25327-1-git-send-email-pthombar@cadence.com \
    --to=pthombar@cadence.com \
    --cc=jpawar@cadence.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=miquel.raynal@bootlin.com \
    --cc=mparab@cadence.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).