From: CL Wang <cl634@andestech.com>
To: <cl634@andestech.com>, <broonie@kernel.org>,
<linux-spi@vger.kernel.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tim609@andestech.com>
Subject: [PATCH V2 0/3] spi: atcspi200: Add support for Andes ATCSPI200 SPI controller
Date: Wed, 10 Dec 2025 17:04:27 +0800 [thread overview]
Message-ID: <20251210090430.3602380-1-cl634@andestech.com> (raw)
Hi all,
This series adds support for the Andes ATCSPI200 SPI controller.
Changes in v2 include:
- Added missing clock disable/unprepare handling in probe error paths.
- Switched to devm_dma_request_chan() for proper DMA channel cleanup.
- Updated the DT binding and documented all compatible strings.
- Dropped the "spi_" prefix from dma-names as suggested.
- Added suspend/resume support for power management.
- Added the "andestech,ae350-spi" compatible string.
AE350 is part of the AndeShape™ platform family and is a commercially
supported product with a fixed, documented SoC-level architecture (memory
map, interrupt topology, and peripheral integration). Although AE350 is
often deployed on FPGA boards, the platform behaves as a stable SoC
integration rather than a prototype.
Upstream Linux already accepts FPGA-based platform-level compatible strings
for stable SoC-like integrations. For example, the Tensilica FPGA platform
uses:
compatible = "cdns,xtfpga-spi";
Following the same rationale, "andestech,ae350-spi" is proposed as the
platform-level compatible string for AE350-based devices.
More information about AE350 can be found at:
https://www.andestech.com/en/products-solutions/andeshape-platforms/ae350-axi-based-platform-pre-integrated-with-n25f-nx25f-a25-ax25/
Patch overview:
- Patch 1: Adds the device tree binding documentation.
- Patch 2: Add ATCSPI200 SPI controller driver.
- Patch 3: Add MAINTAINERS entry for the ATCSPI200 SPI controller driver.
Comments and reviews are welcome.
Thanks for your time.
Best regards,
CL
CL Wang (3):
dt-bindings: spi: Add support for ATCSPI200 SPI controller
spi: atcspi200: Add ATCSPI200 SPI controller driver
MAINTAINERS: Add MAINTAINERS entry for the ATCSPI200 SPI controller
driver
.../bindings/spi/andestech,qilai-spi.yaml | 86 +++
MAINTAINERS | 6 +
drivers/spi/Kconfig | 9 +
drivers/spi/Makefile | 1 +
drivers/spi/spi-atcspi200.c | 680 ++++++++++++++++++
5 files changed, 782 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/andestech,qilai-spi.yaml
create mode 100644 drivers/spi/spi-atcspi200.c
--
2.34.1
next reply other threads:[~2025-12-10 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 9:04 CL Wang [this message]
2025-12-10 9:04 ` [PATCH V2 1/3] dt-bindings: spi: Add support for " CL Wang
2025-12-10 18:36 ` Conor Dooley
2025-12-12 9:33 ` CL Wang
2025-12-11 5:31 ` Krzysztof Kozlowski
2025-12-12 9:49 ` CL Wang
2025-12-10 9:04 ` [PATCH V2 2/3] spi: atcspi200: Add ATCSPI200 SPI controller driver CL Wang
2025-12-10 9:04 ` [PATCH V2 3/3] MAINTAINERS: Add MAINTAINERS entry for the " CL Wang
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=20251210090430.3602380-1-cl634@andestech.com \
--to=cl634@andestech.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tim609@andestech.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®