[0/4] spi: atmel-quadspi: Fix AHB memory accesses

Message

Tudor Ambarus Dec. 7, 2020, 1:59 p.m. UTC

Starting with the move of the atmel-quadspi driver under SPI,
the following error could be seen when mounting a 16MByte ubifs:
UBIFS error (ubi0:0 pid 1893): check_lpt_type.constprop.6: invalid type (15) in LPT node type

1/4 fixes AHB accesses. The rest of the patches are small optimizations.
Tested on both sama5d2 and sam9x60.

Tudor Ambarus (4):
  spi: atmel-quadspi: Fix AHB memory accesses
  spi: atmel-quadspi: Drop superfluous set of QSPI_IFR_APBTFRTYP_READ
  spi: atmel-quadspi: Write QSPI_IAR only when needed
  spi: atmel-quadspi: Move common code outside of if else

 drivers/spi/atmel-quadspi.c | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)

Comments

Mark Brown Dec. 7, 2020, 5:22 p.m. UTC | #1

On Mon, 7 Dec 2020 15:59:55 +0200, Tudor Ambarus wrote:
> Starting with the move of the atmel-quadspi driver under SPI,
> the following error could be seen when mounting a 16MByte ubifs:
> UBIFS error (ubi0:0 pid 1893): check_lpt_type.constprop.6: invalid type (15) in LPT node type
> 
> 1/4 fixes AHB accesses. The rest of the patches are small optimizations.
> Tested on both sama5d2 and sam9x60.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/4] spi: atmel-quadspi: Fix AHB memory accesses
      commit: cac8c821059639b015586abf61623c62cc549a13
[2/4] spi: atmel-quadspi: Drop superfluous set of QSPI_IFR_APBTFRTYP_READ
      commit: a6ff3a784ff9975dc77676827a2f448203511d19
[3/4] spi: atmel-quadspi: Write QSPI_IAR only when needed
      commit: d00364b6a60475cd75fd07e847ad6f955952638b
[4/4] spi: atmel-quadspi: Move common code outside of if else
      commit: c066efb07d1e8b801ea9d0727119958c9904e63d

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