[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210308145502.1075689-3-aardelean@deviqon.com>
Date: Mon, 8 Mar 2021 16:54:54 +0200
From: Alexandru Ardelean <aardelean@...iqon.com>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
greybus-dev@...ts.linaro.org, devel@...verdev.osuosl.org,
linux-tegra@...r.kernel.org, bcm-kernel-feedback-list@...adcom.com
Cc: broonie@...nel.org, gregkh@...uxfoundation.org, elder@...nel.org,
johan@...nel.org, vireshk@...nel.org, rmfrfs@...il.com,
f.fainelli@...il.com, ldewangan@...dia.com,
thierry.reding@...il.com, jonathanh@...dia.com, linux@...iqon.com,
Alexandru Ardelean <aardelean@...iqon.com>
Subject: [PATCH 02/10] spi: bcm63xx-spi: don't check 'delay_usecs' field
The 'delay_usecs' field was handled for backwards compatibility in case
there were some users that still configured SPI delay transfers with
this field.
They should all be removed by now.
Signed-off-by: Alexandru Ardelean <aardelean@...iqon.com>
---
drivers/spi/spi-bcm63xx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-bcm63xx.c b/drivers/spi/spi-bcm63xx.c
index d08bb7600150..80fa0ef8909c 100644
--- a/drivers/spi/spi-bcm63xx.c
+++ b/drivers/spi/spi-bcm63xx.c
@@ -369,7 +369,7 @@ static int bcm63xx_spi_transfer_one(struct spi_master *master,
}
/* CS will be deasserted directly after transfer */
- if (t->delay_usecs || t->delay.value) {
+ if (t->delay.value) {
dev_err(&spi->dev, "unable to keep CS asserted after transfer\n");
status = -EINVAL;
goto exit;
--
2.29.2
Powered by blists - more mailing lists