[PATCH v2 1/2] spi: microchip-core-qspi: report device on which timeout occured instead of which controller
Conor Dooley
conor at kernel.org
Tue Apr 28 11:11:11 PDT 2026
From: Conor Dooley <conor.dooley at microchip.com>
When prepare_message callbacks fail, the SPI core already reports which
controller the failure happened on. The corresponding code in the mem_ops
portion of the driver already reports the device a timeout occurred on,
so make the regular part of the driver do the same.
Signed-off-by: Conor Dooley <conor.dooley at microchip.com>
---
drivers/spi/spi-microchip-core-qspi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-microchip-core-qspi.c b/drivers/spi/spi-microchip-core-qspi.c
index eab059fb0bc2c..c8b053c7c857b 100644
--- a/drivers/spi/spi-microchip-core-qspi.c
+++ b/drivers/spi/spi-microchip-core-qspi.c
@@ -604,7 +604,7 @@ static int mchp_coreqspi_prepare_message(struct spi_controller *ctlr, struct spi
ret = mchp_coreqspi_wait_for_ready(qspi);
if (ret) {
mutex_unlock(&qspi->op_lock);
- dev_err(&ctlr->dev, "Timeout waiting on QSPI ready.\n");
+ dev_err(&m->spi->dev, "Timeout waiting on QSPI ready.\n");
return ret;
}
--
2.53.0
More information about the linux-riscv
mailing list