spi: bcm-qspi: fix MSPI only access with bcm_qspi_exec_mem_op()
Subsystems (2)
PATCH 1/1 spi: bcm-qspi: fix MSPI only access with bcm_qspi_exec_mem_op()
This fixes case where MSPI controller is used to access spi-nor flash and BSPI block is not present.
--- drivers/spi/spi-bcm-qspi.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/spi/spi-bcm-qspi.c +2 -2
@@ -1205,7 +1205,7 @@ static int bcm_qspi_exec_mem_op(struct spi_mem *mem, addr = op->addr.val; len = op->data.nbytes; -if (bcm_qspi_bspi_ver_three (qspi) == true) { +if (has_bspi (qspi) &&bcm_qspi_bspi_ver_three (qspi) == true) {/* * The address coming into this function is a raw flash offset. * But for BSPI <= V3, we need to convert it to a remapped BSPI
@@ -1224,7 +1224,7 @@ static int bcm_qspi_exec_mem_op(struct spi_mem *mem, len < 4) mspi_read = true; -if (mspi_read) +if (!has_bspi (qspi) || mspi_read)return bcm_qspi_mspi_exec_mem_op (spi, op); ret =bcm_qspi_bspi_set_mode (qspi, op,0 );
Signature · 1 line
2.17.1
Quoted 5 lines · Kamal Dasu
This fixes case where MSPI controller is used to access spi-nor flash and BSPI block is not present.
Fixes 5f195ee7d830 ("spi: bcm-qspi: Implement the spi_mem interface")Signed-off-by Kamal Dasu <[email protected]>
Signature · 1 line
Florian
Mark Brown
maintainerQuoted 4 lines · Kamal Dasu
This fixes case where MSPI controller is used to access spi-nor flash and BSPI block is not present.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: bcm-qspi: fix MSPI only access with bcm_qspi_exec_mem_op()
commit: 2c7d1b281286c46049cd22b43435cecba560edde
All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying to this mail.
Thanks,
Mark