From: "Alexey, Korolev" <alexey.korolev@intel.com>
To: Nicolas Pitre <nico@cam.org>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] cfi: Fixup of write errors on XIP
Date: Tue, 21 Mar 2006 17:26:47 +0300 [thread overview]
Message-ID: <44200D27.2060404@intel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0603101044290.3274@localhost.localdomain>
Hi,
>
> I'm back, sorry for the delay.
>
I'm sorry too. I just returned from vacations.
> But the thing is, if you look at get_chip(), you'll see that nothing can
> go and erase another flash sector when a write is suspended. In other
> words, completion of a write operation always has priority on any erase
> attempt. So the problem you're describing may not be due to any erase
> delay occurring in another thread.
>
Oh. Seems if XIP while write is happened get chip will not allow to erase?
> The only possibility I can see is that xip_udelay() is interrupted so
> often that the UDELAY(map, chip, cmd_adr, 1) call never gets a chance to
> make any progress, even in the course of a half second wall clock time.
>
> Do you have a high interrupt rate in your system?
>
Iterrupt rate is not high. It's about one per 10ms. I'm going to make
some more investigations.
I would be happy to hear your suggestions.
Thanks a lot,
Alexey
next prev parent reply other threads:[~2006-03-21 14:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 18:20 [PATCH] cfi: Fixup of write errors on XIP 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2006-03-02 10:18 Korolev, Alexey
2006-02-22 18:17 Korolev, Alexey
2006-03-01 17:48 ` Alexey, Korolev
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=44200D27.2060404@intel.com \
--to=alexey.korolev@intel.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nico@cam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.