From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Re: [PATCH] staging: fbtft: fb_ra8875: replace udelays with usleep_range
Date: Fri, 27 Feb 2026 12:43:24 +1000 [thread overview]
Message-ID: <review-overall-2026022515-booth-silent-f3bd@gregkh> (raw)
In-Reply-To: <2026022515-booth-silent-f3bd@gregkh>
Overall Series Review
Subject: Re: [PATCH] staging: fbtft: fb_ra8875: replace udelays with usleep_range
Author: Greg KH <gregkh@linuxfoundation.org>
Patches: 5
Reviewed: 2026-02-27T12:43:24.355510
---
This mbox contains a v1 patch and its v2 respin, both by Jose A. Perez de Azpillaga, targeting `drivers/staging/fbtft/fb_ra8875.c`. The goal is to replace two `udelay(100)` calls in `write_reg8_bus8()` with a sleeping alternative to avoid busy-waiting in a non-atomic context.
**v1** used `usleep_range(100, 120)`. **v2** (the current revision) switches to `fsleep(100)`, which is the preferred modern API per reviewer feedback.
The change is **correct and appropriate**. The `write_reg8_bus8()` function is clearly in a sleepable context — it calls `write_spi()` → `spi_sync()`, which itself can sleep. The existing `init_display()` function in the same file already uses `mdelay()` for longer waits, further confirming non-atomic context.
For 100us, `fsleep(100)` will internally call `usleep_range(100, 125)` (based on the formula `usleep_range(usecs, usecs + (usecs >> max_slack_shift))` with `max_slack_shift=2`), which is a reasonable range and avoids the busy-wait of `udelay()`.
No functional concerns. This is a straightforward cleanup appropriate for staging.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-27 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 20:45 [PATCH] staging: fbtft: fb_ra8875: replace udelays with usleep_range Jose A. Perez de Azpillaga
2026-02-25 21:14 ` Greg KH
2026-02-27 2:43 ` Claude Code Review Bot [this message]
2026-02-27 2:54 ` Claude review: " Claude Code Review Bot
2026-02-25 23:40 ` [PATCH v2] staging: fbtft: fb_ra8875: replace udelays with fsleep Jose A. Perez de Azpillaga
2026-02-26 7:46 ` Andy Shevchenko
2026-02-26 8:31 ` Jose A. Perez de Azpillaga
2026-02-27 2:54 ` Claude review: " Claude Code Review Bot
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=review-overall-2026022515-booth-silent-f3bd@gregkh \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.com \
/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