diff options
author | Pratyush Yadav <p.yadav@ti.com> | 2021-05-31 23:47:52 +0530 |
---|---|---|
committer | Tudor Ambarus <tudor.ambarus@microchip.com> | 2021-12-23 15:04:13 +0200 |
commit | 0d051a49829a96b26716a724df286be30da42f0e (patch) | |
tree | bde0af7f10dca511103c1df5214232e19b800947 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | 65b54ff67afab2754d61289ec59806d71c7dc0e8 (diff) | |
download | linux-0d051a49829a96b26716a724df286be30da42f0e.tar.gz linux-0d051a49829a96b26716a724df286be30da42f0e.tar.bz2 linux-0d051a49829a96b26716a724df286be30da42f0e.zip |
mtd: spi-nor: core: use 2 data bytes for template ops
The template ops used in spi_nor_spimem_check_pp() and
spi_nor_spimem_check_readop() currently set the data phase to 1 byte
long. This is problematic for 8D-8D-8D protocol where odd length data
phase is invalid since one cycle transfers 2 bytes and odd number of
bytes would mean half a cycle is left over. This could result in a
controller rejecting the op as "not supported" even though it actually
supports the protocol.
Change the data length to 2 bytes in these templates. One might argue
that this should only be done for 8D-8D-8D operations but when talking
about these templates, there is no functional difference between one and
two bytes, even in STR modes.
Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Reviewed-by: Michael Walle <michael@walle.cc>
Link: https://lore.kernel.org/r/20210531181757.19458-2-p.yadav@ti.com
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions