From: "Alexey, Korolev" <alexey.korolev@intel.com>
To: "Korolev, Alexey" <alexey.korolev@intel.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] cfi: Fixup of write errors on XIP
Date: Wed, 01 Mar 2006 20:48:20 +0300 [thread overview]
Message-ID: <4405DE64.4060807@intel.com> (raw)
In-Reply-To: <F92C2EFE7C3BA745855BF7036E1F3F9A01A06023@NNSMSX401>
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
Hi all.
Several days ago I sent this patch to the list. I wonder has anybody
complains about it?
I my opinion the patch shouldn't break anything. It just fixes up write
errors I saw in our tests.
If you don't mind I will commit it.
Thanks,
Alexey
>
> Here is fixup of issue I have seen on XIP configuration.
> Sometimes I received write errors with message "buffer write error
> (status timeout)" on test which did read write and erase on several
> volumes at the same time.
>
> I investigated the issue.
> The scenario of the issue is following:
>
> 1. do_write_buffer
> 2. Waiting for write complete in xip_udelay
> 3. System Interrupt
> 4. Write suspend
> 5. Rescheduling
> 6. Block erasing by other process. ( This operation typically took
> rather long time )
> 7. Complete, rescheduling
> 8. Return to write (write is not complete due to suspend ).
> 9. Check timeout. Time is up.
> 10. Error.
>
> I made small fixup for these issue. Please see patch below.
>
[-- Attachment #2: XIP_wr_errors_fixup.diff --]
[-- Type: text/plain, Size: 665 bytes --]
--- c/drivers/mtd/chips/cfi_cmdset_0001.c 2006-02-22 20:58:05.869203280 +0300
+++ b/drivers/mtd/chips/cfi_cmdset_0001.c 2006-02-22 20:55:42.272033368 +0300
@@ -1571,6 +1571,7 @@
/* GO GO GO */
map_write(map, CMD(0xd0), cmd_adr);
chip->state = FL_WRITING;
+ chip->write_suspended = 0;
INVALIDATE_CACHE_UDELAY(map, chip, cmd_adr,
adr, len,
@@ -1592,6 +1593,12 @@
continue;
}
+ /* Somebody suspended write. We should reset timeo. */
+ if (chip->write_suspended) {
+ chip->write_suspended = 0;
+ timeo = jiffies + (HZ/2);
+ }
+
status = map_read(map, cmd_adr);
if (map_word_andequal(map, status, status_OK, status_OK))
break;
next prev parent reply other threads:[~2006-03-01 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 18:17 [PATCH] cfi: Fixup of write errors on XIP Korolev, Alexey
2006-03-01 17:48 ` Alexey, Korolev [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 18:20 Korolev, Alexey
2006-03-02 15:36 ` Nicolas Pitre
2006-03-02 16:35 ` Alexey, Korolev
2006-03-10 16:36 ` Nicolas Pitre
2006-03-21 14:26 ` Alexey, Korolev
2006-03-21 15:10 ` Nicolas Pitre
2006-03-28 14:09 ` Alexey, Korolev
2006-03-29 16:34 ` Nicolas Pitre
2006-03-29 16:44 ` Nicolas Pitre
2006-03-30 2:54 ` Nicolas Pitre
2006-03-30 13:27 ` Alexey, Korolev
2006-03-30 14:38 ` Nicolas Pitre
2006-03-02 10:18 Korolev, Alexey
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=4405DE64.4060807@intel.com \
--to=alexey.korolev@intel.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