diff options
author | Serge Semin <Sergey.Semin@baikalelectronics.ru> | 2020-10-08 02:55:07 +0300 |
---|---|---|
committer | Mark Brown <broonie@kernel.org> | 2020-10-08 23:00:20 +0100 |
commit | 84ecaf4a7837e8c0957a59d77fd7e8e4926968cb (patch) | |
tree | ed78ba24895c4dff440107243b11f1556d4b0305 /drivers/pinctrl/pinctrl-pic32.h | |
parent | 6423207e57ea53826eaae1a14c14fd6d22561b06 (diff) |
spi: dw: Introduce max mem-ops SPI bus frequency setting
In some circumstances the current implementation of the SPI memory
operations may occasionally fail even though they are executed in the
atomic context. This may happen if the system bus is relatively slow in
comparison to the SPI bus frequency, or there is a concurrent access to
it, which makes the MMIO-operations occasionally stalling before
push-pulling data from the DW APB SPI FIFOs. These two problems we've
discovered on the Baikal-T1 SoC. In order to fix them we have no choice
but to set an artificial limitation on the SPI bus speed.
Note currently this limitation will be only applicable for the memory
operations, since the standard SPI core interface is implemented with an
assumption that there is no problem with the automatic CS toggling.
Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Link: https://lore.kernel.org/r/20201007235511.4935-19-Sergey.Semin@baikalelectronics.ru
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/pinctrl/pinctrl-pic32.h')
0 files changed, 0 insertions, 0 deletions