From: Joe Komlodi <joe.komlodi@xilinx.com>
To: <qemu-devel@nongnu.org>
Cc: figlesia@xilinx.com, alistair@alistair23.me,
philippe.mathieu.daude@gmail.com, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: [PATCH v3 3/3] hw/block/m25p80: Fix Numonyx fast read dummy cycle count
Date: Thu, 5 Nov 2020 17:32:58 -0800 [thread overview]
Message-ID: <1604626378-152352-4-git-send-email-komlodi@xilinx.com> (raw)
In-Reply-To: <1604626378-152352-1-git-send-email-komlodi@xilinx.com>
Numonyx chips determine the number of cycles to wait based on bits 7:4
in the volatile configuration register.
However, if these bits are 0x0 or 0xF, the number of dummy cycles to wait is
10 on a QIOR or QIOR4 command, or 8 on any other currently supported
fast read command. [1]
[1]
https://www.micron.com/-/media/client/global/documents/products/data-sheet/nor-flash/serial-nor/mt25q/die-rev-b/mt25q_qlkt_u_02g_cbb_0.pdf?rev=9b167fbf2b3645efba6385949a72e453
Signed-off-by: Joe Komlodi <komlodi@xilinx.com>
---
hw/block/m25p80.c | 43 ++++++++++++++++++++++++++++++++++++++++---
1 file changed, 40 insertions(+), 3 deletions(-)
diff --git a/hw/block/m25p80.c b/hw/block/m25p80.c
index 8a1b684..a2cdfb6 100644
--- a/hw/block/m25p80.c
+++ b/hw/block/m25p80.c
@@ -841,6 +841,43 @@ static uint8_t numonyx_get_mode(Flash *s)
return mode;
}
+static uint8_t numonyx_extract_cfg_num_dummies(Flash *s)
+{
+ uint8_t cycle_count;
+ uint8_t num_dummies;
+ uint8_t mode;
+ uint8_t cycle_table[0x100][3] = {
+ [FAST_READ] = {8, 8, 10},
+ [FAST_READ4] = {8, 8, 10},
+ [DOR] = {8, 8, 0xff},
+ [DOR4] = {8, 8, 0xff},
+ [QOR] = {8, 0xff, 10},
+ [QOR4] = {8, 0xff, 10},
+ [DIOR] = {8, 8, 0xff},
+ [DIOR4] = {8, 8, 0xff},
+ [QIOR] = {10, 0xff, 10},
+ [QIOR4] = {10, 0xff, 10},
+ };
+ assert(get_man(s) == MAN_NUMONYX);
+
+ mode = numonyx_get_mode(s);
+
+ cycle_count = extract32(s->volatile_cfg, 4, 4);
+ if (cycle_count == 0x0 || cycle_count == 0xf) {
+ num_dummies = cycle_table[s->cmd_in_progress][mode];
+ } else {
+ num_dummies = cycle_count;
+ }
+
+ /*
+ * Validation if the command can be executed should be done outside of
+ * this function. e.g. trying to execute DIOR in QIO mode.
+ */
+ assert(num_dummies != 0xff);
+
+ return num_dummies;
+}
+
static bool numonyx_check_cmd_mode(Flash *s)
{
uint8_t mode;
@@ -901,7 +938,7 @@ static void decode_fast_read_cmd(Flash *s)
break;
case MAN_NUMONYX:
if (numonyx_check_cmd_mode(s)) {
- s->needed_bytes += extract32(s->volatile_cfg, 4, 4);
+ s->needed_bytes += numonyx_extract_cfg_num_dummies(s);
s->state = STATE_COLLECTING_DATA;
}
break;
@@ -947,7 +984,7 @@ static void decode_dio_read_cmd(Flash *s)
break;
case MAN_NUMONYX:
if (numonyx_check_cmd_mode(s)) {
- s->needed_bytes += extract32(s->volatile_cfg, 4, 4);
+ s->needed_bytes += numonyx_extract_cfg_num_dummies(s);
s->state = STATE_COLLECTING_DATA;
}
break;
@@ -993,7 +1030,7 @@ static void decode_qio_read_cmd(Flash *s)
break;
case MAN_NUMONYX:
if (numonyx_check_cmd_mode(s)) {
- s->needed_bytes += extract32(s->volatile_cfg, 4, 4);
+ s->needed_bytes += numonyx_extract_cfg_num_dummies(s);
s->state = STATE_COLLECTING_DATA;
}
break;
--
2.7.4
next prev parent reply other threads:[~2020-11-06 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 1:32 [PATCH v3 0/3] hw/block/m25p80: Numonyx: Fix dummy cycles and check for SPI mode on cmds Joe Komlodi
2020-11-06 1:32 ` [PATCH v3 1/3] hw/block/m25p80: Fix Numonyx NVCFG DIO and QIO bit polarity Joe Komlodi
2020-11-09 14:21 ` Philippe Mathieu-Daudé
2020-11-10 0:22 ` Joe Komlodi
2020-11-11 14:33 ` Francisco Iglesias
2020-11-13 0:44 ` Joe Komlodi
2020-11-06 1:32 ` [PATCH v3 2/3] hw/block/m25p80: Check SPI mode before running some Numonyx commands Joe Komlodi
2020-11-11 15:22 ` Francisco Iglesias
2020-11-06 1:32 ` Joe Komlodi [this message]
2020-11-11 15:40 ` [PATCH v3 3/3] hw/block/m25p80: Fix Numonyx fast read dummy cycle count Francisco Iglesias
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=1604626378-152352-4-git-send-email-komlodi@xilinx.com \
--to=joe.komlodi@xilinx.com \
--cc=alistair@alistair23.me \
--cc=figlesia@xilinx.com \
--cc=mreitz@redhat.com \
--cc=philippe.mathieu.daude@gmail.com \
--cc=qemu-block@nongnu.org \
--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).