* [PATCH v2 0/2] fpga: use 'time_left' instead of 'timeout' with wait_*() functions
@ 2024-06-20 11:50 Wolfram Sang
2024-06-20 11:50 ` [PATCH v2 2/2] fpga: zynq-fpga: use 'time_left' variable with wait_for_completion_timeout() Wolfram Sang
0 siblings, 1 reply; 3+ messages in thread
From: Wolfram Sang @ 2024-06-20 11:50 UTC (permalink / raw)
To: linux-kernel
Cc: Wolfram Sang, linux-arm-kernel, linux-fpga, Michal Simek,
Moritz Fischer, Wu Hao, Xu Yilun
There is a confusing pattern in the kernel to use a variable named 'timeout' to
store the result of wait_*() 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.
This is part of a tree-wide series. The rest of the patches can be found here:
git://git.kernel.org/pub/scm/linux/kernel/git/wsa/linux.git i2c/time_left
Because these patches are generated, I audit them before sending. This is why I
will send series step by step. Build bot is happy with these patches, though.
No functional changes intended.
Changes since v1 are stated per patch. Summary: I addressed review
comments and added acks.
Wolfram Sang (2):
fpga: socfpga: use 'time_left' variable with wait_for_completion*()
fpga: zynq-fpga: use 'time_left' variable with
wait_for_completion_timeout()
drivers/fpga/socfpga.c | 7 ++++---
drivers/fpga/zynq-fpga.c | 8 ++++----
2 files changed, 8 insertions(+), 7 deletions(-)
--
2.43.0
^ permalink raw reply [flat|nested] 3+ messages in thread* [PATCH v2 2/2] fpga: zynq-fpga: use 'time_left' variable with wait_for_completion_timeout() 2024-06-20 11:50 [PATCH v2 0/2] fpga: use 'time_left' instead of 'timeout' with wait_*() functions Wolfram Sang @ 2024-06-20 11:50 ` Wolfram Sang 2024-06-22 14:54 ` Xu Yilun 0 siblings, 1 reply; 3+ messages in thread From: Wolfram Sang @ 2024-06-20 11:50 UTC (permalink / raw) To: linux-kernel Cc: Wolfram Sang, Michal Simek, Moritz Fischer, Wu Hao, Xu Yilun, Tom Rix, linux-fpga, linux-arm-kernel 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. Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Acked-by: Michal Simek <michal.simek@amd.com> --- Change since v1: added ack (Thanks Michal) drivers/fpga/zynq-fpga.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/fpga/zynq-fpga.c b/drivers/fpga/zynq-fpga.c index 0ac93183d201..4db3d80e10b0 100644 --- a/drivers/fpga/zynq-fpga.c +++ b/drivers/fpga/zynq-fpga.c @@ -387,7 +387,7 @@ static int zynq_fpga_ops_write(struct fpga_manager *mgr, struct sg_table *sgt) const char *why; int err; u32 intr_status; - unsigned long timeout; + unsigned long time_left; unsigned long flags; struct scatterlist *sg; int i; @@ -427,8 +427,8 @@ static int zynq_fpga_ops_write(struct fpga_manager *mgr, struct sg_table *sgt) zynq_step_dma(priv); spin_unlock_irqrestore(&priv->dma_lock, flags); - timeout = wait_for_completion_timeout(&priv->dma_done, - msecs_to_jiffies(DMA_TIMEOUT_MS)); + time_left = wait_for_completion_timeout(&priv->dma_done, + msecs_to_jiffies(DMA_TIMEOUT_MS)); spin_lock_irqsave(&priv->dma_lock, flags); zynq_fpga_set_irq(priv, 0); @@ -452,7 +452,7 @@ static int zynq_fpga_ops_write(struct fpga_manager *mgr, struct sg_table *sgt) if (priv->cur_sg || !((intr_status & IXR_D_P_DONE_MASK) == IXR_D_P_DONE_MASK)) { - if (timeout == 0) + if (time_left == 0) why = "DMA timed out"; else why = "DMA did not complete"; -- 2.43.0 ^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v2 2/2] fpga: zynq-fpga: use 'time_left' variable with wait_for_completion_timeout() 2024-06-20 11:50 ` [PATCH v2 2/2] fpga: zynq-fpga: use 'time_left' variable with wait_for_completion_timeout() Wolfram Sang @ 2024-06-22 14:54 ` Xu Yilun 0 siblings, 0 replies; 3+ messages in thread From: Xu Yilun @ 2024-06-22 14:54 UTC (permalink / raw) To: Wolfram Sang Cc: linux-kernel, Michal Simek, Moritz Fischer, Wu Hao, Xu Yilun, Tom Rix, linux-fpga, linux-arm-kernel On Thu, Jun 20, 2024 at 01:50:22PM +0200, Wolfram Sang wrote: Please check the same shortlog problem for all your patches Thanks, Yilun > 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. > > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com> > Acked-by: Michal Simek <michal.simek@amd.com> > --- > > Change since v1: added ack (Thanks Michal) > > drivers/fpga/zynq-fpga.c | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/drivers/fpga/zynq-fpga.c b/drivers/fpga/zynq-fpga.c > index 0ac93183d201..4db3d80e10b0 100644 > --- a/drivers/fpga/zynq-fpga.c > +++ b/drivers/fpga/zynq-fpga.c > @@ -387,7 +387,7 @@ static int zynq_fpga_ops_write(struct fpga_manager *mgr, struct sg_table *sgt) > const char *why; > int err; > u32 intr_status; > - unsigned long timeout; > + unsigned long time_left; > unsigned long flags; > struct scatterlist *sg; > int i; > @@ -427,8 +427,8 @@ static int zynq_fpga_ops_write(struct fpga_manager *mgr, struct sg_table *sgt) > zynq_step_dma(priv); > spin_unlock_irqrestore(&priv->dma_lock, flags); > > - timeout = wait_for_completion_timeout(&priv->dma_done, > - msecs_to_jiffies(DMA_TIMEOUT_MS)); > + time_left = wait_for_completion_timeout(&priv->dma_done, > + msecs_to_jiffies(DMA_TIMEOUT_MS)); > > spin_lock_irqsave(&priv->dma_lock, flags); > zynq_fpga_set_irq(priv, 0); > @@ -452,7 +452,7 @@ static int zynq_fpga_ops_write(struct fpga_manager *mgr, struct sg_table *sgt) > > if (priv->cur_sg || > !((intr_status & IXR_D_P_DONE_MASK) == IXR_D_P_DONE_MASK)) { > - if (timeout == 0) > + if (time_left == 0) > why = "DMA timed out"; > else > why = "DMA did not complete"; > -- > 2.43.0 > > ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-06-22 15:01 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2024-06-20 11:50 [PATCH v2 0/2] fpga: use 'time_left' instead of 'timeout' with wait_*() functions Wolfram Sang 2024-06-20 11:50 ` [PATCH v2 2/2] fpga: zynq-fpga: use 'time_left' variable with wait_for_completion_timeout() Wolfram Sang 2024-06-22 14:54 ` Xu Yilun
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).