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 v5 0/4] hw/block/m25p80: Numonyx: Fix dummy cycles and check for SPI mode on cmds
Date: Mon, 16 Nov 2020 15:11:00 -0800 [thread overview]
Message-ID: <1605568264-26376-1-git-send-email-komlodi@xilinx.com> (raw)
Changelog:
v4 -> v5
- 3/4: Simplify logic when changing state and checking mode.
- 3/4: numonyx_get_mode -> numonyx_mode
- 4/4: Reword commit message to include QIO mode.
v3 -> v4
- 1/4: Patch changed to change names of register fields to be more accurate.
- 1/4: Revert polarity change from v3.
- 2/4: Added, fixes polarity of VCFG XIP mode when copied from NVCFG.
- 3/4: Removed check_cmd_mode function, each command check is done in decode_new_cmd instead.
- 3/4: Add guest error print if JEDEC read is executed in QIO or DIO mode.
- 3/4: Don't check PP and PP4, they work regardless of mode. PP4_4 is left as is.
- 3/4: Simplify get_mode function.
- 4/4: Simplify extract_cfg_num_dummies function.
- 4/4: Use switch statement instead of table for cycle retrieving.
v2 -> v3
- 1/3: Added, Fixes NVCFG polarity for DIO/QIO.
- 2/3: Added, Checks if we can execute the current command in standard/DIO/QIO mode.
- 3/3: Was 1/1 in v2. Added cycle counts for DIO/QIO mode.
v1 -> v2
- 1/2: Change function name to be more accurate
- 2/2: Dropped
Hi all,
The series fixes the behavior of the dummy cycle register for Numonyx flashes so
it's closer to how hardware behaves.
It also checks if a command can be executed in the current SPI mode
(standard, DIO, or QIO) before extracting dummy cycles for the command.
On hardware, the dummy cycles for fast read commands are set to a specific value
(8 or 10) if the register is all 0s or 1s.
If the register value isn't all 0s or 1s, then the flash expects the amount of
cycles sent to be equal to the count in the register.
Thanks!
Joe
Joe Komlodi (4):
hw/block/m25p80: Make Numonyx config field names more accurate
hw/block/m25p80: Fix when VCFG XIP bit is set for Numonyx
hw/block/m25p80: Check SPI mode before running some Numonyx commands
hw/block/m25p80: Fix Numonyx fast read dummy cycle count
hw/block/m25p80.c | 158 ++++++++++++++++++++++++++++++++++++++++++++----------
1 file changed, 129 insertions(+), 29 deletions(-)
--
2.7.4
next reply other threads:[~2020-11-16 23:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 23:11 Joe Komlodi [this message]
2020-11-16 23:11 ` [PATCH v5 1/4] hw/block/m25p80: Make Numonyx config field names more accurate Joe Komlodi
2020-11-16 23:11 ` [PATCH v5 2/4] hw/block/m25p80: Fix when VCFG XIP bit is set for Numonyx Joe Komlodi
2020-11-16 23:11 ` [PATCH v5 3/4] hw/block/m25p80: Check SPI mode before running some Numonyx commands Joe Komlodi
2020-11-17 14:44 ` Francisco Iglesias
2020-11-16 23:11 ` [PATCH v5 4/4] hw/block/m25p80: Fix Numonyx fast read dummy cycle count Joe Komlodi
2020-12-14 21:41 ` [PATCH v5 0/4] hw/block/m25p80: Numonyx: Fix dummy cycles and check for SPI mode on cmds Joe Komlodi
2020-12-15 13:40 ` Peter Maydell
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=1605568264-26376-1-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).