From: Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>
To: Mark Brown <broonie@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
<linux-riscv@lists.infradead.org>, <linux-spi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Valentina Fernandez Alanis
<valentina.fernandezalanis@microchip.com>,
"Cyril Jean" <cyril.jean@microchip.com>,
Prajna Rajendra Kumar <prajna.rajendrakumar@microchip.com>
Subject: [PATCH v3 0/3] Add support for Microchip CoreSPI Controller
Date: Fri, 7 Nov 2025 12:21:01 +0000 [thread overview]
Message-ID: <20251107122104.1389301-1-prajna.rajendrakumar@microchip.com> (raw)
This patch series adds support for the Microchip FPGA CoreSPI "soft" IP
and documents its device tree bindings.
As preparation, the existing Microchip SPI driver is renamed to clearly
indicate that it supports only the Microchip PolarFire SoC "hard" controller.
Although it was originally named with the expectation that it might also
cover the FPGA CoreSPI "soft" IP, the register layouts differ significantly,
so separate drivers are required.
changes in v3
--------------
- Renamed Kconfig symbol to SPI_MICROCHIP_CORE_SPI
- Renamed CoreSPI driver from spi-microchip-core.c to spi-microchip-core-spi.c to avoid confusion
changes in v2
--------------
- Moved compatible strings into an enum and kept alphabetical order
- Replaced .remove_new callback with .remove
- Dropped unused variable reported by kernel test robot
- Updated CoreSPI drivers commit message to include the 8-bit frame size restriction
Prajna Rajendra Kumar (3):
spi: microchip: rename driver file and internal identifiers
spi: dt-binding: document Microchip CoreSPI
spi: add support for microchip "soft" spi controller
.../bindings/spi/microchip,mpfs-spi.yaml | 70 ++-
drivers/spi/Kconfig | 28 +-
drivers/spi/Makefile | 3 +-
drivers/spi/spi-microchip-core-spi.c | 442 ++++++++++++++++++
.../spi/{spi-microchip-core.c => spi-mpfs.c} | 207 ++++----
5 files changed, 635 insertions(+), 115 deletions(-)
create mode 100644 drivers/spi/spi-microchip-core-spi.c
rename drivers/spi/{spi-microchip-core.c => spi-mpfs.c} (68%)
--
2.25.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2025-11-07 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 12:21 Prajna Rajendra Kumar [this message]
2025-11-07 12:21 ` [PATCH v3 1/3] spi: microchip: rename driver file and internal identifiers Prajna Rajendra Kumar
2025-11-07 12:21 ` [PATCH v3 2/3] spi: dt-binding: document Microchip CoreSPI Prajna Rajendra Kumar
2025-11-07 12:21 ` [PATCH v3 3/3] spi: add support for microchip "soft" spi controller Prajna Rajendra Kumar
2025-11-07 17:15 ` Conor Dooley
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=20251107122104.1389301-1-prajna.rajendrakumar@microchip.com \
--to=prajna.rajendrakumar@microchip.com \
--cc=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cyril.jean@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
--cc=valentina.fernandezalanis@microchip.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).