tree 573f5473602b4009463f8bad424dbd3d899173ce
parent 14345c33461bc2373bc4f75f40baf4650e95ee54
author Serge Semin <Sergey.Semin@baikalelectronics.ru> 1602114910 +0300
committer Mark Brown <broonie@kernel.org> 1602194422 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl9/i/YACgkQJNaLcl1U
 h9AKRgf/fDcNdLGocTghkpIWrkHQ7gKcHUD0gBMTWZ6Wup7eCFZSztOKjDaxSD4P
 m0eG9Nb4pELyMMnbv6lMWr9fUixV6Wg7ElPrvK3qVO3FIgErg+ps2e42HJPS9rYS
 FRw+TZAPRpqHTOAMq1kif6wNjQnyHOZo7GZR9w9BFM3aJ9KoRfdorjPHZCl+BwEY
 grmmdtIN3rkU/COHn36kzaJDBbi6SBJilmFFseSNbp8pIxivO2pMcRV2hbrIn5gc
 AiOrvefagPXLblVmovlZJ/o0f45KS1tkh/2Qp9tQxaecXRd/lk+Z1aEU3pjg77O6
 0Ah1H8tZxes9Uf+E/+onmTM1BQ8k0Q==
 =Zhe9
 -----END PGP SIGNATURE-----

spi: dw: Add Baikal-T1 SPI Controller glue driver

Baikal-T1 is equipped with three DW APB SSI-based MMIO SPI controllers.
Two of them are pretty much normal: with IRQ, DMA, FIFOs of 64 words
depth, 4x CSs, but the third one as being a part of the Baikal-T1 System
Boot Controller has got a very limited resources: no IRQ, no DMA, only a
single native chip-select and Tx/Rx FIFO with just 8 words depth
available. In order to provide a transparent initial boot code execution
the Boot SPI controller is also utilized by an vendor-specific IP-block,
which exposes an SPI flash direct mapping interface. Since both direct
mapping and SPI controller normal utilization are mutual exclusive only
one of these interfaces can be used to access an external SPI slave
device. That's why a dedicated mux is embedded into the System Boot
Controller. All of that is taken into account in the Baikal-T1-specific DW
APB SSI glue driver implemented by means of the DW SPI core module.

Co-developed-by: Ramil Zaripov <Ramil.Zaripov@baikalelectronics.ru>
Signed-off-by: Ramil Zaripov <Ramil.Zaripov@baikalelectronics.ru>
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Link: https://lore.kernel.org/r/20201007235511.4935-22-Sergey.Semin@baikalelectronics.ru
Signed-off-by: Mark Brown <broonie@kernel.org>