From: Dante <dantesu@faraday-tech.com>
To: qemu-devel@nongnu.org
Cc: peter.crosthwaite@petalogix.com, Dante <dantesu@faraday-tech.com>
Subject: [Qemu-devel] [PATCH] hw/m25p80.c: add WRSR(0x01) support
Date: Fri, 18 Jan 2013 14:17:11 +0800 [thread overview]
Message-ID: <1358489831-18005-1-git-send-email-dantesu@faraday-tech.com> (raw)
Atmel, SST and Intel/Numonyx serial flash tend to power up
with the software protection bits set.
And thus the new m25p80.c in linux kernel would always tries
to use WREN(0x06) + WRSR(0x01) to turn-off the protection.
The WEL(0x02) of status register is supposed to be cleared
after WRSR(0x01).
There are some drivers (i.e my own tiny driver for RTOSes) would
check the WEL(0x02) in status register to make sure the protection
is correctly turned off, so this patch is mandatory to me.
Signed-off-by: Kuo-Jung Su <dantesu@faraday-tech.com>
---
hw/m25p80.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/hw/m25p80.c b/hw/m25p80.c
index d392656..c8d0411 100644
--- a/hw/m25p80.c
+++ b/hw/m25p80.c
@@ -184,6 +184,7 @@ static const FlashPartInfo known_devices[] = {
typedef enum {
NOP = 0,
+ WRSR = 0x1,
WRDI = 0x4,
RDSR = 0x5,
WREN = 0x6,
@@ -377,6 +378,12 @@ static void complete_collecting_data(Flash *s)
case ERASE_SECTOR:
flash_erase(s, s->cur_addr, s->cmd_in_progress);
break;
+ case WRSR:
+ if (s->write_enable) {
+ s->state = STATE_IDLE;
+ s->write_enable = false;
+ }
+ break;
default:
break;
}
@@ -440,6 +447,15 @@ static void decode_new_cmd(Flash *s, uint32_t value)
s->len = 0;
s->state = STATE_COLLECTING_DATA;
break;
+
+ case WRSR:
+ if (s->write_enable) {
+ s->needed_bytes = 1;
+ s->pos = 0;
+ s->len = 0;
+ s->state = STATE_COLLECTING_DATA;
+ }
+ break;
case WRDI:
s->write_enable = false;
--
1.7.9.5
********************* Confidentiality Notice ************************
This electronic message and any attachments may contain
confidential and legally privileged information or
information which is otherwise protected from disclosure.
If you are not the intended recipient,please do not disclose
the contents, either in whole or in part, to anyone,and
immediately delete the message and any attachments from
your computer system and destroy all hard copies.
Thank you for your cooperation.
***********************************************************************
reply other threads:[~2013-01-18 6:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1358489831-18005-1-git-send-email-dantesu@faraday-tech.com \
--to=dantesu@faraday-tech.com \
--cc=peter.crosthwaite@petalogix.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).