| commit | 80f2c625cbd67447a750c0c6c5d377dfa65d4d7d | |
| author | Stephen Checkoway <stephen.checkoway@oberlin.edu> | |
| Fri, 26 Apr 2019 16:26:24 +0000 (26 12:26 -0400) | ||
| committer | Philippe Mathieu-Daudé <philmd@redhat.com> | |
| Tue, 2 Jul 2019 00:34:55 +0000 (2 02:34 +0200) | ||
| tree | b1b6632bde06ff580897e84e5acb3e1471773ab5 | treesnapshot (tar.gz zip) |
| parent | ddb6f2254871c7c686561c4b41d52e2f0413f9a1 | commitdiff |
hw/block/pflash_cfi02: Use chip erase time specified in the CFI table
When erasing the chip, use the typical time specified in the CFI table
rather than arbitrarily selecting 5 seconds.
Since the currently unconfigurable value set in the table is 12, this
means a chip erase takes 4096 ms so this isn't a big change in behavior.
Signed-off-by: Stephen Checkoway <stephen.checkoway@oberlin.edu>
Message-Id: <20190426162624.55977-11-stephen.checkoway@oberlin.edu>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
When erasing the chip, use the typical time specified in the CFI table
rather than arbitrarily selecting 5 seconds.
Since the currently unconfigurable value set in the table is 12, this
means a chip erase takes 4096 ms so this isn't a big change in behavior.
Signed-off-by: Stephen Checkoway <stephen.checkoway@oberlin.edu>
Message-Id: <20190426162624.55977-11-stephen.checkoway@oberlin.edu>
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
| hw/block/pflash_cfi02.c | diffblobblamehistory |