public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Todd Poynor <tpoynor@mvista.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Bug: Flash writing & suspending
Date: Wed, 05 Oct 2005 09:47:08 -0700	[thread overview]
Message-ID: <4344038C.3040506@mvista.com> (raw)
In-Reply-To: <200510051701.54776.hs4233@mail.mn-solutions.de>

Holger Schurig wrote:

> I suspect that maybe MTD is writing data into the StrataFlash. While this 
> erasing & writings happens, it probably polls the built-in state-machine 
> status of the chips. Probably during such an operation the suspend-to-memory 
> takes place. The hardware switches off the power to the StrataFlash, but MTD 
> doesn't know about this.
> 
> At resume time, the StataFlash get's power and resets to some initial state. 
> Linux thaws the processes, among them the JFFS2/MTD thread. Which continues 
> to poll the StrataFlash, but because it has been resetted in the meantime ...

Right, the mtd state machine goes out of sync with the actual chip state 
when the system sleep mode power cycles the chips.

I submitted a patch to rmk's ARM patch system that adds flash chips as 
platform devices to the Lubbock (PXA25x eval board) and Mainstone 
(PXA27x eval board) files.  If that's accepted, I'll send a common 
PXA2xx platform driver for mtd that adds the PM suspend/resume callbacks 
as discussed here recently.

In the meantime, get the struct mtd_info's ->resume routine called 
somehow at resume time.

-- 
Todd

  reply	other threads:[~2005-10-05 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05 12:37 Bug: Flash writing & suspending Holger Schurig
2005-10-05 15:01 ` Holger Schurig
2005-10-05 16:47   ` Todd Poynor [this message]
2005-10-07 12:36     ` Holger Schurig
2005-10-08 21:04       ` Todd Poynor

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=4344038C.3040506@mvista.com \
    --to=tpoynor@mvista.com \
    --cc=hs4233@mail.mn-solutions.de \
    --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