summaryrefslogtreecommitdiff
path: root/tools/testing/radix-tree/linux/xarray.h
diff options
context:
space:
mode:
authorBogdan-Gabriel Roman <bogdan-gabriel.roman@nxp.com>2025-05-22 15:51:31 +0100
committerMark Brown <broonie@kernel.org>2025-05-22 16:05:25 +0100
commit8a30a6d35a11ff5ccdede7d6740765685385a917 (patch)
treecbd464c846fed48da9aaaf393cc5711ec7ed82f0 /tools/testing/radix-tree/linux/xarray.h
parent283ae0c65e9c592f4a1ba4f31917f5e766da7f31 (diff)
spi: spi-fsl-dspi: Halt the module after a new message transfer
The XSPI mode implementation in this driver still uses the EOQ flag to signal the last word in a transmission and deassert the PCS signal. However, at speeds lower than ~200kHZ, the PCS signal seems to remain asserted even when SR[EOQF] = 1 indicates the end of a transmission. This is a problem for target devices which require the deassertation of the PCS signal between transfers. Hence, this commit 'forces' the deassertation of the PCS by stopping the module through MCR[HALT] after completing a new transfer. According to the reference manual, the module stops or transitions from the Running state to the Stopped state after the current frame, when any one of the following conditions exist: - The value of SR[EOQF] = 1. - The chip is in Debug mode and the value of MCR[FRZ] = 1. - The value of MCR[HALT] = 1. This shouldn't be done if the last transfer in the message has cs_change set. Fixes: ea93ed4c181b ("spi: spi-fsl-dspi: Use EOQ for last word in buffer even for XSPI mode") Signed-off-by: Bogdan-Gabriel Roman <bogdan-gabriel.roman@nxp.com> Signed-off-by: Larisa Grigore <larisa.grigore@nxp.com> Signed-off-by: James Clark <james.clark@linaro.org> Link: https://patch.msgid.link/20250522-james-nxp-spi-v2-2-bea884630cfb@linaro.org Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/testing/radix-tree/linux/xarray.h')
0 files changed, 0 insertions, 0 deletions