spi: microchip-core-qspi: report device on which timeout occured instead of which...

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@microchip.com>
Link: https://patch.msgid.link/20260428-porcupine-ninetieth-af00cb11b990@spud
Signed-off-by: Mark Brown <broonie@kernel.org>

diff --git a/drivers/spi/spi-microchip-core-qspi.c b/drivers/spi/spi-microchip-core-qspi.c
index eab059fb0bc2ce0bb8361d5b814c1cdc8650e4eb..c8b053c7c857b9c1bf1571fcfb57de3f179bf43f 100644 (file)
--- 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;
        }