From: Alex Elder <elder@riscstar.com>
To: pavankumaryalagada@gmail.com, greybus-dev@lists.linaro.org,
outreachy@lists.linux.dev
Cc: pure.logic@nexus-software.ie, johan@kernel.org, elder@kernel.org,
gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: greybus: loopback: Use fsleep() for delay
Date: Fri, 23 Oct 2026 07:48:54 -0500 [thread overview]
Message-ID: <a411ee0e-22c4-4797-9fdc-3ac11fa20d60@riscstar.com> (raw)
In-Reply-To: <20261022202455.104142-1-pavankumaryalagada@gmail.com>
On 10/22/26 3:24 PM, pavankumaryalagada@gmail.com wrote:
> From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
>
> In the loopback function, usleep_range() is used for short delays
> and msleep() for longer delays. This requires choosing the delay
> function based on the requested time and converting microseconds
> to milliseconds when using msleep().
>
> Replace both functions with fsleep(), which chooses a delay
> delay method based on the requested time. For short delays,
s/delay delay/delay/
I think "checkpatch.pl" would have caught this.
Maybe Greg can fix this up.
> fsleep() allows up to 25% extra time instead of the fixed 100
> microseconds. For longer delays, the old code rounds the
> requested time down to whole milliseconds, while fsleep() rounds
> it up when using msleep().
>
> These changes may affect time between loopback operations and
> the reported performance.
>
> Suggested-by: Alex Elder <elder@riscstar.com>
> Signed-off-by: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
Looks good to me. Nice job.
Reviewed-by: Alex Elder <elder@riscstar.com>
> ---
> v2:
> - Add more details about how fsleep() affects delays.
> - Update the subject to include the loopback module.
>
> v1: https://lore.kernel.org/outreachy/c482704b-903e-413d-ba7b-5bf31c0a6104@riscstar.com/T/#t
> ---
> drivers/staging/greybus/loopback.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/staging/greybus/loopback.c b/drivers/staging/greybus/loopback.c
> index efc69c10cffe..2fe845eaef29 100644
> --- a/drivers/staging/greybus/loopback.c
> +++ b/drivers/staging/greybus/loopback.c
> @@ -898,12 +898,8 @@ static int gb_loopback_fn(void *data)
> gb->send_count++;
> mutex_unlock(&gb->mutex);
>
> - if (us_wait) {
> - if (us_wait < 20000)
> - usleep_range(us_wait, us_wait + 100);
> - else
> - msleep(us_wait / 1000);
> - }
> + if (us_wait)
> + fsleep(us_wait);
> }
>
> gb_pm_runtime_put_autosuspend(bundle);
next prev parent reply other threads:[~2026-10-23 12:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 20:24 pavankumaryalagada
2026-10-23 12:48 ` Alex Elder [this message]
2026-10-23 13:04 ` Greg KH
2026-10-23 13:18 ` Alex Elder
2026-10-23 14:14 ` Yalagada Pavan Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a411ee0e-22c4-4797-9fdc-3ac11fa20d60@riscstar.com \
--to=elder@riscstar.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=outreachy@lists.linux.dev \
--cc=pavankumaryalagada@gmail.com \
--cc=pure.logic@nexus-software.ie \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®