[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8de1c6c5-e86f-40cc-9650-efc2c581b221@linaro.org>
Date: Wed, 24 Jan 2024 09:32:25 +0000
From: Tudor Ambarus <tudor.ambarus@...aro.org>
To: André Draszik <andre.draszik@...aro.org>,
broonie@...nel.org, andi.shyti@...nel.org, arnd@...db.de
Cc: robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor+dt@...nel.org, alim.akhtar@...sung.com, linux-spi@...r.kernel.org,
linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-arch@...r.kernel.org, peter.griffin@...aro.org,
semen.protsenko@...aro.org, kernel-team@...roid.com, willmcvicker@...gle.com
Subject: Re: [PATCH 08/21] spi: s3c64xx: move error check up to avoid
rechecking
On 1/24/24 09:21, André Draszik wrote:
> Hi Tudor,
>
Hi!
> On Tue, 2024-01-23 at 15:34 +0000, Tudor Ambarus wrote:
>> @@ -538,13 +538,8 @@ static int s3c64xx_wait_for_dma(struct s3c64xx_spi_driver_data *sdd,
>> cpu_relax();
>> status = readl(regs + S3C64XX_SPI_STATUS);
>> }
>> -
>> }
>>
>> - /* If timed out while checking rx/tx status return error */
>> - if (!val)
>> - return -EIO;
>> -
>
> This change behaviour of this function. The loop just above adjusts val and it is used to
> determine if there was a timeout or not:
>
> if (val && !xfer->rx_buf) {
> val = msecs_to_loops(10);
> status = readl(regs + S3C64XX_SPI_STATUS);
> while ((TX_FIFO_LVL(status, sdd)
> || !S3C64XX_SPI_ST_TX_DONE(status, sdd))
> && --val) {
> cpu_relax();
> status = readl(regs + S3C64XX_SPI_STATUS);
> }
>
Oh, yes, the timeout in this block. You're right, I'll drop the patch.
Thanks!
ta
Powered by blists - more mailing lists