| commit | 02a595d5d6e4ecc0564ec31afb76202035a7591c | |
| author | Heiner Kallweit <hkallweit1@gmail.com> | |
| Wed, 17 Aug 2016 19:11:01 +0000 (17 21:11 +0200) | ||
| committer | Mark Brown <broonie@kernel.org> | |
| Thu, 18 Aug 2016 10:15:16 +0000 (18 11:15 +0100) | ||
| tree | e4ec99f150702f31fc5d6afb60586492b32dbd44 | treesnapshot (tar.gz zip) |
| parent | 5090cc6ae2f79ee779e5faf7c8a28edf42b7d738 | commitdiff |
spi: fsl-espi: eliminate spi nor flash read loop
The fsl-espi driver contains a read loop that implicitely assumes that
the device to read from is a m25p80 SPI NOR flash (bytes 2 - 4 of the
first write transfer are interpreted as 3 byte flash address).
Now that we have such a read loop in the spi-nor driver and are able
to correctly indicate the message size limit of the controller,
the read loop can be removed from the fsl-espi driver.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
The fsl-espi driver contains a read loop that implicitely assumes that
the device to read from is a m25p80 SPI NOR flash (bytes 2 - 4 of the
first write transfer are interpreted as 3 byte flash address).
Now that we have such a read loop in the spi-nor driver and are able
to correctly indicate the message size limit of the controller,
the read loop can be removed from the fsl-espi driver.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
| drivers/spi/spi-fsl-espi.c | diffblobblamehistory |