[PATCH 1/3] spi: ma35d1-qspi: Drop a pure software limitation

From: Miquel Raynal

Date: Wed Nov 18 2026 - 08:55:18 EST


The controller has no documented limit when it comes to the amount of
data it can read in a single operation. The current limit is purely
software and prevents continuous reads. Some of the limits may be kept
for use with the normal SPI API, but do not make any sense in the
context of an optimized implementation for use with SPI memories.

To make sure there was no problem with my approach, I wrote a test tool
(link below) and ran a hundred tests over dozens of blocks.

Link: https://lore.kernel.org/linux-mtd/20261030144108.2211604-1-miquel.raynal@xxxxxxxxxxx/T/#u
Signed-off-by: Miquel Raynal <miquel.raynal@xxxxxxxxxxx>
---
drivers/spi/spi-ma35d1-qspi.c | 13 -------------
1 file changed, 13 deletions(-)

diff --git a/drivers/spi/spi-ma35d1-qspi.c b/drivers/spi/spi-ma35d1-qspi.c
index 0644bb2990b8..1ec631afa403 100644
--- a/drivers/spi/spi-ma35d1-qspi.c
+++ b/drivers/spi/spi-ma35d1-qspi.c
@@ -295,9 +295,6 @@ static int nuvoton_qspi_txrx(struct nuvoton_qspi *qspi, const void *txbuf,
if (!len)
return 0;

- if (len > NUVOTON_QSPI_MAX_TRANSFER_SIZE)
- return -EMSGSIZE;
-
ret = nuvoton_qspi_reset_fifo(qspi);
if (ret) {
dev_err(qspi->dev, "FIFO reset timed out\n");
@@ -386,15 +383,6 @@ static size_t nuvoton_qspi_max_message_size(struct spi_device *spi)
return NUVOTON_QSPI_MAX_MESSAGE_SIZE;
}

-static int nuvoton_qspi_mem_adjust_op_size(struct spi_mem *mem,
- struct spi_mem_op *op)
-{
- if (op->data.nbytes > NUVOTON_QSPI_MAX_TRANSFER_SIZE)
- op->data.nbytes = NUVOTON_QSPI_MAX_TRANSFER_SIZE;
-
- return 0;
-}
-
static bool nuvoton_qspi_mem_supports_op(struct spi_mem *mem,
const struct spi_mem_op *op)
{
@@ -560,7 +548,6 @@ static int nuvoton_qspi_mem_exec_op(struct spi_mem *mem,
}

static const struct spi_controller_mem_ops nuvoton_qspi_mem_ops = {
- .adjust_op_size = nuvoton_qspi_mem_adjust_op_size,
.supports_op = nuvoton_qspi_mem_supports_op,
.exec_op = nuvoton_qspi_mem_exec_op,
};

--
2.56.0