You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by ry...@apache.org on 2019/02/27 22:13:53 UTC
[mynewt-core] branch master updated: spiflash: Remove delay when
reading ready status
This is an automated email from the ASF dual-hosted git repository.
rymek pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mynewt-core.git
The following commit(s) were added to refs/heads/master by this push:
new 490e126 spiflash: Remove delay when reading ready status
new bfde282 Merge pull request #1666 from rymanluk/spiflash_fix2
490e126 is described below
commit 490e12617ecec14d5cb617cd3475520167e4c6fc
Author: Łukasz Rymanowski <lu...@codecoup.pl>
AuthorDate: Wed Feb 27 23:00:02 2019 +0100
spiflash: Remove delay when reading ready status
Assume that when spiflash_wait_ready() is called in general flash should
be ready, therfore while() in this function should not take long.
If any delay is needed for given operation it should be applied outside
this function e.g. erase
---
hw/drivers/flash/spiflash/src/spiflash.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/hw/drivers/flash/spiflash/src/spiflash.c b/hw/drivers/flash/spiflash/src/spiflash.c
index 5e05616..8214b2a 100644
--- a/hw/drivers/flash/spiflash/src/spiflash.c
+++ b/hw/drivers/flash/spiflash/src/spiflash.c
@@ -876,8 +876,6 @@ spiflash_wait_ready(struct spiflash_dev *dev, uint32_t timeout_ms)
spiflash_lock(dev);
while (!spiflash_device_ready(dev)) {
- /* If not ready let's give it 10ms */
- os_time_delay(os_time_ms_to_ticks32(10));
if (os_time_get() > exp_time) {
rc = -1;
goto err;