SDK:ti-processor-sdk-linux-am437x-evm-07.03.00.005
Kernel:5.4.106
I use the SPI bus to connect to other devices, SPI for host mode,Tx and Rx both Use DMA mode.
I find that the SPI thread state becomes D when running for some time.
the SPI thread PID is 47
cat /proc/47/wchan ,return show :omap2_mcspi_tranfer_one
then i find omap2_mcspi_txrx_dma() use completion,and set it to TASK_UNINTERRUPTIBLE,
when i use kernel 4.19.94（last SDK）,Without this issue.
device tree ：
&spi2 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&spi2_pins_default>;
ti,spi-num-cs = <1>;
ti,pindir-d0-out-d1-in = <1>;
dmas = <&edma_xbar 16 0 16>,
<&edma_xbar 17 0 17>;
dma-names = "tx0", "rx0";
spidev:mainboard@0 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "spi,spi_mainboard";
spi-max-frequency = <2000000>;
reg = <0>;
pinctrl-names = "default";
pinctrl-0 = <&hw_version_pins>;
hwver0-gpios = <&gpio3 16 GPIO_ACTIVE_HIGH>;
hwver1-gpios = <&gpio3 15 GPIO_ACTIVE_HIGH>;
hwver2-gpios = <&gpio3 14 GPIO_ACTIVE_HIGH>;
};
};
terminal output:
Call relationship:omap2_mcspi_transfer_one()->omap2_mcspi_txrx_dma()->mcspi_wait_for_completion(),Maybe there's something wrong with this place,It can make the thread TASK_UNINTERRUPTIBLE.I guess.
The problem is contingency,Sometimes it comes quickly, sometimes it takes a long time.But the probability of occurrence is quite high.
