Message ID | 20240429112843.67628-1-wsa+renesas@sang-engineering.com |
---|---|
Headers | show |
Series | spi: use 'time_left' instead of 'timeout' with wait_for_*() functions | expand |
> > - if (!timeout) > > + time_left = wait_for_completion_timeout(&sspi->dma_rx_done, > > + time_left); > > Nit: indentation is off here. Regardless: Oh, right. Thanks, will fix!
Dne ponedeljek, 29. april 2024 ob 13:28:40 GMT +2 je Wolfram Sang napisal(a): > There is a confusing pattern in the kernel to use a variable named 'timeout' to > store the result of wait_for_completion_timeout() causing patterns like: > > timeout = wait_for_completion_timeout(...) > if (!timeout) return -ETIMEDOUT; > > with all kinds of permutations. Use 'time_left' as a variable to make the code > self explaining. > > Fix to the proper variable type 'unsigned long' while here. > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Acked-by: Jernej Skrabec <jernej.skrabec@gmail.com> Best regards, Jernej > --- > drivers/spi/spi-sun6i.c | 17 +++++++++-------- > 1 file changed, 9 insertions(+), 8 deletions(-) > > diff --git a/drivers/spi/spi-sun6i.c b/drivers/spi/spi-sun6i.c > index cd018ea1abf1..7bbe7ea0d66a 100644 > --- a/drivers/spi/spi-sun6i.c > +++ b/drivers/spi/spi-sun6i.c > @@ -277,7 +277,8 @@ static int sun6i_spi_transfer_one(struct spi_controller *host, > struct spi_transfer *tfr) > { > struct sun6i_spi *sspi = spi_controller_get_devdata(host); > - unsigned int div, div_cdr1, div_cdr2, timeout; > + unsigned int div, div_cdr1, div_cdr2; > + unsigned long time_left; > unsigned int start, end, tx_time; > unsigned int trig_level; > unsigned int tx_len = 0, rx_len = 0, nbits = 0; > @@ -488,26 +489,26 @@ static int sun6i_spi_transfer_one(struct spi_controller *host, > > tx_time = spi_controller_xfer_timeout(host, tfr); > start = jiffies; > - timeout = wait_for_completion_timeout(&sspi->done, > - msecs_to_jiffies(tx_time)); > + time_left = wait_for_completion_timeout(&sspi->done, > + msecs_to_jiffies(tx_time)); > > if (!use_dma) { > sun6i_spi_drain_fifo(sspi); > } else { > - if (timeout && rx_len) { > + if (time_left && rx_len) { > /* > * Even though RX on the peripheral side has finished > * RX DMA might still be in flight > */ > - timeout = wait_for_completion_timeout(&sspi->dma_rx_done, > - timeout); > - if (!timeout) > + time_left = wait_for_completion_timeout(&sspi->dma_rx_done, > + time_left); > + if (!time_left) > dev_warn(&host->dev, "RX DMA timeout\n"); > } > } > > end = jiffies; > - if (!timeout) { > + if (!time_left) { > dev_warn(&host->dev, > "%s: timeout transferring %u bytes@%iHz for %i(%i)ms", > dev_name(&spi->dev), tfr->len, tfr->speed_hz, >
On Mon, 29 Apr 2024 13:28:33 +0200, Wolfram Sang wrote: > There is a confusing pattern in the kernel to use a variable named 'timeout' to > store the result of wait_for_*() functions causing patterns like: > > timeout = wait_for_completion_timeout(...) > if (!timeout) return -ETIMEDOUT; > > with all kinds of permutations. Use 'time_left' as a variable to make the code > obvious and self explaining. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/8] spi: armada-3700: use 'time_left' variable with wait_for_completion_timeout() commit: 7dbbbb1206dd0b695b9a76d3b758c8a689f1aa52 [2/8] spi: fsl-lpspi: use 'time_left' variable with wait_for_completion_timeout() commit: eef51e99f7b9ecc903a3a9ad9e7ca84dc35c3f52 [3/8] spi: imx: use 'time_left' variable with wait_for_completion_timeout() commit: eaeac043ab842d2e84616ff0412eec0121c1758c [4/8] spi: pic32-sqi: use 'time_left' variable with wait_for_completion_timeout() commit: a7c79e50a26cb619400ccc6294dbd7d8c24a0341 [5/8] spi: pic32: use 'time_left' variable with wait_for_completion_timeout() commit: e66480aed4a194f278da1e46ec45221b3983216f [6/8] spi: sun4i: use 'time_left' variable with wait_for_completion_timeout() commit: 34bed8a33f3a4f69b0ef584ef49f04a671a4a5c2 [7/8] spi: sun6i: use 'time_left' variable with wait_for_completion_timeout() commit: 83a3f1ba60d6e2f73c9dd2627a8ce41867dbc46b [8/8] spi: xlp: use 'time_left' variable with wait_for_completion_timeout() commit: 594aa75d6bdda85b5fd027a5056d8cd1345c1db3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark