public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Devin Butterfield <dbutter@wireless.net>
Cc: ipaq@handhelds.org, linux-mtd@lists.infradead.org
Subject: Re: [iPAQ] Sleep/resume problems, etc.
Date: Tue, 08 May 2001 08:20:52 +0100	[thread overview]
Message-ID: <3428.989306452@redhat.com> (raw)
In-Reply-To: <01050718392500.02834@dbm.wireless.net>

dbutter@wireless.net said:
>  The other more serious problem (which seems to only be related to
> resuming  from deep sleep) is that the entire OS seems to become
> unresponsive  (processes will not run) after a resume and I'll see
> these messages on the  console:

> waiting for chip to be ready timed out in read. WSM status = e0021985
> Error reading node from 0x0030fa84: -5

The power cycle has reset the flash chip into read mode. The driver still 
thinks it's in status mode.

The chip driver's resume function needs to make sure the chip is in a known 
state, rather than assuming it'll still be in the same state it was before 
the sleep.

I'm sure I'd done this before. 

diff -u -r1.72 cfi_cmdset_0001.c
--- cfi_cmdset_0001.c	2001/03/26 13:51:15	1.72
+++ cfi_cmdset_0001.c	2001/05/08 07:19:12
@@ -1582,7 +1582,9 @@
 		spin_lock_bh(chip->mutex);
 		
 		if (chip->state == FL_PM_SUSPENDED) {
-			chip->state = chip->oldstate;
+			/* We need to force it back to a known state. */
+			cfi_write(map, CMD(0xff), cmd_addr);
+			chip->state = FL_READY;
 			wake_up(&chip->wq);
 		}
 


--
dwmw2

       reply	other threads:[~2001-05-09  7:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01050718392500.02834@dbm.wireless.net>
2001-05-08  7:20 ` David Woodhouse [this message]
2001-05-09  7:50   ` [iPAQ] Sleep/resume problems, etc Devin Butterfield

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=3428.989306452@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=dbutter@wireless.net \
    --cc=ipaq@handhelds.org \
    --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