From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Stepan Ionichev <sozdayvek@gmail.com>
Cc: jic23@kernel.org, lars@metafoo.de, Michael.Hennerich@analog.com,
alisa.roman@analog.com, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] iio: adc: ad7192: replace usleep_range() with fsleep()
Date: Mon, 11 May 2026 10:29:19 +0300 [thread overview]
Message-ID: <agGFT0aHuqWGpUPq@ashevche-desk.local> (raw)
In-Reply-To: <20260510113921.50133-1-sozdayvek@gmail.com>
On Sun, May 10, 2026 at 04:39:21PM +0500, Stepan Ionichev wrote:
> The AD7192 datasheet (Rev. A, page 34, RESET section) says:
> "When a reset is initiated, the user must allow a period of
> 500 us before accessing any of the on-chip registers."
> fsleep(500) expands to the same usleep_range(500, 1000) and
> keeps the 500 us minimum.
>
> Drop the redundant "/* Wait for at least 500us */" comment.
> No functional change.
Same comment as per other patch.
> Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
> ---
> v3:
> - Cite AD7192 datasheet for the 500 us minimum (per Andy)
To have it in the code comment is much more important.
> - Add this changelog (was missing in v2)
...
> if (ret < 0)
> return ret;
+ blank line
+ comment as per datasheet
> - usleep_range(500, 1000); /* Wait for at least 500us */
> + fsleep(500);
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-05-11 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 11:39 [PATCH v3] iio: adc: ad7192: replace usleep_range() with fsleep() Stepan Ionichev
2026-05-11 2:55 ` [PATCH v4] " Stepan Ionichev
2026-05-11 13:28 ` Andy Shevchenko
2026-05-11 16:10 ` Jonathan Cameron
2026-05-11 7:29 ` Andy Shevchenko [this message]
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=agGFT0aHuqWGpUPq@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=alisa.roman@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=sozdayvek@gmail.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