From: "Joël Esponde" <joel.esponde@honeywell.com>
To: <linux-mtd@lists.infradead.org>
Cc: "Joël Esponde" <joel.esponde@honeywell.com>
Subject: [PATCH] mtd: spi-nor: fixed spansion quad enable
Date: Thu, 20 Oct 2016 15:43:46 +0200 [thread overview]
Message-ID: <1476971026-9665-1-git-send-email-joel.esponde@honeywell.com> (raw)
With the S25FL127S nor flash part, each writing to the configuration register takes hundreds of ms. During that time, no more accesses to the flash should be done (even reads).
This commit adds:
- a pre check of the quad enable bit to avoid a useless and time consuming writing to the flash,
- a wait loop after the register writing until the flash finishes its work.
This issue could make rootfs mounting fail when the latter was done too much closely to this quad enable bit setting step. And in this case, a driver as UBIFS may try to recover the filesystem and may broke it completely.
---
drivers/mtd/spi-nor/spi-nor.c | 31 +++++++++++++++++++++++++++----
1 file changed, 27 insertions(+), 4 deletions(-)
diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
index d0fc165..df43cd7 100644
--- a/drivers/mtd/spi-nor/spi-nor.c
+++ b/drivers/mtd/spi-nor/spi-nor.c
@@ -1246,18 +1246,41 @@ static int spansion_quad_enable(struct spi_nor *nor)
int ret;
int quad_en = CR_QUAD_EN_SPAN << 8;
+ /* check quad enable bit
+ * as S25FL127S takes 200 ms to execute each write of SR & CR
+ * registers even if data is the same, write step will be shorted
+ * if not needed
+ */
+ ret = read_cr(nor);
+ if (ret < 0) {
+ dev_err(nor->dev, "error %d reading CR\n", ret);
+ return ret;
+ }
+ if (ret & CR_QUAD_EN_SPAN) {
+ /* quad enable bit is already set */
+ return 0;
+ }
+
+ /* set SR & CR, enable quad I/O */
write_enable(nor);
ret = write_sr_cr(nor, quad_en);
if (ret < 0) {
- dev_err(nor->dev,
- "error while writing configuration register\n");
+ dev_err(nor->dev, "error while writing SR and CR registers\n");
return -EINVAL;
}
- /* read back and check it */
+ ret = spi_nor_wait_till_ready(nor);
+ if (ret)
+ return ret;
+
+ /* read CR and check it */
ret = read_cr(nor);
- if (!(ret > 0 && (ret & CR_QUAD_EN_SPAN))) {
+ if (ret < 0) {
+ dev_err(nor->dev, "error %d reading CR\n", ret);
+ return ret;
+ }
+ if (!(ret & CR_QUAD_EN_SPAN)) {
dev_err(nor->dev, "Spansion Quad bit not set\n");
return -EINVAL;
}
--
2.7.4
next reply other threads:[~2016-10-20 13:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 13:43 Joël Esponde [this message]
2016-10-20 15:23 ` [PATCH] mtd: spi-nor: fixed spansion quad enable Cyrille Pitchen
2016-10-21 10:37 ` Esponde, Joel
2016-10-21 12:50 ` Cyrille Pitchen
2016-10-21 13:44 ` Cyrille Pitchen
2016-10-24 8:29 ` Esponde, Joel
2016-10-24 8:33 ` Esponde, Joel
2016-11-16 12:58 ` Cyrille Pitchen
2016-11-22 14:02 ` Esponde, Joel
2016-11-22 22:24 ` [PATCH v2] " Joël Esponde
2016-11-23 10:39 ` Cyrille Pitchen
2016-11-23 14:27 ` Esponde, Joel
2016-11-23 15:35 ` Marek Vasut
2016-11-23 18:21 ` Esponde, Joel
2016-11-23 11:47 ` [PATCH v3] mtd: spi-nor: fix " Joël Esponde
2016-11-23 14:35 ` Cyrille Pitchen
2016-11-25 14:17 ` Marek Vasut
2016-11-25 14:50 ` Cyrille Pitchen
2016-11-25 15:08 ` Marek Vasut
2016-11-25 16:01 ` Esponde, Joel
2016-11-25 16:43 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2016-10-19 22:11 [PATCH] mtd: spi-nor: fixed " Joël Esponde
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=1476971026-9665-1-git-send-email-joel.esponde@honeywell.com \
--to=joel.esponde@honeywell.com \
--cc=linux-mtd@lists.infradead.org \
/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).