From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Wolfram Sang <wsa@the-dreams.de>,
linux-i2c <linux-i2c@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH 05/13] eeprom: at24: replace msleep() with usleep_range()
Date: Thu, 24 Mar 2016 15:45:59 +0100 [thread overview]
Message-ID: <1458830767-23816-6-git-send-email-bgolaszewski@baylibre.com> (raw)
In-Reply-To: <1458830767-23816-1-git-send-email-bgolaszewski@baylibre.com>
We cannot expect msleep(1) to actually sleep for a period shorter than
20 ms. Replace all calls to msleep() with usleep_range().
Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
---
drivers/misc/eeprom/at24.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
index 9e01428..bc5be1e 100644
--- a/drivers/misc/eeprom/at24.c
+++ b/drivers/misc/eeprom/at24.c
@@ -240,8 +240,7 @@ static ssize_t at24_eeprom_read(struct at24_data *at24, char *buf,
if (status == count)
return count;
- /* REVISIT: at HZ=100, this is sloooow */
- msleep(1);
+ usleep_range(1000, 1500);
} while (time_before(read_time, timeout));
return -ETIMEDOUT;
@@ -355,8 +354,7 @@ static ssize_t at24_eeprom_write(struct at24_data *at24, const char *buf,
if (status == count)
return count;
- /* REVISIT: at HZ=100, this is sloooow */
- msleep(1);
+ usleep_range(1000, 1500);
} while (time_before(write_time, timeout));
return -ETIMEDOUT;
--
2.7.4
next prev parent reply other threads:[~2016-03-24 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 14:45 [PATCH 00/13] eeprom: support for at24cs and at24mac Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 01/13] eeprom: at24: remove a reduntant if Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 02/13] eeprom: at24: improve the device_id table readability Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 03/13] eeprom: at24: platform_data: use BIT() macro Bartosz Golaszewski
2016-03-24 14:45 ` [PATCH 04/13] eeprom: at24: make locking more fine-grained Bartosz Golaszewski
2016-03-24 14:45 ` Bartosz Golaszewski [this message]
2016-03-24 14:46 ` [PATCH 06/13] eeprom: at24: add serial number flag Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 07/13] eeprom: at24: support reading of the serial number Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 08/13] eeprom: at24: call read and write routines via function pointers Bartosz Golaszewski
2016-03-24 15:12 ` kbuild test robot
2016-03-24 15:13 ` kbuild test robot
2016-03-24 14:46 ` [PATCH 09/13] eeprom: at24: use at24cs_serial_read() Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 10/13] eeprom: at24: add the at24cs series to the list of supported devices Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 11/13] eeprom: at24: add at24mac series flag Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 12/13] eeprom: at24: add support for at24mac series Bartosz Golaszewski
2016-03-24 14:46 ` [PATCH 13/13] eeprom: at24: add at24mac chips to the list of supported devices Bartosz Golaszewski
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=1458830767-23816-6-git-send-email-bgolaszewski@baylibre.com \
--to=bgolaszewski@baylibre.com \
--cc=andrew@lunn.ch \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).