Hi
On 3/8/2019 12:09 AM, Mark Brown wrote:
On Thu, Mar 07, 2019 at 05:26:53PM +0200, Jarkko Nikula wrote:
On 3/7/19 9:24 AM, xiao jin wrote:
The patch is to do cs again if spi-pxa2xx restar the SSP during
pxa2xx_spi_transfer_one()
Hmm.. please correct me if I'm wrong but pxa2xx_spi_unprepare_transfer() is
called always when there is no more messages pending and the spi core should
have deasserted the CS already?
Yes.
I try to describe the situation in more detail.
cpu0 cpu1
=> spi_transfer_one_message
=> __spi_pump_messages
=> __spi_sync
=> spi_sync
=> spi_sync_transfer.constprop.2
=> spi_write
=> fm1388_spi_burst_write
=> fm1388_fw_loaded
=> request_firmware_work_func
=> process_one_work
=> pxa2xx_spi_unprepare_transfer
=> spi_pump_messages
=> kthread_worker_fn
Yes, the spi core has de-asserted the CS before the
pxa2xx_spi_unprepare_transfer(). The problem on my side is that the new
transfer will restart the SSP in pxa2xx_spi_transfer_one(). The spi core
has asserted the CS again before restart the SSP. In my test the CS
assert before the restart SSP can't ensure the spi transfer working
correctly.
@@ -1056,6 +1057,11 @@ static int pxa2xx_spi_transfer_one(struct spi_controller *master,
if ((pxa2xx_spi_read(drv_data, SSCR0) != cr0)
|| (pxa2xx_spi_read(drv_data, SSCR1) & change_mask)
!= (cr1 & change_mask)) {
+ /* It needs to deassert the chip selection
+ * firstly before restart the SPP */
+ need_cs_change = true;
+ cs_deassert(spi);
I think code comes here at the beginning of each transfer so will be hit
multiple times before pxa2xx_spi_unprepare_transfer() if SPI message
consists of multiple transfers.
This makes me wondering if the device driver setting up the "struct
spi_transfer" is maybe missing the cs_change flag set for transfers before
last one in case HW needs CS toggling between transfers? For instance what
following drivers are doing with the cs_change flag:
drivers/char/tpm/tpm_tis_spi.c: tpm_tis_spi_transfer()
drivers/input/touchscreen/ad7877.c: ad7877_read(), ad7877_read_adc()
Right, this really feels like it's fixing the wrong thing.
I check the cs_change flag in the spi_transfer_one_message(). The
cs_change flag is used in two cases. If the transfer is the last one it
is used to keep the CS assert. If the transfer is not the last one it's
used to generate the 10us pulse and then de-assert the CS. In my case
the transfer is the last one and it can work correctly if I re-assert
the CS after restart the SSP in the pxa2xx_spi_transfer_one() which is
called from spi_transfer_one_message(). From my experiments both
cs_change flag cases in the spi_transfer_one_message() can't help the
problem. I am not sure if I fully understand your point.
