public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Anders <dave123_aml@yahoo.com>
To: linux-mtd <linux-mtd@lists.infradead.org>
Cc: nico@cam.org
Subject: patch to leave cfi in read-array on suspend(reposted)
Date: Thu, 19 Oct 2006 07:05:29 -0700 (PDT)	[thread overview]
Message-ID: <20061019140534.10858.qmail@web54408.mail.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 674 bytes --]

greetings,

during some testing with several samsung s3c24xx based
devices it was discovered that often the
cfi_cmdset_0001.c would not leave the chip in
read-array mode on suspend. this is an issue if the
same flash chip is used for the bootloader that needs
to be read on resume. attached is a patch generated
against the 2.6.18 kernel and has been tested with
several s3c24xx based devices as well as several sharp
lh79520 devices. your feedback would be appreciated.

Signed-off-by: David Anders <danders@amltd.com>

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[-- Attachment #2: 3238585821-cfi_cmdset_0001.patch --]
[-- Type: application/octet-stream, Size: 524 bytes --]

--- linux-2.6.18/drivers/mtd/chips/cfi_cmdset_0001.c	2006-09-19 23:42:06.000000000 -0400
+++ linux-2.6.18-m5900/drivers/mtd/chips/cfi_cmdset_0001.c	2006-09-22 09:16:21.000000000 -0400
@@ -2224,6 +2224,8 @@
 		case FL_CFI_QUERY:
 		case FL_JEDEC_QUERY:
 			if (chip->oldstate == FL_READY) {
+				/* place the chip in a known state before suspend */
+				map_write(map, CMD(0xFF), cfi->chips[i].start);
 				chip->oldstate = chip->state;
 				chip->state = FL_PM_SUSPENDED;
 				/* No need to wake_up() on this state change -

             reply	other threads:[~2006-10-19 14:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 14:05 David Anders [this message]
2006-10-19 14:21 ` patch to leave cfi in read-array on suspend(reposted) Nicolas Pitre
2006-10-19 14:26   ` Artem Bityutskiy

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=20061019140534.10858.qmail@web54408.mail.yahoo.com \
    --to=dave123_aml@yahoo.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox